No, Claude Didn't 'Go Rogue' — But Its Supply Chain Did

Reports have circulated describing an "autonomous Claude coding agent" publishing malicious packages to public registries — but that's not what the record shows. What actually happened is arguably more instructive: Claude Code became a target, not a perpetrator, across two separate 2026 incidents.

On March 31, 2026, Anthropic accidentally exposed Claude Code's full source through a 59.8MB unminified JavaScript source map bundled into the public @anthropic-ai/claude-code npm package — roughly 513,000 lines of TypeScript across nearly 2,000 files, laid bare for anyone who downloaded it.

What happened

Read Zscaler's account next to the product docs, not instead of them. Names and figures in the lede are the ones we can stand behind; everything else below is how teams usually absorb a story like this. If a number, ship date, or quote is not in the source excerpt, it is not in this briefing. That is deliberate — day-one coverage is where invented specifics do the most damage.

Reports have circulated describing an "autonomous Claude coding agent" publishing malicious packages to public registries — but that's not what the record… What actually happened is arguably more instructive: Claude Code became a target, not a perpetrator, across two separate 2026 incidents.

How it works

Under the hood this is a systems change, not a press-release adjective. Ask what surface area moved — API, policy, hardware, model behavior, or go-to-market — and which of those you actually ship against. A useful working question: if you had to draw the before/after on a whiteboard, which box would you erase? That is the mechanism. Everything else is packaging.

On March 31, 2026, Anthropic accidentally exposed Claude Code's full source through a 59.8MB unminified JavaScript source map bundled into the public @anthropic-ai/claude-code npm package — roughly 513,000 lines of TypeScript across nearly 2,000 files, laid bare for anyone who downloaded it. Read Zscaler's account next to the product docs, not instead of them.

Why it matters

If you build on or compete with the parties named in No, Claude Didn't 'Go Rogue' — But Its Supply Chain Did, the practical hit is on roadmap sequencing and risk reviews this quarter, not on a vague 'future of the industry'. Put one owner on the story, give them a day to read the primary material, and decide whether this is a this-sprint item, a this-quarter item, or noise.

Names and figures in the lede are the ones we can stand behind; everything else below is how teams usually absorb a story like this. If a number, ship date, or quote is not in the source excerpt, it is not in this briefing.

Who is affected

Incumbents, customers, and adjacent open-source projects do not feel this equally. Map the change to your own stack: what you operate, what you buy, and what you will have to explain to a security, legal, or finance review. Partners and resellers often feel it before the end user does — check those contracts before you assume nothing moved.

That is deliberate — day-one coverage is where invented specifics do the most damage. Under the hood this is a systems change, not a press-release adjective.

What to watch next

Treat the next two weeks as a verification window. Watch the vendor's own changelog, any regulator or standards follow-up, and whether a competitor ships a matching capability. Do not change production on day-one coverage alone. If nothing new is published in that window, the story was smaller than the headline.

Ask what surface area moved — API, policy, hardware, model behavior, or go-to-market — and which of those you actually ship against. A useful working question: if you had to draw the before/after on a whiteboard, which box would you erase?

A 3–5 minute news post is a briefing, not a runbook. Keep Zscaler and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of No, Claude Didn't 'Go Rogue' — But Its Supply Chain Did.