Repo of the Day
tracebit-com/turingpot
Published: Nov 21, 2026
Open repository ↗An open-source AI agent honeypot proof of concept for investigating ARTEX and other autonomous offensive frameworks (AOFs)
Summary
TuringPot is an open-source JavaScript proof-of-concept honeypot for investigating ARTEX and other autonomous offensive frameworks (AOFs). It presents visitors with calculation puzzles, records how quickly they solve them, and emits events such as possible_ai_agent and pagination_sequence_completed. The resulting source IP, time window, and sometimes JA4 fingerprint are leads for threat hunting, not proof that an autonomous agent caused the activity.
What it is useful for
Use TuringPot when you suspect an autonomous offensive framework is investigating your organization and want a signal your team can investigate. Its default configuration serves stock puzzles at /api/inventory: a visitor might be asked which stock bin holds the most available units, and each correct answer unlocks the next puzzle. A human, an AI agent, or a purpose-built script can solve these, so fast, correct progress is a heuristic rather than attribution.
By default, the third correct answer logs possible_ai_agent, and the twelfth logs pagination_sequence_completed; both include elapsed time and the same session ID. The logs can provide source_ips, user_agents, ja4, first_seen, last_seen, hostname, and checkpoints. Engineers can search those values in WAF, API-gateway, authentication, or other service logs, then check the user agent and request history before grouping activity.
The project is also a practical template for changing the puzzle mix, endpoint, instructions, and signal thresholds. The README notes two important limits: the false-positive rate on real traffic is unknown, and an agent may recognize a stock TuringPot deployment and skip it.
How engineers can use it
Clone the repository and use Node.js 22.12 or later. From the project directory, run:
npm ci
npm run dev
Open the local URL printed by Wrangler and follow Access inventory. The first puzzle’s HTTP 409 response is intentional. Run npm test for the protocol and hosting-adapter tests.
For Cloudflare Workers Free, the documented deployment flow is npx wrangler login followed by npm run deploy. On Vercel, import the repository, select the Other framework preset, and deploy with the included vercel.json. Give the honeypot a reason to be found—for example, use a relevant subdomain of the domain you think is targeted and leave a breadcrumb from the main site—then search Observability → Logs on Cloudflare or Runtime Logs on Vercel for the event names.
You can edit default.json to change the endpoint, puzzle types (allocations, journal, or extents), and thresholds from 1 to 20. A new puzzle type must be registered in src/manifest.js. Cloudflare Workers Free returns an empty ja4 list; Cloudflare Enterprise with Bot Management and Vercel on all plans can supply the fingerprint, so treat IP and timing evidence as the portable starting point.