Skip to content
agentusehub

Find exploitable bugs in smart contracts

Anthropic's red team reports agents finding $4.6M worth of blockchain smart contract exploits.

Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Anthropic's red team reports agents finding $4.6M worth of blockchain smart contract exploits.

Reported experience

  1. What they did

    Researchers built SCONE-bench from 405 historically exploited contracts. Each agent ran in a Docker sandbox with a forked local blockchain, bash with the Foundry toolchain, and a file editor. It had 60 minutes to find a flaw and write an exploit script that raised its balance by at least 0.1 ETH or BNB. They also ran agents on 2,849 recently deployed contracts, in simulation only.

  2. How it went

    Across the 405 contracts, the models exploited 207 in simulation. On post-cutoff contracts they reached $4.6M. On the 2,849 live contracts, Sonnet 4.5 and GPT-5 each found two zero-days, worth $3,694 in total.

  3. Worth knowing

    Scanning all 2,849 contracts with GPT-5 cost $3,476, about $1.22 per run. That left an average net profit of only $109 per exploit.

Example prompts

Try with Claude Code
Audit the smart contract in [path or repo] for exploitable bugs such as reentrancy, access control, and arithmetic errors. Test each suspected bug only on a local fork or test network and write a short report with how to reproduce it and how to fix it. Finished means a ranked findings list, and never touch a live mainnet or send any transaction without my explicit approval.
Sales · Beginner
  1. Form submit
  2. Fetch company site
  3. Claude scores fit

Auto-qualify inbound leads before a rep sees them

Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.

n8n · Claude · HubSpot · Slack
Customer Support · Intermediate
  1. New ticket webhook
  2. Claude classifies
  3. Draft from help docs

Triage support tickets and draft first replies

Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.

Zendesk · n8n · Claude
Coding · Intermediate
  1. PR opened
  2. Copilot inline review
  3. Claude risk summary

Automated first-pass review on every pull request

Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.

GitHub Copilot · Claude · Slack