[BREACH] VS Code extensions are now part of the supply chain
The plugin had keys. A VS Code extension sat beside repos, tokens, terminals, and AI configs. That is not just productivity. That is inherited access.
The plugin had keys. A VS Code extension sat beside repos, tokens, terminals, and AI configs. That is not just productivity. That is inherited access.
Known AI agents are becoming trusted traffic. The first defender move is finding claims without proof.
The forecast likely resolves No, but the useful lesson is where Iran-linked operators still depend on access defenders can pressure.
The best intel sharing still somehow happens next to bad coffee and a suspiciously sticky conference table..
The forecast is stubborn.
Iran-linked PLC activity is real. The harder part is proof: numbers, attribution, novelty.
Noise is not qualification.
We’re revising the Akira hospital disruption forecast down to 2%. The risk is real, but the question is narrower than it looks.
“Secure by default” sounds great until it meets BYOD, VDI, federated SSO, and the help desk exception list from hell.
Device-bound sessions help.
Waiting for every SaaS vendor to flip the default is not a strategy.