Level 3. Significant control incident
Ethereum core dev’s crypto wallet drained by malicious AI extension
- Developer
- Not established
- Model
- Not established
- When it happened
- September 1, 2024
- 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 tradingview.com. 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
- Limited data was exposed. Argues for level 2
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
An external system was affected
The plugin “read my .env file” and sent the key to an attacker’s server, giving access to a hot wallet for three days before funds were drained on Sunday, he said.
Ethereum core dev’s crypto wallet drained by malicious AI extensionLimited data was exposed
The developer installed the “contractshark.solidity-lang” that appeared legitimate with a professional icon, descriptive copy and more than 54,000 downloads, but it silently exfiltrated his private key.
Ethereum core dev’s crypto wallet drained by malicious AI extension
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
Ethereum core dev’s crypto wallet drained by malicious AI extensionA 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.