Looks like it's issuing a GET to https://zelensky.zip/save/{ENCODED_JWT_TOKEN_AND_NAV_FLAG}.
The ENCODED_JWT_TOKEN is from btoa(document.cookie+nav_flag) where nav_flag is essentially 'navAdmin' if the account hit is an admin or '' if the user hit is not an admin (it checks if the admin button in the nav exists). Their server is likely logging all incoming requests and they just need to do a quick decoding to get jwt tokens and a flag telling them if it's an admin account.
I'd be hesitant to visit Lemmy on a browser atm 😓
Sure enough, the .zip TLD is just being used for malicious activity
Lemmy.zip is cool!
Good to know, will look into adding it to the kill-it lists out there. Generally more inclined to rely on dynamic naughty lists but sometimes you just need to cut off the limb if it's 90% rotten.
Google Domains, creating new ways to exploit users right before being sold off to Squarespace.
Can we just hit that domain with junk data and crash their shit?
Yo thanks for the obfuscation. Makes a lot of sense.
Looks like it's issuing a GET to
https://zelensky.zip/save/{ENCODED_JWT_TOKEN_AND_NAV_FLAG}. TheENCODED_JWT_TOKENis frombtoa(document.cookie+nav_flag)wherenav_flagis essentially'navAdmin'if the account hit is an admin or''if the user hit is not an admin (it checks if the admin button in the nav exists). Their server is likely logging all incoming requests and they just need to do a quick decoding to get jwt tokens and a flag telling them if it's an admin account.I'd be hesitant to visit Lemmy on a browser atm 😓
Sure enough, the
.zipTLD is just being used for malicious activityLemmy.zip is cool!
Good to know, will look into adding it to the kill-it lists out there. Generally more inclined to rely on dynamic naughty lists but sometimes you just need to cut off the limb if it's 90% rotten.
Google Domains, creating new ways to exploit users right before being sold off to Squarespace.
Can we just hit that domain with junk data and crash their shit?
Yo thanks for the obfuscation. Makes a lot of sense.