[Corp Blog] Twitter Blue to X Phishing Breakout – Gridinsoft Blogs

Elephant0991@lemmy.bleh.au to Technology@beehaw.org – 32 points – Twitter Blue to X Phishing Breakout – Gridinsoft Blogs
gridinsoft.com

Summary

  • Scammers exploit Twitter's rebranding (transition to name "X") confusion for phishing.
  • Twitter Blue users targeted, offered migration to "X," but scammers gain account access.
  • Phishing emails seem genuine, appearing to come from x.com and passing the Security Policy Framework (SPF), and include deceptive authorization link, opening a legitimate API authorization screen.
  • Clicking link grants attackers control over victim's Twitter account settings and content.
  • Victims can block access by revoking app authorization in Twitter settings.
  • Twitter is aware and "working on a solution."

::: spoiler Article's Safety Recommendations (probably a bit generic and self-promotional)

  1. Being cautious with unfamiliar emails, especially attachments or links.

  2. Verifying URLs by hovering over them.

  3. Not sharing personal info on suspicious/unknown sites.

  4. Be careful with attachments and links.

  5. Using two-factor authentication (2FA) for account security.

  6. Keeping antivirus software updated to prevent malware. :::

Edited based on comment from: @incogtino@lemmy.zip

5

This is a great short analysis, but I think the generic recommendations are a bit strange when tacked onto it

Firstly, who knows what to expect from the Twitter X changeover. If I had a blue subscription I wouldn't not (!) expect to get an email about migrating considering the chaos so far

Then the email is verified as coming from Twitter, and sends you to the genuine Twitter API. No amount of 2FA or antivirus is going to save you here

You're right. Edited.

Cool cool, definitely not criticising, and a great article to post

I think the weakness of the article was mentioning that the email passed the Security Policy Framework (i.e. appeared to legitimately be from x.com) without discussing why this is possible and who is responsible for it not happening

They even say in bold that 'the primary responsibility less with the end user', but in this case even careful users could easily be caught