Weekly reading · methodology v0.6
Window ending June 1, 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 May 3, 2026 through June 1, 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
2
Control failures only · No qualifying harm. The reading is the highest control level breached: 2, by 1 record. It is a level, not a count.
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
2 selected records; 0 documented external harms counting (1 qualifying). Records and ratings below reflect the current catalogue.
No harm counts in this week. The reading is the highest control level breached: 2 (set by 1 record: PI-0055). It is a level, not a count.
- Documented harm
- 1
- No harm found (stated scope)
- 0
- No harm reported
- 1
- Impact unknown
- 0
- Alleged, AI role uncorroborated
- 0
- Counts toward the index
- 1
- Unverified, watching
- 0
- Alleged in court
- 0
- Control failure, tracked
- 1
- Tracked separately
- 0
Documented exclusions: 0 internal; 0 awaiting evidence review. 0 qualifying records with a bounded single-source review.
Inspect the evidence · 2 records
- PI-0055 · Morse-code prompt on X tricked Grok and Bankrbot into sending about $175,000 in tokensDocumented harm · qualifying harm, no longer counting · extent undisclosed
- PI-0084 · Pennsylvania sues Character.AI, alleging chatbots posed as licensed psychiatrists and gave a fake license numberNo harm reported · excluded from the harm reading
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-0055Morse-code prompt on X tricked Grok and Bankrbot into sending about $175,000 in tokensMay 4, 2026 · Minor harm · no longer counting · Deployment
- PI-0084Pennsylvania sues Character.AI, alleging chatbots posed as licensed psychiatrists and gave a fake license numberMay 5, 2026 · No harm reported · Deployment
Sources
These links support the records above. Source availability and conclusions may change.
- Cointelegraph: How a Free NFT Allegedly Drained $174K From a Grok-Connected WalletCited in PI-0055
- CryptoSlate: Grok's crypto wallet was just exploited by a tweet sent in morse code without any private key compromiseCited in PI-0055
- Giskard: How Grok got prompt injected: an X user drained $150,000 from an AI walletCited in PI-0055
- OECD.AI Incidents Monitor: AI Prompt Injection Exploit Drains Grok-Linked Crypto WalletCited in PI-0055
- Pennsylvania Governor's Office: Shapiro Administration Sues Character.AI Alleging AI Chatbot Unlawfully Presented Itself as Licensed Medical Professional in PennsylvaniaCited in PI-0084
All weekly readings · How this reading is calculated · Download the weekly card
