archive.today Allegedly Used a CAPTCHA Script to Flood a Blog — February 2026

A technical summary, safe simulation, timeline, and source hub. Claims below are reported and linked to primary materials. :contentReference[oaicite:1]{index=1}

Summary

The reported incident (Feb 2026)

Public reporting states that archive.today’s CAPTCHA page ran a small client-side script that repeatedly attempted requests to a specific blog’s search endpoint every ~300 milliseconds, constructing randomized query strings so responses would not be cached. The original investigator published the code snippet and screenshots. :contentReference[oaicite:2]{index=2}

These are allegations drawn from public reporting and community threads — consult the Sources section for the original materials. :contentReference[oaicite:3]{index=3}

Safe simulation

Visual-only demonstration of the reported request pattern (no network calls).

Requests/sec
0.00

Total requests
0

Interval

[Simulation log — simulated GET lines appear here]

Tip: this is a safe visualization that replicates the visible request pattern reported in the sources. :contentReference[oaicite:4]{index=4}

Technical explanation (plain English)

The reported code uses `setInterval` to run repeatedly. Each iteration builds a URL such as: https://gyrovague.com/?s=<random-string> and attempts to fetch it. Randomizing the query defeats caches, so the target server must compute a fresh response on each request — consuming CPU, memory, and I/O. :contentReference[oaicite:5]{index=5}

If many visitors simultaneously run the code, the aggregated load can overwhelm small or lightly provisioned blogs; in practice this becomes DDoS-like behavior even though the requests originate from unmodified browsers.

Timeline & community response

The investigation and timeline were discussed widely on Hacker News and Reddit, where community members inspected the code, screenshots and correspondence and debated attribution and mitigation. :contentReference[oaicite:6]{index=6}

Sources

• Gyrovague — original investigation (code snippet & timeline). :contentReference[oaicite:7]{index=7}
• Hacker News discussion. :contentReference[oaicite:8]{index=8}
• Reddit /r/DataHoarder thread. :contentReference[oaicite:9]{index=9}