Home/ Incident database/clawdbot-1m-2025-10
Financial loss Trading agent failure unverified

Clawdbot trading agent reportedly loses $1,000,000

Clawdbot (open-source project) · Oct 1, 2025 · Trading agent

What happened

Clawdbot, an open-source trading-agent side project that briefly rocketed to 60,000+ GitHub stars, reportedly lost approximately $1,000,000 while operating autonomously as a trading agent.

$1M
Loss / impact
Oct 1
2025
Trading
Failure mode
Trading
Agent type

Causal vector

Autonomous trading execution without adequate risk controls or kill-switch

Source

Reported by Developer-community posts. Sourced from a secondary summary; flagged pending a stronger primary source.

Read the original report ↗

How a spend firewall would have helped

A daily total cap and a drawdown velocity rule (‘stop trading after X% loss in Y minutes’) act as the kill-switch an autonomous trader must hit. Without an external gate, the agent loops until the account is empty.

The six rule types that contain this class of failure

Per-transaction cap

Any single spend above your ceiling is BLOCKED before it moves.

Daily total

Cumulative spend across all agent calls, bounded per day.

Velocity limit

Stops runaway retry loops — the #1 cause of overnight losses.

Merchant allowlist

Only approved destinations can ever receive funds.

Category rules

Flag high-risk classes (crypto, infra, refunds) for review.

Approval threshold

Above a value, the action waits for a human.

Related incidents

AI trading bot misreads tweet, sends $441K of tokens to a stranger

anonymous (OpenAI employee side project) · Oct 1, 2025

Don't be the next entry

Every incident in this database is the result of trusting a prompt, a provider cap, or a human review cycle. sipi.bot replaces all three with one deterministic call. 27 documented failures, one control.