← Back to tableAll incidents timeline

Suggest a change

About Claude Mythos 5 publishes a malicious package to PyPI in an eval

Suggest a change to an entry, the methodology or the ledger as a whole: something to fix, correct or add. We read every suggestion, and check corrections against their sources.

Anthropic· Claude Mythos 5

Claude Mythos 5 publishes a malicious package to PyPI in an eval

During an Irregular capture-the-flag evaluation, Claude Mythos 5 built a malicious Python package, published it to the real PyPI, and used credentials it captured from a security vendor's scanner to reach that vendor's live database.

The model was told it had no internet access, but the evaluation environment was connected to the internet. Trying to compromise its fictional target, it published a malicious package to PyPI. Anthropic says the package was public for roughly one hour and was downloaded and run on 15 real systems, one of them a real security company's malware scanner. The model sent that company's credentials to a collection point it had set up and used them to access more of the company's infrastructure; the September assessment says this was the vendor's live database. PyPI's own security systems removed the package. Anthropic says the model kept treating the environment as simulated despite evidence it was real.

Updated 19 Oct 2026

First incident action to disclosure
Unknown
First incident action to discovery
Not disclosed
Noticed first by
The handler
Caught
A later review

What happened

  • First incident action
  • Unnoticed
  • Handler found out
  • Known, not public
  • Disclosed
  • Public
  1. Not disclosed

    First incident action

    Mythos 5 builds and publishes a malicious package to PyPI

    It registered with a disposable email provider PyPI had not blocked and published three versions of the package. Not dated beyond the April 2026 start of the three July-disclosed incidents.

  2. Not disclosed

    Package runs on 15 real systems, including a security vendor's scanner

    Public for roughly one hour. The model took credentials left in the vendor scanner's sandbox, sent them to a collection point it had set up and used them to reach more of the vendor's infrastructure, which the September assessment calls the vendor's live database.

  3. Not disclosed

    PyPI's security systems remove the package

    Automatic removal after about an hour. No source says anyone linked it to Anthropic at the time.

  4. 24 Jul 2026

    Handler found out

    Anthropic identifies the incident in its transcript review

    Review began 23 July.

  5. 27 Jul 2026

    Anthropic notifies Irregular and affected organisations; PyPI told separately

    The July post says PyPI was notified and given indicators; the date of that notice is not stated.

  6. 30 Jul 2026

    Disclosed

    Anthropic publishes the three incidents

  7. 9 Sep 2026

    Assessment says offline monitor would likely have missed it

    Anthropic says its offline monitor flagged about 1% of actions, while its cyber classifiers would have caught each incident; it describes the model as disregarding evidence it was on the real internet.

Agent failures

Sandbox escape, Supply chain compromise, Credential misuse, Data exfiltrationShow
Map to frameworks
  • Sandbox escape

    Reached the live internet from an environment it was told was offline.

  • Supply chain compromise

    Published a malicious package to the real PyPI, where 15 systems ran it.

  • Credential misuse

    Used a security vendor's credentials to reach its live database.

  • Data exfiltration

    Sent the captured credentials to a collection point it had set up.

How it was found

Found first by the handler, from a later reviewShow
Found first by
The handler
How
A later review
Found to disclosed
6 days

PyPI's automated systems took the package down after about an hour, but no source says anyone connected it to Anthropic's evaluation at the time. Anthropic found the run in its July transcript review. In September Anthropic said its offline monitor would likely not have flagged this incident, because the model's reasoning misled it, while its cyber classifiers would have caught each incident.

What is publicly known

3 of 12 fully publicShow
3 of 12 fully public
ItemPublic?DetailSources
PartialClaude Mythos 5, named by Anthropic; checkpoint not given.
PartialThe published transcript includes raw thinking, so thinking was on. The effort or budget setting is not stated.
KnownNo release safeguards were active. Anthropic estimates auto mode would have denied 66% of actions; offline monitor would likely have missed it.
PartialSaid to describe a simulation without internet access. Excluded from the published transcript; opening messages redacted.
PartialA capture-the-flag task to compromise a fictional company. Challenge prompt left out of the transcript release.
WeakIrregular environment; the transcript shows tool calls but tool definitions are not published. Could publish to real PyPI.
PartialEnvironment was connected to the live internet by mistake, reaching real PyPI. Configuration detail not given.
PartialRedacted raw transcript with thinking and tool calls on GitHub; messages 1 to 81 and after 2145 removed, secrets masked.
KnownPyPI's systems removed the package after about an hour; Anthropic found the run in its 24 July transcript review.
PartialPackage ran on 15 third-party hosts, which Anthropic believes were all security vendors' scanners; one vendor lost credentials and had its live database reached.
KnownUnintended internet access; Anthropic says biased reasoning led the model to keep treating a real environment as simulated.
PartialPyPI given indicators; default outbound blocking and new misconfigured-CTF evals listed as done. Not independently verified.

Controls that apply

  • Protect

    Hold test, training and evaluation environments to production standards

    The model was told it had no internet, but the evaluation environment was connected, and Anthropic says the model kept treating it as simulated despite evidence it was real. With the internet closed, the malicious package it built would have had no real registry to reach and no real systems to run on.

  • Limit where the agent can send traffic

    Requests to the real PyPI to register with a disposable email and publish three versions of a package, then traffic carrying a security vendor's credentials to a collection point the model had set up. A destination allowlist would have refused both and raised the attempts.

  • Isolate where the agent runs

    An evaluation run publishing to a public registry and then reaching a security vendor's live database with captured credentials. Raised as a boundary crossing, it would have surfaced during the run rather than in the July transcript review.

  • Detect

    Record every agent action, outside the agent

    The actions themselves: an account registered with a disposable email, three package versions published to PyPI, and a vendor's credentials sent to a collection point. Anthropic found the run in its July transcript review and has published the redacted tool calls.

  • Monitor every run and alert on what does not fit the task

    Anthropic says its offline monitor, which flagged about 1% of actions, would likely have missed this run because the model's reasoning misled it, while its cyber classifiers reading actions would have caught it. PyPI removed the package after about an hour, but no one linked it to the evaluation until July.

  • Respond

    Contain, notify and disclose

    PyPI's own systems removed the package, and no source says anyone tied it to Anthropic's evaluation at the time. Anthropic notified Irregular and affected organisations on 27 July and gave PyPI indicators separately, on a date it does not state.

  • All controls →

Coverage and commentary

4 posts on X, 3 articlesShow
All 6 sources
  1. Primary source

    Investigating three incidents in our cybersecurity evaluations ↗Anthropic · 2026-07-30

  2. Primary source

    An alignment assessment of recent cybersecurity incidents ↗Anthropic · 2026-09-09

  3. Primary source

    mythos-5-incident-transcript ↗Anthropic (GitHub)

  4. Commentary

    Claude's Cybersecurity Evaluations Breached Three Organizations ↗Cloud Security Alliance · 2026-07-31

  5. Commentary

    Investigating three real-world incidents in our cybersecurity evaluations ↗Simon Willison's Weblog · 2026-07-30

  6. Commentary

    Anthropic Looks At Some Of Its Alignment Problems ↗Don't Worry About the Vase (Substack)

Entry id anthropic-mythos5-pypi-2026 · overall Confirmed · impact serious