hn.today

Octopus, Gecko and Tortoise: the 3 scanners hunting your AI keys

tin.computer27 points6 comments
Screenshot of Octopus, Gecko and Tortoise: the 3 scanners hunting your AI keys

A 50-day examination of traffic to ten websites identifies three scanners probing for exposed AI credentials and other secrets. Octopus disguises requests as 32 legitimate and invented AI crawler names, changing its user agent on every request. It first visits sites like a browser, reading pages, robots.txt, sitemaps and build manifests; it then selects framework-specific paths, including .env files, cloud credentials, AI gateway endpoints and deployment configurations. Its 97 Google Cloud machines spanned 15 regions, usually scanning one site and disappearing within an hour, so blocking individual addresses offers little protection. Its canary path, /z9x8c7v6b5-debug-trigger-, is a distinctive log clue.

Gecko uses a different approach: a .NET program sends roughly 200 requests in a fixed sequence, with a Chrome user agent truncated after 60 characters. Mostly based in Google Cloud’s Belgium region, it has expanded its targets from Claude Code settings to MCP configurations and credentials for Codex, Gemini CLI, Cursor and other coding agents; its list grew from four to 26 paths in five weeks. Tortoise is described as a smaller, slower scanner, identifiable by a different canary path and occasional Chrome-on-Windows requests. The evidence points to separate operators behind Octopus and Gecko, but does not establish who they are. The findings show why crawler-name filters alone miss scans and why logs should be checked for browser-like reconnaissance and requests to sensitive paths.

Read on tin.computer6 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.