Octopus, Gecko and Tortoise: the scanners hunting your AI keys · Ege Demir, Tin Analytics · tin.computer, November 18, 2026
Scanners now ask websites for coding agents' credential files
Tin Analytics watched ten websites it runs from late September to November 18 and describes three scanners. The one it calls Gecko asked for Claude Code's settings files on its first visit on September 30, then added MCP configs in late October and, on November 12 and 13, /.claude/.credentials.json, /.codex/auth.json and /.gemini/settings.json. By the company's count its AI tool paths went from 4 on October 16 to 26 on November 17, about 10% of its requests that week. A second scanner, Octopus, rotates through 32 AI crawler names, 25 of them copied from real crawlers such as GPTBot and ClaudeBot, and rented 97 Google Cloud machines in 15 regions, most of them gone within an hour. The post says it has not proven who runs them, and that the evidence points to two operators.
The post names three ways these files end up public: a build that copies the whole project into its output, a container serving the wrong folder, or a committed .claude/settings.local.json. It gives log signatures, Cloudflare and nginx rules, and a checklist: request your own secret paths and expect a 404, keep agent credential files out of Git, and put MCP server keys in environment variables rather than mcp.json. The figures are the company's own log observations, and the post carries pitches for its analytics product.
Why it matters: Agent setups create credential files in project and home folders that most deploy checklists were not written to catch. Blocking crawler names will not help, because the scanners change names; the fix is making sure those files are never served.