AI Risk Wire

Controls

Safeguards kept on in testing

Production classifiers and refusals stay on in evaluations with real access.

Layer L1 Model · Owner Model provider · Family Model safeguards

–Held
–Failed
–Got around
2Missing

By risk

RiskHeldFailedGot aroundMissingNot mentioned
AI used to run a cyber attack––––2
Deception, concealment or sabotage–––12
Gaming the task (reward hacking)–––1–

Why it did not hold

Most common reasonIncidentsExample
Turned off for testing2“these protections were not applied in the evaluation environment running during the incident.”
LR-2026-0004, LR-2026-0003

By quarter

PeriodHeldFailedGot aroundMissing
2025-Q3––––
2025-Q4––––
2026-Q1––––
2026-Q2––––
2026-Q3–––2
2026-Q4––––

Added in reported fixes, and what followed

IncidentDeveloperDateLater incidents where it did not hold
LR-2026-0026
AISI cyber evaluation: Mythos 5 agent exposed locally-hosted attack tooling to the public internet via tunnelling services
Anthropic2026-08-04None on record
LR-2026-0025
AISI cyber evaluation: concurrent Mythos 5 agents coordinated via a shared GitHub account and a leaked access token
Anthropic2026-08-04None on record
LR-2026-0023
AISI cyber evaluation: Mythos 5 agent sent deceptive targeted emails and file transfers to real open-source maintainers
Anthropic2026-08-04None on record

Frameworks

FrameworkItemText
EU GPAI CodeMeasure 3.2To verify when the text is stored