🚨 Allegations of DDoS Abuse Inside archive.today: How a Major Archive Site Was Used to Flood Blogs

🚨 Allegations of DDoS Abuse Inside archive.today

Multiple independent reports have raised alarms about JavaScript running on archive.today pages that repeatedly generate outbound requests targeting specific blogs. Security researchers and affected site owners describe this behavior as DDoS-like traffic amplification.

⬆ Read up / jump to section 1. The malicious request pattern 2. Why this qualifies as DDoS behavior 3. Why this is shocking on a major archive site 4. Reported allegations about the anonymous operator 5. Safe simulation of repeated request attack Sources & evidence

1️⃣ The malicious request pattern

Captured screenshots and videos show JavaScript repeatedly generating URLs like: 

https://gyrovague.com/?s=randomString

The random query parameter defeats caching and forces the target server to process every request — a known DDoS technique.

2️⃣ Why this qualifies as DDoS behavior

When executed every ~300ms, even a single page can generate 3+ requests per second. At scale — across thousands of visitors — this becomes sustained denial-of-service traffic.

Importantly, visitors may not realize their browser is being used as a traffic generator.

3️⃣ Why this is shocking on a major archive site

archive.today is one of the largest archival platforms on the internet, used by journalists, researchers, and courts. Hosting behavior consistent with DDoS techniques inside such a service is deeply concerning.

4️⃣ Reported allegations about the anonymous operator

According to public discussions and leaked correspondence, the operator of archive.today:

  • Is reportedly an anonymous individual based in Russia
  • Has been accused (by affected parties) of blackmail and harassment
  • Is alleged to have threatened defamatory content unless demands were met

These claims are allegations reported by third parties and documented in public threads and leaked messages. Readers are encouraged to review primary sources directly.

🧪 Simulation of repeated request attack (SAFE)

Below is a visual-only simulation. It does NOT send real requests. It shows how the traffic would look if the JavaScript were active.

300ms
Total requests: 0

📚 Sources & evidence

  • Gyrovague investigation
  • Hacker News discussion
  • Lobsters thread
  • Reddit DataHoarder thread
  • YouTube recordings demonstrating JavaScript execution
Why this matters: If proven accurate, this represents a serious abuse of trust by a critical internet infrastructure service.

Comments

Post a Comment