[AI](https://leakly.com/ai/)

[Confirmed][Archive]

# A Claude Code packaging mistake exposed the tool’s internal workings

Anthropic confirmed a packaging error exposing internal source and said no sensitive customer data or credentials were exposed.

Published 09 Nov 2026, 02:21 UTC

Leaked on 31 March 2026

![Original Leakly terminal-style archive card: A Claude Code packaging mistake exposed the tool’s internal workings](https://leakly.com/assets/og/claude-code-package-map.png)

## Previously on this story

[![Original Leakly terminal-style archive card: An exposed publishing cache revealed Anthropic’s Mythos model](https://leakly.com/assets/images/anthropic-mythos-cms-400x300.jpg)](https://leakly.com/archive/anthropic-mythos-cms/)

[Confirmed][Archive]

AI

### [An exposed publishing cache revealed Anthropic’s Mythos model](https://leakly.com/archive/anthropic-mythos-cms/)

Published 09 Nov 2026, 02:21 UTCLeaked on 26 March 2026

Related earlier disclosure; a distinct leak, not a duplicate account of this event.

Anthropic suffered a second, distinct disclosure days after the Mythos publishing-cache story. On 31 March 2026, a Claude Code release included a source-map file that exposed the coding tool’s internal source. Ars Technica, The Verge and TechCrunch reported the incident and the company’s response.

The distinction from Mythos is essential. This was a software packaging problem involving the application around the AI model, not the release of model weights. Treating both events as the same leak would erase how they happened and exaggerate what was available. The two stories are linked here as related incidents, not duplicate accounts of one discovery.

Contemporary reporting credited security researcher Chaofan Shou with calling attention to the package. Code copies and analyses then spread rapidly. We do not link those copies or reproduce implementation details. The public-interest question is the failed release process and the implications of exposing a commercially important tool’s internal design.

Anthropic acknowledged that a release had included internal source code and said no sensitive customer data or credentials had been exposed. It characterized the event as a human packaging error rather than a security breach. The confirmed badge concerns the source exposure it acknowledged, not an assumption that every claim made by people examining the files was accurate.

The Verge described apparent unreleased ideas, including an always-on agent and a virtual pet. Those are development clues, not commitments to ship. It is possible for code to contain experiments, abandoned work or features that change substantially before release. The archive therefore separates the confirmed accidental disclosure from speculation about the roadmap. All links lead to reporting rather than repositories, archives or download instructions, and the original per-story illustration contains no copied source code or confidential interface imagery.

[Confirmed]

## What happened later

Anthropic confirmed a packaging error exposing internal source and said no sensitive customer data or credentials were exposed.

## Sources & captured post

> **The Verge** @verge
>
> Claude Code leak exposes a Tamagotchi-style ‘pet’ and an always-on agent https://t.co/ur16kzh36c
>
> 92 likes · 7 reposts · counts as of 09 Nov 2026, 01:46 UTC
>
> [View the post on X](https://x.com/verge/status/2039107476994543783) · not in our leaker index

### Original source & corroborating coverage

* [Original X post by @verge](https://x.com/verge/status/2039107476994543783)
* [Ars Technica — Entire Claude Code CLI source code leaks thanks to exposed map file - Ars Technica](https://arstechnica.com/ai/2026/03/entire-claude-code-cli-source-code-leaks-thanks-to-exposed-map-file/)
* [The Verge — Claude Code leak exposes a Tamagotchi-style ‘pet’ and an always-on agent](https://www.theverge.com/ai-artificial-intelligence/904776/anthropic-claude-source-code-leak)
* [TechCrunch — Anthropic is having a month](https://techcrunch.com/2026/03/31/anthropic-is-having-a-month/)

[Status definitions](https://leakly.com/editorial-guidelines/#status) · [Corrections](https://leakly.com/corrections/) · [Contact](https://leakly.com/contact/)