US regulators contact banks after $6.3 billion Binance hack, report says
US regulators reach out to banks after Binance hack
US regulators are reportedly contacting banks to check for unusual activity or disruptions after the $6.3 billion hack of Binance, a crypto exchange where users can buy and sell digital assets.
The report is based on sources speaking to Reuters. It says banks are also checking their own security systems to see if they are prepared for a similar attack.
Main points from the report
- The hack was reported to have taken place on October 29 and involved three Binance employees.
- Officials from the Federal Reserve and the Office of the Comptroller of the Currency have been reaching out to banks, according to Reuters sources.
- One contacted bank said it saw no disruptions to its services.
- A cybersecurity team at one of the largest US banks contacted Binance to prepare its own internal review.
What sources told Reuters
Reuters reported that regulators are probing banks for unusual activity or disruptions linked to the Binance hack.
One source whose bank was contacted said there were no disruptions to its services, but the bank had prepared statements in case customers asked questions.
Another source claimed that the rapid development of AI means banks need to put more resources into cybersecurity while trying to keep up with hackers. This is a claim from that source, not a confirmed finding in the report.
Reuters also reported that a cybersecurity team at one of the largest US banks contacted Binance after the hack. The team wants to create an internal report reviewing the bank's security systems.
How the attack unfolded
The report says the hack followed a series of security breaches targeting three Binance employees.
First, an engineer looking for a popular AI coding tool clicked a malicious search engine ad for a software installation program and downloaded a program containing malware. The breach was detected and dealt with by Binance, but details about the engineer and his team had already been leaked.
Three months later, another Binance engineer was tricked into a fake job interview and downloaded an assignment containing malicious code. The malware extracted sensitive information from the engineer.
By October 29, the malware was able to log into a third engineer's computer and launch the malicious script that caused the $6.3 billion hack, according to the report.
What is still unclear
The contacts with banks and the actions banks are taking are reported by Reuters sources. The supplied material does not include a direct public statement from the Federal Reserve or the Office of the Comptroller of the Currency about the outreach.
The material also does not say how many banks were contacted or whether any bank found unusual activity linked to the hack.
Why banks are reviewing their systems
According to the report, banks are trying to learn from the hack and assess whether their own systems could respond to a similar attack. Based on the supplied material, the practical effect so far is checks, prepared customer statements, and internal security reviews, rather than confirmed disruptions at banks.
Sources
Newisty Editorial Team covers technology, cryptocurrency, digital products, online platforms, developer tools and the wider digital economy. Our content is researched from official sources, company announcements, public documentation, market data and other primary or reputable sources. Articles are reviewed and edited before publication for clarity, accuracy and useful context.
Related Posts
Binance restarts customer withdrawals after $6.3bn heist
Aave Labs acquires Avon team to enhance fixed-rate lending
Kevin O’Leary Predicts Bitcoin at $1 Million, Warns of Quantum Threat
SEC and CFTC say they will push crypto rules after Clarity Act fails in Senate
