Octopus, Gecko and Tortoise: the 3 scanners hunting your AI keys
A blog post by Ege Demir reports observations from ten websites run by the author between late September and 18 November 2026.
Source-based brief · Editor review not recorded · See checks and limits ↓
One primary source; other links are context, not independent corroboration.
- Primary sourcetin.computer
- Discovery linkHacker News
- Linked in sourceBook a free 30-minute call with Emre →
- Linked in sourceGreyNoise
- Linked in sourceFastly
- Linked in sourceCequence
- Linked in sourcethe canary path
- Linked in sourceGoogle Cloud’s published ranges
- Linked in sourcedefault list that .NET uses on Linux
- Linked in sourceSANS
- Linked in sourceHoneyLabs
- Linked in sourcea remote code execution bug in Java
- Linked in sourceexploited within hours of disclosure
- Linked in sourcepull request that added Hunyuan and MoonshotBot
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Open full article view →- Community discussion+5
- Fetched source page+30
- No editor link review+0
- Community link+0
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
A blog post by Ege Demir reports observations from ten websites run by the author between late September and 18 November 2026. It describes three scanners: Octopus, which rotates among 32 AI crawler user agents and runs from many short-lived Google Cloud machines; Gecko, a .NET program using a truncated Chrome 128 user agent to request AI tool credential files; and Tortoise, a slow scanner. Octopus is said to browse like a browser before requesting secret paths tailored to each site's framework. The author notes operator identity is not proven.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Based on the author's logs from ten self-run websites over about seven weeks; the operators are not identified and source claims not independently checked.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Based on the author's logs from ten self-run websites over about seven weeks; the operators are not identified and source claims not independently checked.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
Octopus rotates among 32 user agents, seven with undocumented names and 25 copying real AI crawlers, from one machine per website.
Source: tin.computer ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe author recorded 97 Google Cloud machines across 15 regions, with most lasting under an hour.
Source: tin.computer ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseOctopus first browses the site like Chrome, then sends a framework-specific list of about 265 to 385 secret paths.
Source: tin.computer ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseGecko's list of AI tool credential files grew from 4 to 26 paths in five weeks, per the author's logs.
Source: tin.computer ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Based on the author's logs from ten self-run websites over about seven weeks; the operators are not identified and source claims not independently checked.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
A community post points to the original link. Discussion and upvotes do not establish accuracy.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
Site operators may mistake these scanners for legitimate AI crawlers, and the credential paths they target can expose API keys, cloud credentials and AI service tokens if misconfigured.
Limits and open questions
Based on the author's logs from ten self-run websites over about seven weeks; the operators are not identified and source claims not independently checked.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →