logoalt Hacker News

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

27 points • by demegire • yesterday at 6:53 PM • 6 comments • view on HN

Comments

mormegil • yesterday at 10:45 PM

Whenever I see similar scanning in my server logs, I feel the urge to... provide them with same fake/poisoned credentials to... well, that's the problem. There is no way to hurt those. Usually I report the scan to Google (as they most often come from GCP IPs), but never hear back and it's not like it would stop them (it's some stolen cards or Google accounts, anyway, right?). It's just... it offends me there is no way to fight back.

AMerrit • yesterday at 7:06 PM

Interesting that in some cases they are using the AI Agent crawler names to hide themselves. With the explosion in bot traffic it gets much easier to hide yourself in the crowd.

nerdralph • yesterday at 10:19 PM

Some useful information, though I'd like more details on headers sent like Sec-Fetch.

For passive blocking, TLSv1.3 filters out some bad bots and scrapers.

Most bad bots follow 302 redirect, but don't parse html and act on meta refresh.

Most bad bots don't store cookies, but I've seen a couple that do.

flockonus • yesterday at 9:35 PM

I wonder if Cloudflare blocks it through their default protection?

I'm ok with having agents / LLMs reading my site, but not happy about scanners.

seethishat • yesterday at 11:10 PM

Welcome to the Internet.

486sx33 • yesterday at 11:28 PM

[dead]