Level 3. Significant control incident
AI-Assisted Commit Enables North Korean Malware Attack on Crypto Trading Agent
- Developer
- Not established
- Model
- Not established
- When it happened
- April 29, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by oecd.ai. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 3 of 5Significant control incident
- Potential
- 3 of 5Significant control incident
An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- An external system was affected. Argues for level 3
- Sensitive data was reachable. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
An external system was affected
The article explicitly states that the AI model (Claude Opus) made a malicious npm package a dependency, which gave hackers access to users' crypto wallets and funds.
AI-Assisted Commit Enables North Korean Malware Attack on Crypto Trading AgentSensitive data was reachable
The malware, linked to North Korean group Famous Chollima, enabled theft of crypto assets and sensitive data, demonstrating direct harm caused by AI-assisted software development.
AI-Assisted Commit Enables North Korean Malware Attack on Crypto Trading Agent
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 19, 2026
AI-Assisted Commit Enables North Korean Malware Attack on Crypto Trading AgentA structured incident database · read September 18, 2026
AI Agent Incident Database by sipi.bot (CC BY 4.0)
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.