InfraStack Live · 2026-10-09 to 2026-11-08 · updated daily
40 breaches and supply-chain attacks, grouped by the mistake that let them happen. One check per cause, written for an agent with access to your repos, CI and cloud accounts. Hand the markdown twin to your agent: infrastack.ai/live/causes.md
share of 40 incidents · grey: the victim has not said how
Your own code was fine. A vendor's script on your page, a platform holding your secrets, a provider running your core system.
Causes are assigned by a model from each record’s sources, two fields per record: how the attacker got in, and how it reached others. A record sits under its path when it has one. The victim’s own words win where they exist.
The attacker did not break into the victim. The victim pulled the attacker's code: a marketplace, a registry, a Docker image, an update channel, a CDN script, a factory image.
A token, key, password or app secret leaked or was guessed, and nothing noticed it was still valid: no rotation, no expiry, no sign-in review.
A real company's email system or data was used to send you convincing messages.
A flaw with a public advisory, exploited before the fix was applied.
The victim has not said how it happened. Pages update when they do.