(4 DAYS BEFORE SUBMISSIONS CLOSE) I get this question a lot about the Find Evil! hackathon: What does “find evil” actually mean?
In this case, the name comes from a real command. I built an autonomous incident response agent I built on the SIFT Workstation.
Then I typed “find evil” as a prompt into Claude Code.
And it did (watch the demo). I was blown away to watch the autonomous agent run a complete C drive forensic analysis, across 200 tools via MCP.
The agent identified threat actor and context, the attack chain, malware deployment method, persistence mechanisms, code injection analysis, network connections, command-and-control (C2) infrastructure, a complete malicious process tree, and a chronological activity timeline.
Two days after I shared initial findings, Anthropic released their report on how threat actors were deploying Claude Code with operational tools and letting it go do evil. (Same thing I was doing.)
Find Evil! is the first hackathon dedicated to building autonomous AI agents for incident response.
4,178 defenders are working on final Find Evil! hackathon submits. (This number makes me very happy to see so many diving in. And wishing that the thousands more in our community were experimenting with us.)
Your job: teach an AI agent to think like a senior analyst, how to sequence its approach, recognize when something doesn’t add up, and self-correct when it gets it wrong.
There are FOUR DAYS left to build with us! (Very few of us are actual AI experts. The rest of us including me are learning.) Register:
findevil.devpost.com
Apply to judge: We need DFIR, AI, cybersecurity, and open-source reviewers who can separate useful autonomous response tools from polished demos. Apply:
findjudges-9kvkxt6m.manus.sp…
I am SO EXCITED to see what comes out of this hackathon and goes back to the community.
Sponsored by
@SANSInstitute