✨Live from Studiopolis Zone!! 📷✨

hapisan:

hapisan:
rachaelmayo:
elfgrove:
elfgrove:
New Things to Beware on the Internet
On May 3rd, Google released 8 new top-level domains (TLDs) – these are new values like .com, .org, .biz, domain names. These new TLDs were made available for public registration via any domain registrar on May 10th.
Usually, this should be a cool info, move on with your life and largely ignore it moment.
Except a couple of these new domain names are common file type extensions: “.zip” and “.mov”.
ALT
This means typing out a file name could resolve into a link that takes you to one of these new URLs, whether it’s in an email, on your tumblr blog post, a tweet, or in file explorer on your desktop.
What was previously plain text could now resolve as link and go to a malicious website where people are expecting to go to a file and therefore download malware without realizing it.
Folk monitoring these new domain registrations are already seeing some clearly malicious actors registering and setting this up. Some are squatting the domain names trying to point out what a bad idea this was. Some already trying to steal your login in credentials and personal info.
ALT
ALT
ALT
ALT
ALT
This is what we’re seeing only 12 days into the domains being available. Only 5 days being publicly available.
What can you do? For now, be very careful where you type in .zip or .mov, watch what website URLs you’re on, don’t enable automatic downloads, be very careful when visiting any site on these new domains, and do not type in file names without spaces or other interrupters.
I’m seeing security officers for companies talking about wholesale blocking .zip and .mov domains from within the company’s internet, and that’s probably wise.
Be cautious out there.
I really want to reiterate how this can go wrong frequently and fast, folks.
A malicious actor sets up a page with an auto-downloader squatting on a domain name that matches a common zip file name like photos DOT zip. This website is set up to start an auto downloader upon being visited, downloading a zip file with the same name as the URL which contains malicious software (virus, worm, keylogger, etc).
Scenario.
Someone you know well sends you an email or text with promised photos attached. The email even reads something like this.
Because .zip is now a TLD, that plain text is automatically formatted into a link to malicious actor’s website without them having to send you anything.
Folk with family with iPhones or iPads that are sent multiple photos in one go might be familiar with iCloud’s tendency to automatically compile them into zip file for the sender and less savvy tech users have trouble NOT doing that.
These same less savvy users, or even just someone just not thinking in the moment, will click that .zip link, not realizing it isn’t the the same as clicking on the promised attachment.
They download a file that matches the name they expected. They open it because they were expecting that file and it’s from a trusted source. Except the file they downloaded isn’t the one that was sent by their trusted source and now they have malware.
Another Scenario.
An IT person tries to send you an email with instructions on how to resolve a problem with a commonly used filename like install-repair DOT zip or to install new software like microsoft-office DOT zip.
The email may start with instructions of where to go get the legitimate file to do the install or repair, but now a line later in the instructions is also has a link to a .zip URL. A user, already frazzled by IT problems, may click it to ensure they have the right file. Again, they download malicious code from a squatting website or it prompts them with a fake login and now the squatting website has stolen their login credentials for a legitimate site. All due to an expected email from a trusted source.
Above you can see microsoft-office DOT zip is already out there with a fake Microsoft login screen waiting to steal your credentials.
These risks are already out there now because the TLD has been activated.
Plain text on old post are already being resolved into links to the new websites.
Here you can see a tweet from 2021, long before .zip was a domain name, now resolves that plan text into a clickable link. You’ll start seeing this everywhere, and malicious actors do not have to lift a finger to send it to you.
Yes, a lot of users aren’t going to click that, but a lot of folk will. Whomever is squatting on photos DOT zip domain name has made a one time payment to have access to anyone that ever sees that file name typed out.
In an example of an existing squatter site, clientdocs DOT zip is exactly one such pre-setup .zip domain name that initiates an automatic download. This one may be harmless, but the set ups are already out there and waiting to catch folk.
It’s an unnecessary and risky can of worms that’s been opened up.
Holy Unforced Errors, Batman.
Critical intel.
One of the examples above, familyphotos[dot]zip, also actually exists as a warning site to this exact thing. It autodownloads a zip file, containing a single text file, labelled “what_happened.txt”:
“Hey, this isn’t family pictures!”

You’re right – and that link you clicked wasn’t a file attached to the email or message you received.

Thanks to Google[0][1], now it’s impossible to discern the difference between a link to an attachment called “familyphotos.zip” and a link to this file… unless you are able to inspect the destination of a link before clicking it. Most software and apps don’t allow that, and most people don’t know how to tell the difference anyway.

Have fun in the Wild Wild Web!

[0]: https://www.blog.google/products/registry/8-new-top-level-domains-for-dads-grads-tech/
[1]: https://twitter.com/Google/status/1653866291692728320
Just.. how did anyone think a .zip TLD was a good idea? Just less than a minute of thinking it through would reveal how absolutely ridiculous it is.
The Dangers of Google’s .zip TLD
Can you quickly tell which of the URLs below is legitimate and which one is a malicious phish that drops evil.exe?
Medium
Something else to be aware of beyond autolinking, as with some clever use of an @ and unicode slashes near-indistinguishable from normal said fake URLs can be longer too. Yikes.