Sunday, November 22, 2026 Independent technology & AI reporting
SoilTune Tech & AI, decoded

Security

Supply-chain attacks, exploited zero-days and the trust model behind the software we use. SoilTune's security coverage, start here.

Last updated November 21, 2026

Security coverage at SoilTune follows the parts of the stack that fail quietly: a vendor’s signup flow, an extension inside a remote-management tool, a model that finds a zero-day before the vendor can patch it. We are interested in what actually happened, which trust relationship broke, and what defenders can do about it.

Our approach is deliberately narrow. We read the primary advisories, the vendor statements and the technical write-ups. We separate what is confirmed from what is alleged, and we say when a key question is still unanswered. We do not publish exploit code or instructions that would help someone attack a system. When we get something wrong, we correct it in public on our corrections page.

Start with the supply-chain incidents below. They share a pattern: the victims’ own code was fine, and the trust they placed in someone else’s was the vulnerability. Then follow the zero-day and policy coverage for the other side of the same problem, how attackers find weaknesses, and how governments and vendors respond.

Start here

More security coverage

How we cover security

  • Primary sources first. We link to vendor advisories, court documents, regulatory filings and the researchers’ own write-ups. If a claim rests on a secondary report, we say so.
  • No exploit code. We describe impact, timeline and defense. We do not publish step-by-step instructions for attacking a system or evading a control.
  • Updates are labeled. Refreshed articles carry a “What changed” block and a “Last reviewed” date. Substantive corrections are logged on the corrections page.
  • Tips are welcome. Use the contact form and choose Editorial. We do not promise anonymity.

Related hubs

Security work rarely stays in one lane. For the policy side, see Policy. For the companies and products behind the incidents, see Big Tech. For the models and tools being attacked or used as attack tools, see AI. For patches, releases and developer tooling, see Software.

You can also browse the full Security archive, newest first.

Have a tip? Email [email protected] or use the contact form and choose Editorial. We do not promise anonymity.