post Shared by Xformerly Twitter, claims that the Security and Exchange Commission (SEC) approved a Bitcoin ETF on January 9th.

SEC approves Bitcoin Spot ETF https://t.co/46joQ8194c

— Zero Hedge (@zerohedge) January 9, 2024

Verdict: False

The SEC has made no such approval. This announcement was made by an unauthorized party and was quickly removed.

Fact check:

According to the SEC, the SEC is scheduled to make a decision on Bitcoin exchange transfer funds on January 10th. wall street journal. Citing tweets from the SEC's X account, social media users claimed that the SEC had already approved a Bitcoin ETF.

However, this claim is false.SEC accounts were compromised, according to Reuters.Both S.E.C. chairman And that SEC X said the account had been compromised and the tweets were not authorized.

An SEC spokesperson told Check Your Fact in an email that an “unidentified person” briefly accessed the SEC's X account.

“The SEC has determined that there has been unauthorized access and activity on @SECGov. x.com Account by an unknown party for a short time shortly after 4:00 PM ET. Unauthorized access has been stopped. “The SEC will work with law enforcement and partners across the government to investigate this matter and determine appropriate next steps regarding both the unauthorized access and related misconduct,” the spokesperson said.

Zero hedge after that Has been updated The article points out that the SEC's announcement was false. The article also points out that the hack of the SEC's X account was not due to X's systems, but because two-factor authentication was not enabled on the number associated with the SEC. (Did the Times Square billboard call Ceasefire anti-Semitic?)

Account has been confirmed @SECGov We have completed a preliminary investigation due to a breach. According to our investigation, the breach was not due to a compromise of X's systems, but rather due to an unidentified individual gaining control of the phone number…

— Safety (@Safety) January 10, 2024

“Our investigation indicates that the breach was not due to a compromise of X's systems, but rather due to an unidentified individual gaining control of a phone number associated with X. @SECGov Accounts via third parties. We can also confirm that his two-factor authentication on the account was not enabled at the time the account was compromised,” the X safety team said. tweeted January 10th.