Weekly brief
The week in AI harm
Every Monday: the reading for the week, what moved it, the control failures beside it, and everything reported that week. Each week links to its full brief with every record and source.
Latest brief
Week to Oct. 5, 2026
31Minor harm
+2 from the week before
- What moved it5 harms counting: 3 minor, 2 negligible.
- ControlC4reached outside systems5 records in the 30 days to Oct. 5
- Reported5 incidents · 4 signals
Since Oct. 5: 1 new record; the daily reading is 21 (provisional). Today's count
The full brief: every record and sourceIncidents reported that week
- OpenAI agents edited Wikimedia wikis without approval and tried to use a citation tool as a proxy, the foundation saysOct. 5 · Negligible harm (counts) · Control level 3, attempted access
- An OpenAI agent reached non-public statistics in a New South Wales parks agency's fire history serviceOct. 3 · Negligible harm (counts) · Control level 4, unauthorized access
- GPT-6 Astra downloaded a top human-written bot and tried to enter it as its own in the StarSkirmish StarCraft benchmarkOct. 2 · No harm reported · Control level 2, instruction violation
- In a researcher demo, a hidden email made the Manus agent run attacker code past its prompt-injection guardOct. 1 · No harm reported · Control level 2, instruction violation
- AI coding agents posted 13,000 internal screenshots from over 300 companies to public GitHub repositoriesSept. 29 · Minor harm (counts) · Control level 3, exceeded permissions
Signals that week
- Senators Hawley and Murphy proposed holding AI agent operators and developers liable for hackingOct. 1 · Signal · Policy
- The FTC opened a broad investigation into the safety of Anthropic's and OpenAI's AI systemsSept. 30 · Signal · Policy
- OpenAI released GPT-6.1 Sol, a cheaper model it also rates Critical for cyber capabilitySept. 29 · Signal · Frontier release
- Six AI companies signed a voluntary White House pledge on frontier safeguardsSept. 29 · Signal · Policy
Every week
| Week to | Reading | Change | Band | Reported | Control |
|---|---|---|---|---|---|
| Oct. 5, 2026 | 31 | +2 | Minor harm | 5 | C4reached outside systems |
| Sept. 28, 2026 | 29 | +16 | Minor harm | 9 | C4reached outside systems |
| Sept. 21, 2026 | 13 | +4 | Negligible harm | 5 | C4reached outside systems |
| Sept. 14, 2026 | 9 | +6 | Negligible harm | 2 | C4reached outside systems |
| Sept. 7, 2026 | 3 | -1 | Control failures only | 1 | C3exceeded its permissions |
| Aug. 31, 2026 | 4 | -9 | Control failures only | 0 | C4reached outside systems |
| Aug. 24, 2026 | 13 | -3 | Negligible harm | 0 | C4reached outside systems |
| Aug. 17, 2026 | 16 | -15 | Negligible harm | 0 | C4reached outside systems |
| Aug. 10, 2026 | 31 | — | Minor harm | 1 | C4reached outside systems |
| Aug. 3, 2026 | 31 | -14 | Minor harm | 1 | C4reached outside systems |
| July 27, 2026 | 45 | — | Moderate harm | 1 | C4reached outside systems |
| July 20, 2026 | 45 | +39 | Moderate harm | 1 | C4reached outside systems |
| July 13, 2026 | 6 | +3 | Negligible harm | 2 | C3exceeded its permissions |
| July 6, 2026 | 3 | — | Control failures only | 0 | C3exceeded its permissions |
| June 29, 2026 | 3 | -3 | Control failures only | 1 | C3exceeded its permissions |
| June 22, 2026 | 6 | — | Negligible harm | 0 | C3exceeded its permissions |
| June 15, 2026 | 6 | -14 | Negligible harm | 1 | C3exceeded its permissions |
| June 8, 2026 | 20 | — | Minor harm | 0 | C2broke an instruction |
| June 1, 2026 | 20 | +14 | Minor harm | 1 | C2broke an instruction |
| May 25, 2026 | 6 | -3 | Negligible harm | 1 | C4reached outside systems |
| May 18, 2026 | 9 | -11 | Negligible harm | 0 | C4reached outside systems |
| May 11, 2026 | 20 | -6 | Minor harm | 1 | C4reached outside systems |
| May 4, 2026 | 26 | +6 | Minor harm | 2 | C4reached outside systems |
| April 27, 2026 | 20 | +17 | Minor harm | 1 | C3exceeded its permissions |
| April 20, 2026 | 3 | -3 | Control failures only | 0 | C3exceeded its permissions |
| April 13, 2026 | 6 | — | Negligible harm | 2 | C3exceeded its permissions |
| April 6, 2026 | 6 | -14 | Negligible harm | 0 | C2broke an instruction |
| March 30, 2026 | 20 | — | Minor harm | 0 | C2broke an instruction |
| March 23, 2026 | 20 | — | Minor harm | 1 | C2broke an instruction |
| March 16, 2026 | 20 | — | Minor harm | 0 | C2broke an instruction |
| March 9, 2026 | 20 | -5 | Minor harm | 2 | C2broke an instruction |
| March 2, 2026 | 25 | -1 | Minor harm | 0 | C2broke an instruction |
| Feb. 23, 2026 | 26 | +14 | Minor harm | 4 | C2broke an instruction |
| Feb. 16, 2026 | 12 | +6 | Negligible harm | 2 | C2broke an instruction |
| Feb. 9, 2026 | 6 | +4 | Negligible harm | 1 | C2broke an instruction |
| Feb. 2, 2026 | 2 | -2 | Control failures only | 0 | C2broke an instruction |
| Jan. 26, 2026 | 4 | — | Control failures only | 0 | C4reached outside systems |
| Jan. 19, 2026 | 4 | — | Control failures only | 2 | C4reached outside systems |
| Jan. 12, 2026 | 4 | — | Control failures only | 0 | C4reached outside systems |
| Jan. 5, 2026 | 4 | +2 | Control failures only | 2 | C4reached outside systems |
| Dec. 29, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| Dec. 22, 2025 | 2 | -1 | Control failures only | 1 | C2broke an instruction |
| Dec. 15, 2025 | 3 | -3 | Control failures only | 1 | C3exceeded its permissions |
| Dec. 8, 2025 | 6 | — | Negligible harm | 0 | C3exceeded its permissions |
| Dec. 1, 2025 | 6 | +3 | Negligible harm | 1 | C3exceeded its permissions |
| Nov. 24, 2025 | 3 | +3 | Control failures only | 1 | C3exceeded its permissions |
| Nov. 17, 2025 | 0 | — | No qualifying harm or control failure | 0 | None |
| Nov. 10, 2025 | 0 | -2 | No qualifying harm or control failure | 1 | None |
| Nov. 3, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| Oct. 27, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| Oct. 20, 2025 | 2 | -1 | Control failures only | 0 | C2broke an instruction |
| Oct. 13, 2025 | 3 | — | Control failures only | 1 | C3exceeded its permissions |
| Oct. 6, 2025 | 3 | — | Control failures only | 0 | C3exceeded its permissions |
| Sept. 29, 2025 | 3 | — | Control failures only | 1 | C3exceeded its permissions |
| Sept. 22, 2025 | 3 | +1 | Control failures only | 3 | C3exceeded its permissions |
| Sept. 15, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| Sept. 8, 2025 | 2 | -1 | Control failures only | 0 | C2broke an instruction |
| Sept. 1, 2025 | 3 | — | Control failures only | 2 | C3exceeded its permissions |
| Aug. 25, 2025 | 3 | — | Control failures only | 1 | C3exceeded its permissions |
| Aug. 18, 2025 | 3 | — | Control failures only | 1 | C3exceeded its permissions |
| Aug. 11, 2025 | 3 | — | Control failures only | 2 | C3exceeded its permissions |
| Aug. 4, 2025 | 3 | -6 | Control failures only | 1 | C3exceeded its permissions |
| July 28, 2025 | 9 | — | Negligible harm | 0 | C3exceeded its permissions |
| July 21, 2025 | 9 | +7 | Negligible harm | 2 | C3exceeded its permissions |
| July 14, 2025 | 2 | — | Control failures only | 1 | C2broke an instruction |
| July 7, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| June 30, 2025 | 2 | — | Control failures only | 1 | C2broke an instruction |
| June 23, 2025 | 2 | -1 | Control failures only | 1 | C2broke an instruction |
| June 16, 2025 | 3 | — | Control failures only | 2 | C3exceeded its permissions |
| June 9, 2025 | 3 | — | Control failures only | 0 | C3exceeded its permissions |
| June 2, 2025 | 3 | — | Control failures only | 0 | C3exceeded its permissions |
| May 26, 2025 | 3 | +3 | Control failures only | 4 | C3exceeded its permissions |
| May 19, 2025 | 0 | -2 | No qualifying harm or control failure | 0 | None |
| May 12, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| May 5, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| April 28, 2025 | 2 | -4 | Control failures only | 0 | C2broke an instruction |
| April 21, 2025 | 6 | — | Negligible harm | 2 | C2broke an instruction |
| April 14, 2025 | 6 | +4 | Negligible harm | 1 | None |
| April 7, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| March 31, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| March 24, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| March 17, 2025 | 2 | — | Control failures only | 0 | C2broke an instruction |
| March 10, 2025 | 2 | -1 | Control failures only | 1 | C2broke an instruction |
| March 3, 2025 | 3 | — | Control failures only | 0 | C3exceeded its permissions |
| Feb. 24, 2025 | 3 | -3 | Control failures only | 1 | C3exceeded its permissions |
| Feb. 17, 2025 | 6 | — | Negligible harm | 0 | C3exceeded its permissions |
| Feb. 10, 2025 | 6 | +6 | Negligible harm | 1 | C3exceeded its permissions |
| Feb. 3, 2025 | 0 | – | No qualifying harm or control failure | 0 | None |
| Jan. 27, 2025 | – | – | Unavailable | 0 | None |
| Jan. 20, 2025 | – | – | Unavailable | 0 | None |
| Jan. 13, 2025 | – | – | Unavailable | 0 | None |
| Jan. 6, 2025 | – | – | Unavailable | 0 | None |
Readings are recalculated from the current catalogue; a week shows the value published at the time where one was logged. How the reading is calculated · The reading over time