Weekly reading · methodology v0.6
Window ending April 27, 2026
Harms count in full for two weeks after they are reported, then one level less every two weeks. The control floor looks at reports from March 29, 2026 through April 27, 2026. A selected catalogue of reported AI incidents, reviewed through Oct. 7, 2026. This reading describes documented harm in the records or, when none qualifies, the highest control level breached. It is not a forecast or a measure of all AI activity.
Current recalculation
20
Minor harm · Worst documented harm counting: minor. 1 record at this level.
Recalculated from the catalogue in this build. Historical backcasts were not published at the time.
Published at the time
No publication snapshot exists for this week.
This is a backcast from the current catalogue. It was not a reading published at the time.
Records behind this reading
3 selected records; 1 documented external harm counting (1 qualifying). Records and ratings below reflect the current catalogue.
1 qualifying harm record. Extent undisclosed for this record.
- Documented harm
- 1
- No harm found (stated scope)
- 0
- No harm reported
- 2
- Impact unknown
- 0
- Alleged, AI role uncorroborated
- 0
- Counts toward the index
- 1
- Unverified, watching
- 0
- Alleged in court
- 0
- Control failure, tracked
- 2
- Tracked separately
- 0
Documented exclusions: 0 internal; 0 awaiting evidence review. 0 qualifying records with a bounded single-source review.
Inspect the evidence · 3 records
- PI-0052 · In an authorized test, Claude Mythos Preview escaped its sandbox and, unasked, posted exploit details on public websitesNo harm reported · excluded from the harm reading
- PI-0053 · An earlier Claude Mythos version hid forbidden file edits from git history during internal testingNo harm reported · excluded from the harm reading
- PI-0054 · Coding agent used a stray API token to delete a startup's production database and backupsDocumented harm · qualifying harm · extent undisclosed
Status totals cover counted records; aliases, superseded aggregates and records tracked separately are excluded. Eligibility and extent notes overlap those totals. These observations are not statistical uncertainty bounds.
- PI-0052In an authorized test, Claude Mythos Preview escaped its sandbox and, unasked, posted exploit details on public websitesApril 7, 2026 · No harm reported · Internal research
- PI-0053An earlier Claude Mythos version hid forbidden file edits from git history during internal testingApril 7, 2026 · No harm reported · Internal research
- PI-0054Coding agent used a stray API token to delete a startup's production database and backupsApril 25, 2026 · Minor harm · Deployment
Sources
These links support the records above. Source availability and conclusions may change.
- Anthropic: System Card: Claude Mythos PreviewCited in PI-0052, PI-0053
- The Next Web: Anthropic's most capable AI escaped its sandbox and emailed a researcher - so the company won't release itCited in PI-0052
- Futurism: Anthropic Warns That 'Reckless' Claude Mythos Escaped a Sandbox Environment During TestingCited in PI-0052, PI-0053
- Fanatical Futurist: Anthropic says reckless Claude Mythos AI escaped its sandbox during testingCited in PI-0053
- Jer Crane (@lifeofjer) on X: An AI Agent Just Destroyed Our Production Data. It Confessed in Writing. (article on X)Cited in PI-0054
- Railway: Your AI wants to nuke your database. Guardrails fix that.Cited in PI-0054
- Decrypt: AI agent deletes startup database in 9 seconds, founder saysCited in PI-0054
- ABC7 News: 'Rogue' AI agent from SF-based Cursor goes haywire, deletes company's entire databaseCited in PI-0054
- ProPakistani: Claude-powered AI agent deleted entire startup database and backups in 9 secondsCited in PI-0054
- ACS Information Age: Gone in 9 seconds: AI agent deletes company databaseCited in PI-0054
All weekly readings · How this reading is calculated · Download the weekly card
