ACVERogue and malicious agent events

ACVE-2026-0539 · Real incident · HIGH

Reviewed incident · from the researchers' own report

WHAT HAPPENED

The hijacked assistant recommends and executes the installation of a poisoned external package, which the attacker uses to steal tokens and deploy a worm.

Not reported: Mandiant's case study does not say whether the compromise was contained, the tokens revoked or the repositories cleaned.

THE SETUP — is yours like this?

WHAT TO CHANGE

Protect secrets and verify dependencies recommended by coding agents.

  • Reconfigure agent.approval to ask. Dependency installation and repository-wide actions need review. Owner: operator
  • Reconfigure coding-assistant.credentials to local credentials kept out of the assistant extension's reach. Recommended: Mandiant advises it after the hijacked session harvested GitHub OAuth tokens. Owner: harness-vendor

HARM, REACH AND RECOVERY

SOURCES

First-hand sources

REPORT

ARTICLE

Technical details

An attacker hijacked a developer's AI coding-assistant session, which recommended a poisoned package; the attacker then stole tokens and spread the Shai-Hulud worm across about 100 repositories.

Model as recorded: any; product and model not stated

Reproducibility: partial (model availability not checked (no registry reference); trigger not published)

Claims

Confirmed means the statement matches the cited primary source. Nothing on this page has been reproduced.

The exposure axes marked confirmed were matched to the first-hand sources listed above.

Description

Threat

user · supply-chain · exfiltration

What

In a case study in its September 2026 AI risk and resilience report, Mandiant says a threat actor compromised a SaaS provider and hijacked an active AI coding-assistant session on a developer's workstation. The assistant recommended installing an external package the attacker had poisoned, and by executing that recommendation it helped install the malicious software. Through the developer's session the attacker then installed an infostealer via a poisoned PyPI package, harvested GitHub OAuth tokens and deployed the self-propagating Shai-Hulud worm across about 100 internal code repositories, stealing repository secrets and proprietary source code. The attacker also poisoned a package in the organisation's official namespace, which infected another employee who pulled it. The assistant's product and model are not named.

Detection

The case study does not state when or how the session was hijacked, or whether the compromise was contained. Recorded from Mandiant's report. Not recreated in a lab.

Fix

Keep secrets and long-lived tokens out of direct agent reach, verify agent-recommended dependencies, and route dependencies through controlled repositories.

Validation

Report a problemJSON