archive.today Targeted for DDoS Allegations: Russian Scripts, Wikipedia Edits, and the uBlock Origin Patch Exposed
Multiple users allege the web archiving service archive.today facilitates malicious activity, including suspected DDoS attacks targeting sites like gyrovague.com. Specific claims point to the service executing JavaScript on CAPTCHA pages and incorporating pixels and scripts from Russian domains such as mail.ru and vk.com.
The community is sharply divided. One side, led by 'A_norny_mousse' and citing ArsTechnica, claims archive.today is actively manipulating captured content, even altering snapshots to insert blogger names. The opposition, including 'whaleross', expresses deep distrust, questioning the evidence or arguing that the accuser might be overstating the threat. Meanwhile, 'nullroot' provided a technical workaround: the uBlock Origin filterlist was updated to specifically block the alleged attack mechanism.
The raw takeaway is that while there is a concrete technical mitigation—an updated uBlock Origin filterlist—the fundamental debate remains unclosed. The weight of allegations centers on systemic misuse of the archiving tool for hostile actions, while strong counterpoints challenge the evidence and the sheer accusation itself.
Key Points
archive.today executes suspicious JavaScript and loads scripts from Russian domains.
'A_norny_mousse' claims this serves to spread IP information and execute attacks via user proxies.
The service allegedly manipulates captured webpages to target individuals.
Citations from ArsTechnica suggest archive.today alters snapshots to insert the name of the blogger under attack.
The attack mechanism has a documented technical countermeasure.
'nullroot' reported that the uBlock Origin filterlist was specifically updated to block the alleged DDoS vectors.
Skepticism surrounds the core accusations of malicious activity.
'whaleross' expresses blanket distrust, suggesting the evidence of covert DDOS attacks might be overstated.
Discussions reference alternative archiving solutions.
Users suggest alternatives like archive.org, ghostarchive.org, or self-hosting options, bypassing the central dispute.
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.