Wednesday, February 19, 2025
HomeCyber Security NewsSEC X Account was Hacked Using SIM Swapping Method

SEC X Account was Hacked Using SIM Swapping Method

Published on

SIEM as a Service

Follow Us on Google News

In a brazen act of digital deception, the U.S. Securities and Exchange Commission’s (SEC) official Twitter account, @SECGov, was compromised on January 9th, 2024. 

This wasn’t just a prank; it sent shockwaves through the financial world, momentarily igniting a frenzy of cryptocurrency trading fueled by a fake announcement of Bitcoin ETF approval. 

Unpacking the details of this incident reveals a story of vulnerability, swift action, and ongoing investigations.

Document
Free Webinar

Fastrack Compliance: The Path to ZERO-Vulnerability

Compounding the problem are zero-day vulnerabilities like the MOVEit SQLi, Zimbra XSS, and 300+ such vulnerabilities that get discovered each month. Delays in fixing these vulnerabilities lead to compliance issues, these delay can be minimized with a unique feature on AppTrana that helps you to get “Zero vulnerability report” within 72 hours.

Timeline of a Tweet-Jacking:

  • 4:00 PM ET: The unthinkable happens – an unauthorized party gains control of the @SECGov account.
  • 4:11 PM ET: A tweet claiming the SEC’s approval of spot Bitcoin ETFs appears, sending the crypto market into a speculative whirlwind.
  • 4:13 PM ET: Another cryptic tweet simply reads “$BTC,” further amplifying the confusion.
  • 4:26 PM ET: The SEC, alerted to the breach, issues a public statement via Chair Gary Gensler’s Twitter, notifying everyone of the unauthorized activity and clarifying that no such Bitcoin ETF approval exists.
  • 4:40-5:30 PM ET: The compromised access is finally terminated, but the damage is done.

Investigations, still ongoing, point towards a “SIM swap” attack, where the hacker tricked the phone carrier associated with the @SECGov account into transferring its number to a new device, thereby gaining control of the account’s password reset process.

This highlights a critical security lapse, as two-factor authentication (MFA) was surprisingly disabled at the time despite being standard practice.

Anatomy of a Response:

Amidst the chaos, the SEC’s swift response is commendable. 

They alerted the public promptly, deleted the false tweets, and engaged in damage control. 

Collaboration with law enforcement agencies like the FBI and the SEC’s own Office of Inspector General demonstrates a commitment to a thorough investigation.

Katie Moussou, Founder of Luta Security, said, “The ease with which the hackers bypassed safeguards underscores the need for multi-layered security protocols, including hardware tokens for MFA and stricter identity verification processes with phone carriers.”

The @SECGov hack raises vital questions:

  • How did the hacker breach the phone carrier’s security?
  • Was any other SEC data compromised?
  • Should social media ever be relied upon for official announcements?
Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Russian Hackers Target Signal Messenger Users to Steal Sensitive Data

Russian state-aligned threat actors have intensified their efforts to compromise Signal Messenger accounts, targeting...

Hackers Exploit Jarsigner Tool to Deploy XLoader Malware

Security researchers at AhnLab Security Intelligence Center (ASEC) have uncovered a new campaign leveraging...

Hackers Converting Stolen Payment Card Data into Apple & Google Wallets

Cybercriminal groups, primarily based in China, are leveraging advanced phishing techniques and mobile wallet...

Snake Keylogger Targets Chrome, Edge, and Firefox Users in New Attack Campaign

A new variant of the Snake Keylogger, also known as 404 Keylogger, has been...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Russian Hackers Target Signal Messenger Users to Steal Sensitive Data

Russian state-aligned threat actors have intensified their efforts to compromise Signal Messenger accounts, targeting...

Hackers Exploit Jarsigner Tool to Deploy XLoader Malware

Security researchers at AhnLab Security Intelligence Center (ASEC) have uncovered a new campaign leveraging...

Hackers Converting Stolen Payment Card Data into Apple & Google Wallets

Cybercriminal groups, primarily based in China, are leveraging advanced phishing techniques and mobile wallet...