Every Octopus visit starts the same way:
- 01
The canary/z9x8c7v6b5-debug-trigger-<your hostname>
- 02
Two random paths/gubgyjrd34ipmzr98uwq
- 03
About 300 secret filesin about 10 seconds, each with a different crawler name
The two random paths always get a 404. Octopus probably uses them to learn what your site sends for a missing page. Then it can tell a real .env file from a page that says “not found” with a 200.
On each request, Octopus picks one of 32 user agents at random. Seven of them use names that no company documents:
The other 25 copy real crawlers, mostly letter for letter:
A typical one reads Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; GPTBot/1.4; +https://openai.com/gptbot. All 32 come from one machine, on one connection, within seconds. No real crawler does that.
- Accept
- */*
- Accept-Encoding
- gzip
- TLS
- the same handshake as Chrome
- Redirects
- follows them, keeps the user agent, adds a Referer
- Network
- Google Cloud, AS396982, *.bc.googleusercontent.com
Its handshake is the same as Chrome’s. It follows redirects, keeps the user agent and adds a Referer. That is how Go’s standard HTTP client behaves. We think Octopus is a Go program with a Chrome-like TLS library.
Other site owners have seen it. GreyNoise, Fastly and Cequence reported scanners with fake AI crawler names on Google Cloud, and the canary path is in public logs from September. On our sites it started on 3 October. Until 16 October it used 23 or 24 names, including PanguBot/1.0, YiBot/1.0 and MistralAI-User. It then went to 32.