Binance says banks received its hack report as Fed and OCC checks follow $6.3B incident

What the reported bank checks cover

The Federal Reserve and OCC reportedly began contacting banks on Monday, November 2, asking about unusual activity or interruptions to services. Odaily's later dispatch, published at 22:47 SGT on November 5, identifies that date and says large banks started internal diagnostics. It attributes the account to Bitcoin.com News. The earlier Odaily item credits Reuters. These accounts should not be counted as separate investigations proving the same outreach. Odaily's later account.

Cointelegraph also attributes the outreach to Reuters and people familiar with the matter. Its additional reporting includes a response from Binance and interviews with cybersecurity specialists. Those interviews add information about how the exchange communicated and how specialists interpret the risk. They do not turn unnamed sources into an official regulator announcement.

According to the reports, the banks' immediate questions concern their own systems: whether anything unusual happened, whether services were interrupted, and whether defenses could withstand a similar attack. A bank can investigate those questions before it discovers a loss. A request from a supervisor to inspect a system also does not by itself establish that the supervisor has found an intrusion.

Odaily's later dispatch says one banking source reported no operational interruption, while employees prepared responses for customers and received only a few inquiries. That is one source's description of one institution. It cannot be expanded into a claim that every US bank has completed its review or that all customer payments are operating normally.

Binance's partner response is the new detail

Cointelegraph reports that a Binance spokesperson confirmed the exchange had shared the publicly released incident report with all its banking partners. The spokesperson also said Binance was not aware of vulnerabilities affecting those partners. This is a statement by Binance about its communications and knowledge. It is useful evidence of what the exchange says it did; it is not a joint audit signed by its banks.

The scope of the response matters to a reader trying to understand a transfer delay. Sharing an incident report gives counterparties material to examine. It does not tell a customer which particular bank reviewed it, what tests that bank performed, or when a specific payment will arrive. The opened article does not provide those answers.

Cointelegraph separately sought responses from the regulators. A Federal Reserve spokesperson said the agency had nothing to share about the reported inquiries. The OCC had not replied by the article's publication. Neither response supplies a public finding about a named bank's exposure. A lack of public comment should not be rewritten as confirmation of either a compromise or an all-clear.

This leaves two different pieces of information on the record: Reuters-sourced reporting about supervisory contact, and Cointelegraph's direct exchange response. Keeping them separate prevents a common reading error, in which a company's statement about its partners becomes a regulator's conclusion about the entire banking system.

Keep the $6.3 billion figure attached to the exchange incident

The roughly $6.3 billion figure in the headline describes the Binance incident that prompted the reported checks. It is not a reported loss across US banks. Cointelegraph attributes a more precise figure of approximately $6.34 billion in affected digital assets to Binance's November 3 incident report. It also attributes roughly $2.85 billion frozen or intercepted at that report's cutoff to the exchange.

Those figures measure different things. Affected assets describe the reported scale of the incident; frozen or intercepted assets describe a response at a particular time. Neither number measures bank customer deposits, and neither gives a customer's current available balance. This follow-up uses the rounded incident figure to identify the event, without converting it into a claim about a new banking loss.

The same care applies to the timing. November 2 is the reported start of the bank outreach, November 3 is the incident report date cited by Cointelegraph, and November 5 is the publication date of the coverage. They are different points in the story. Reading the newest article on November 6 SGT does not mean the bank checks began that morning.

Why security teams are examining the method

Cointelegraph's account of the exchange report says the attack involved compromised software, social engineering, stolen credentials and malicious software used to reach wallet systems. This article does not independently reconstruct the attack or identify which controls failed. The reason to mention the method is that the specialists interviewed by Cointelegraph connect it to a broader question about authorized systems being misused.

BlackFog founder and chief executive Darren Williams told the outlet that compromised employee devices, accounts or outside services could create risks for traditional banks, especially those handling crypto custody or payments. That is an expert assessment of possible exposure. It does not establish that a particular bank suffered the same intrusion or used the same software as Binance.

For customers, the distinction between a security review and an operational restriction is practical. A bank's technicians may examine access controls while customers continue to use accounts. A service may also have its own restriction that requires a separate explanation. The reports do not give a bank-by-bank operating-status list, so there is no basis here for assigning a status to a reader's bank.

CertiK's head of US government affairs, Stefan Muehlbauer, told Cointelegraph that supervisory checks after such an incident fit the regulators' role in understanding exposures and response capacity. He did not describe the outreach as evidence that regulators were abandoning crypto. His interpretation should stay attributed to him rather than becoming a newly announced policy.

The older Fed notice explains the supervisory context

An official Federal Reserve notice dated April 24, 2025 says the Board withdrew guidance that had expected state member banks to give advance notification of crypto-asset activities. It said those activities would instead be monitored through the normal supervisory process. The notice is background, not a public confirmation of the November inquiries. The Federal Reserve's April 2025 notice.

That wording helps answer a narrower question: removing a special advance-notification expectation did not mean the Fed said it would stop supervising crypto-related banking activities. The older notice specifically describes ongoing monitoring. It cannot tell us which banks received questions this week, what those questions contained, or whether a new rule is being considered.

A customer does not need to infer a policy reversal to respond to a transfer problem. The opened materials provide no new customer instruction from the Fed or OCC tied to these checks. An actual operational notice from the institution handling the payment would be a separate document and should be evaluated on its own terms.

Check the pending transfer before changing anything

If you have a payment waiting between a bank and an exchange, start with the transaction you can identify. Open the existing account directly, locate the transfer record, and retain its reference, amount, currency and displayed status. Compare that record with the receiving side's record.

If the records disagree, use the support channel inside the account you already opened and ask about that transfer reference. A report about a security review cannot establish where an individual payment is held. Avoid submitting another payment solely because a news headline mentions bank checks; first establish whether the original payment was rejected, remains pending or completed.

Treat messages offering compensation for the Binance incident with care. Do not use an unsolicited direct message to reach an account, install a tool or provide credentials. Open the service through your existing route and look for its own notices. Nothing in the bank-check reporting establishes a compensation claim form or authorizes a stranger to handle a withdrawal for you.

For a reader managing open positions as well as transfers, review available collateral and pending orders inside the account. Do not convert the incident's reported dollar amount into a prediction for Bitcoin or another asset. The sources do not measure a causal price impact or give a trading signal.

What remains unanswered

The reporting does not name the banks contacted, publish their diagnostic results, or provide a shared completion date for the reviews. Binance's response describes the report it shared and the vulnerabilities it knew about; it does not replace each banking partner's own findings. Those missing results are the information needed before making a broader claim about bank exposure.

The next substantive development would be an identified bank or regulator explaining an actual finding, an operating restriction, or a completed review. Another article repeating the same anonymous-source account would add circulation, without necessarily adding evidence. For now, the reader's actionable record is the status of their own transfer and any notice issued by the institution handling it.

Quick answers

Were US banks reported to have lost $6.3 billion?

No. That rounded figure refers to the Binance incident. The reporting does not establish a US banking-system loss of that size.

Did Binance say it sent the report to its banking partners?

Yes. Cointelegraph says a spokesperson confirmed the public incident report was shared with all banking partners. The exchange also said it was not aware of vulnerabilities affecting them.

Has the Federal Reserve publicly confirmed the specific inquiries?

Cointelegraph reports that its spokesperson had nothing to share. The April 2025 official notice confirms the older supervisory framework, not this week's individual contacts.