AI Risk Wire

Risks

Unauthorised transactions or spend

An agent pays, trades, orders or commits money nobody authorised.

NIST AI 600-1 · No exact NIST AI 600-1 categoryFSB agentic AI consultation (2026)OWASP Agentic ASI02

5incidents (primary) · 5 more as secondary
1read for controls · 4 not yet
1fixes reported
0repeats after a fix

Incidents per week

No rise: 0 in the week of 26 Oct 2026, against an average of 0.2 over the 4 weeks before.

Week of 10 Aug 2026: 0Week of 17 Aug 2026: 0Week of 24 Aug 2026: 0Week of 31 Aug 2026: 11Week of 7 Sep 2026: 0Week of 14 Sep 2026: 0Week of 21 Sep 2026: 0Week of 28 Sep 2026: 0Week of 5 Oct 2026: 0Week of 12 Oct 2026: 11Week of 19 Oct 2026: 0Week of 26 Oct 2026: 0Week of 2 Nov 2026: 0 10 Aug17 Aug24 Aug31 Aug7 Sep14 Sep21 Sep28 Sep5 Oct12 Oct19 Oct26 Oct2 Novto date

Developers

OpenAI · 1

Where the chain broke

Part of the systemIncidents where the control was not effective or did not existIncidents where the control was effectiveIncidents where sources don't mention the controlIncidents not yet checked for controls
L1 Model
Model provider
14
L2 Harness
Agent framework vendor
14
L3 Application
Deployer
14
L4 Infrastructure / target
Organisation hit
14

Controls for this risk, by layer

ControlIncidents where the control was not effective or did not existIncidents where the control was effectiveIncidents where sources don't mention the controlMost common reason it was not effective
Separate identity for each agent
L3 Application
1
Rate and spend limits
L3 Application
1
Payment mandates and transaction limits
L3 Application
1
Human approval for high-impact actions
L3 Application
1
Undo for agent actions
L3 Application
1
Alerts on unusual tool use
L3 Application
1
Out-of-band verification of payment and identity requests
L4 Infrastructure / target
1

7 of 7 controls for this risk not yet recorded as effective.

Fixes reported and what followed

IncidentControl added by the fixIncidents after the fix
LR-2026-0793 2026-10-16 · OpenAI
Fix reported
Not tied to a controlNo repeat on record
LR-2026-0606 2026-05-09
Advice in source, not a fix by the party
Not tied to a control

Incidents

EffectiveNot effectiveNot effective (bypassed)Did not existNot stated in sourcesNot yet checkedAttacker's ownOrder: model · harness · application · target

Also under this risk as a secondary risk: LR-2026-0273, LR-2026-0648, LR-2026-0545, LR-2026-0501, LR-2026-0422