this post was submitted on 09 Aug 2023
34 points (100.0% liked)

Technology

37724 readers
487 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
Los@beehaw.org
coldredlight@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
34
[Corp Blog] Twitter Blue to X Phishing Breakout – Gridinsoft Blogs (gridinsoft.com)
submitted 1 year ago* (last edited 1 year ago) by Elephant0991@lemmy.bleh.au to c/technology@beehaw.org
6 comments fedilink hide all child comments
 

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."

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

you are viewing a single comment's thread
view the rest of the comments
[–] incogtino@lemmy.zip 7 points 1 year ago (1 children)

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

[–] Elephant0991@lemmy.bleh.au 2 points 1 year ago (1 children)

You're right. Edited.

[–] incogtino@lemmy.zip 6 points 1 year ago

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