chief security officer
  • macropolicy
  • Industrial Development
  • CSO·Insight
  • Threat intelligence
  • Data Security
  • privacy protection
  • Cloud security
  • en_USEN
    • de_DEDE
    • ru_RURU
    • zh_CNCN
    • zh_TWTW
    • jaJP
    • ko_KRKR
Sign in Sign up
Creation Center
  1. chief security officerHome
  2. intelligence gathering

X (formerly twitter) security team confirms theft of SEC account

chief security officer • January 11, 2024 at 7:42 pm • intelligence gathering • 9115 views

The U.S. Securities and Exchange Commission compromised the X (formerly twitter) account after unidentified individuals took control of the X (formerly twitter) account cell phone number. Approval for the Bitcoin ETF to be listed on all registered national stock exchanges was posted through the account, which did not have two-factor authentication enabled at the time of the theft.The X security team recommends that all users enable two-factor authentication to secure their accounts.

The SEC posted on its X (formerly twitter) account on Tuesday that the agency has "approved the listing of bitcoin ETFs on all registered national securities exchanges" and that "approved bitcoin ETFs will be subject to ongoing oversight and compliance measures to ensure continued investment "protection."

X (formerly twitter) security team confirms theft of SEC account

The post received more than 35,000 likes and more than 26,000 retweets in just 18 minutes before it was deleted, and SEC Chairman Gary Gensler later declared that the agency's accounts had been hacked via X Explained.

Company X's security team today confirmed that its Twitter account @SECGov has been compromised. The company has completed its initial investigation and determined that the compromise was not due to a breach of its systems, but rather to an unidentified individual taking control of X-related phone numbers. @SECGov via a third-party account.

X (formerly twitter) security team confirms theft of SEC account

Company X can also confirm that the account was not enabled at the time of the thefttwo-factor authentication. Two-factor authentication is an extra strong account security measure that helps protect accounts from unauthorized access.

Company X encourages all users to enable two-factor authentication. For more information on how to do this, please visit Company X's Help Center: https://help.x.com/en/safety-and-security/account-security-tips

leakparticulars

According to Company X's investigation, unidentified individuals were able to take control of the phone numbers associated with X. @SECGov through a third party account. This allowed them to reset the account's password and gain access to the account.

The account did not have two-factor authentication enabled at the time of the theft. Two-factor authentication requires the user to provide two different authentication factors in order to log into the account. This typically includes a username, password, and a one-time code from a cell phone or other security device.

Response from Company X

Company X has taken steps to protect its systems from future attacks. The company has also updated its security policy to require two-factor authentication (2FA) to be enabled for all accounts.

Users' recommendations

Company X encourages all users to take steps to protect theirAccount Security. This includes:

  • Use strong passwords and change them regularly
  • Enable two-factor authentication
  • Monitor their account activity and note any anomalies

Users may also take the following measures to protect their personal information:

  • Be cautious about sharing personal information
  • Use a secure browser andcyber securityhardware
  • Keep your operating system and software up to date

Original article by Chief Security Officer, if reproduced, please credit https://www.cncso.com/en/us-sec-twitter-account-hacked.html

2FA Security VerificationSEC account theft Twitter securitytwo-factor authenticationAccount Securitycell phone number hijackingleakloopholescyber securityhacking attack
Like (0)
0 0
Generate poster

About the author

chief security officer

chief security officer

113 posts
4 comments
1 questions
3 answers
4 followers
Chief Security Officer (cncso.com)
Windows & Edge Browser Patch:Microsoft Security Update Fixes 48 New Vulnerabilities
Previous January 10, 2024 9:30 pm
Five years of safe operation practice summary and future thinking
Next January 12, 2024 at 9:25 pm

