4 comments

[ 2.1 ms ] story [ 15.7 ms ] thread
Hmm, I wonder where the Twitter/X employees who would've seen this coming went?
Someone's also purchased setwitter.com to prevent the same attack on another obvious domain
A famous shipping company's fake page redirects to someone's blog
I feel like a lot of the time when I see vulnerabilities I am in awe of the ingenuity of malicious hackers to exploit very precise issues in a codebase.

This time I'm just amazed how anyone could fail to see this coming.

It's nice that Netflix.com is protected, but this is a potential phishing attack (or links just won't work) for any website ending in x?!