Here’s a quick bash script if anyone wants to help flood the attackers with garbage data to hopefully slow them down: while true; do curl https://zelensky.zip/save/$(echo $(hostname) $(date) | shasum | sed ‘s/.{3}$//’ | base64); sleep 1; done
Once every second, it grabs your computer name and the current system time, hashes them together to get a completely random string, trims off the shasum control characters and base64 encodes it to make everything look similar to what the attackers would be expecting, and sends it as a request to the same endpoint that their xss attack uses. It’ll run on Linux and macOS (and windows if you have a WSL vm set up!) and uses next to nothing in terms of system resources.
It’s essentially to add a unique salt to each machine that’s doing this, otherwise they’d all be generating the same hash from identical timestamps. Afaik, sha hashes are still considered secure; and it’s very unlikely they’d even try to crack one. But even if they did try and were successful, there isn’t really anything nefarious they can do with your machines local name.
A butterfly effect is the phenomeon that a small change in initial conditions that leads to a significantly different result than if the initial conditions haven’t been changed. Have you personally witnessed such phenomeon?...
Lemmy.world is down because of a DDOS attack (lemmy-world.statuspage.io)
What are these comments on lemmy posts? (lemmy.sdf.org)
Are they just an issue with wefwef or trying to use an exploit
What butterfly effect have you personally witnessed?
A butterfly effect is the phenomeon that a small change in initial conditions that leads to a significantly different result than if the initial conditions haven’t been changed. Have you personally witnessed such phenomeon?...