AI agent incident
Mandiant reported that an attacker hijacked an AI coding assistant session and used it to spread the Shai-Hulud worm across about 100 internal repositories.
The session was the credential. Everything the assistant could reach, the attacker could reach, and code suggestions are a delivery route nobody reads line by line.
New incidents by email
Get incidents like this one in your inbox
New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.
You confirm by email. Unsubscribe in one click.
Agent plugins and skills are a supply chain An explainer on the problem behind this incident.
“A hijacked coding assistant session spread Shai-Hulud across about 100 repositories.” The Permission Layer AI Agent Incident Database, https://thepermissionlayer.com/incidents/shai-hulud-coding-assistant-session/. Database updated October 22, 2026.
Every record traces to the dated sources above. If something here is wrong or missing, email [email protected] and it gets fixed. See this record in the full list.
The Permission Layer
At least one email a week on AI agent identity, permissions, security and spend, written for the people who approve agent access. Five-minute read, free.
You confirm by email. Unsubscribe in one click.