SEC X Account was Hacked Using SIM Swapping Method

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.

- Advertisement -

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?