related suggestion

  • Fortinet Releases High-Risk Security Vulnerability in FortiOS SSL VPNs intelligence gathering

    Fortinet Releases High-Risk Security Vulnerability in FortiOS SSL VPNs

    010.5K00
    chief security officer chief security officer
    February 10, 2024
  • Malicious AI tool FraudGPT is sold on the dark web, causing network security issues intelligence gathering

    Malicious AI tool FraudGPT is sold on the dark web, causing network security issues

    011.5K00
    lyon lyon
    August 1, 2023
  • How to implement secure and trusted data security encryption in your business? Data Security

    How to implement secure and trusted data security encryption in your business?

    09.8K00
    chief security officer chief security officer
    February 19, 2024
  • Cybersecurity certification "mapping" Awareness training

    Cybersecurity certification "mapping"

    09.1K00
    chief security officer chief security officer
    February 26, 2024
  • Google open-sources Magika AI document recognition Safe operation

    Google open-sources Magika AI document recognition

    09.4K00
    chief security officer chief security officer
    February 17, 2024
  • Safe operations from the perspective of Party A and Party B Safe operation

    Safe operations from the perspective of Party A and Party B

    09.9K01
    chief security officer chief security officer
    March 1, 2024
chief security officer
chief security officer
chief security officer

Chief Security Officer (cncso.com)

113 posts
4 comments
1 questions
3 answers
4 followers

Recent Posts

  • CVE-2025-34291:Langflow AI智能体和工作流平台账户接管和远程代码执行漏洞
  • CVE-2025-55182: React Server Components 远程代码执行漏洞
  • Bloody Wolf Organizes Report on Cyberattacks Impersonating Central Asian Government Agencies
  • CVE-2025-47812: Wing FTP Server Remote Code Execution Vulnerability
  • Google chrome V8 JavaScript Engine Type Obfuscation Remote Code Execution Vulnerability
  • Industrial Control System Security Vulnerability Analysis Report 2025
  • Apple iMessage Zero-Click (Zero-Click) Vulnerability (CVE-2025-43200)
  • Google chrome V8 JavaScript engine out-of-bounds read/write vulnerability (CVE-2025-5419)
  • AI zero-hit vulnerability: can steal Microsoft 365 Copilot data
  • The Economics of Cybersecurity in Emerging Markets

Recommended reading

  • CVE-2025-34291:Langflow AI智能体和工作流平台账户接管和远程代码执行漏洞

    CVE-2025-34291:Langflow AI智能体和工作流平台账户接管和远程代码执行漏洞

    2025年12月11日

  • CVE-2025-55182: React Server Components 远程代码执行漏洞

    CVE-2025-55182: React Server Components 远程代码执行漏洞

    2025年12月11日

  • Artificial Intelligence (AI) Big Model Security Risks and Defense In-Depth Report

    Artificial Intelligence (AI) Big Model Security Risks and Defense In-Depth Report

    November 29, 2025

  • Bloody Wolf Organizes Report on Cyberattacks Impersonating Central Asian Government Agencies

    Bloody Wolf Organizes Report on Cyberattacks Impersonating Central Asian Government Agencies

    November 28, 2025

  • CVE-2025-47812: Wing FTP Server Remote Code Execution Vulnerability

    CVE-2025-47812: Wing FTP Server Remote Code Execution Vulnerability

    November 2, 2025

  • Google chrome V8 JavaScript Engine Type Obfuscation Remote Code Execution Vulnerability

    Google chrome V8 JavaScript Engine Type Obfuscation Remote Code Execution Vulnerability

    July 2, 2025

  • Industrial Control System Security Vulnerability Analysis Report 2025

    Industrial Control System Security Vulnerability Analysis Report 2025

    July 2, 2025

  • Apple iMessage Zero-Click (Zero-Click) Vulnerability (CVE-2025-43200)

    Apple iMessage Zero-Click (Zero-Click) Vulnerability (CVE-2025-43200)

    June 15, 2025

  • Google chrome V8 JavaScript engine out-of-bounds read/write vulnerability (CVE-2025-5419)

    Google chrome V8 JavaScript engine out-of-bounds read/write vulnerability (CVE-2025-5419)

    June 12, 2025

  • AI zero-hit vulnerability: can steal Microsoft 365 Copilot data

    AI zero-hit vulnerability: can steal Microsoft 365 Copilot data

    June 12, 2025

chief security officer
  • fig. beginning
  • My Account
  • Creation Center
  • Privacy Policy
  • safe community
  • about Us
  • Sitemap

Copyright © 2020 Chief Security Officer. All Rights Reserved.

Zhejiang ICP No. 2023041448 Zhejiang Public Network Security No. 33011002017423