Level 3. Significant control incident
Clawdbot (Moltbot): When "Easy AI" Becomes a Security Nightmare
- Developer
- Not established
- Model
- Not established
- When it happened
- January 27, 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 intruder.io. 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
- Significant data was exposed. Argues for level 3
- The system acted without authorisation. Argues for level 2
- Sensitive data was reachable. Argues for a potential level of 3
What is established, and what is not
Confirmed
Significant data was exposed
We've confirmed multiple instances where attackers extracted API keys, email content, and internal system information through social engineering of the AI itself.
Clawdbot (Moltbot): When "Easy AI" Becomes a Security Nightmare
Reported, not confirmed
Sensitive data was reachable
Some exposed panels allowed retrieval of API keys, conversation histories and, in certain deployments, unauthenticated command execution that could enable remote code execution.
Clawdbot/Moltbot exposed admin dashboards enabled unauthenticated RCE and data leaksThe system acted without authorisation
We're observing instances performing unintended actions including unauthorized posting, data exfiltration, and execution of commands beyond user intent.
Clawdbot (Moltbot): When "Easy AI" Becomes a Security Nightmare
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 October 5, 2026
Clawdbot (Moltbot): When "Easy AI" Becomes a Security NightmareA structured incident database · read September 19, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it
Clawdbot/Moltbot exposed admin dashboards enabled unauthenticated RCE and data leaksWhere we first saw it
Clawdbot becomes Moltbot, but can’t shed security concernsWhere we first saw it
Moltbot security alert exposed Clawdbot control panels risk credential leaks and account takeovers
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.