The FBI has attributed the $6.43 billion Binance theft to North Korea's TraderTraitor. About $2.85 billion is frozen, and the FBI says the rest is being converted mainly into Ethereum. For a business holding operating cash on the exchange, Binance company funds safety now comes down to two checks: who can move your balance, and whether a fake recruiter's Terraform coding test reached the laptop that can.
Key takeaways
- The FBI, Secret Service and IRS-CI attributed the Binance theft, put at $6.43 billion across 11 blockchains, to North Korea's TraderTraitor.
- $2.85 billion is frozen by Tether, Circle, Ripple, Arbitrum and Optimism; native BTC and ETH cannot be frozen, and frozen does not mean returned.
- Binance reopened withdrawals on all 15 networks; from 06:00 to 15:30 UTC on November 1, net outflow was about $3.64 billion.
- TraderTraitor's recent tradecraft is fake recruiters plus trojanized Terraform providers delivering FLATROOF and ROOFDECK. Binance's own entry point is still unknown.
- Audit who and what can withdraw company funds, check laptops that ran interview tasks, and use the FBI address list as a screening seed for deposits and payouts.
What did the FBI say about the Binance theft?
The FBI says North Korea did it. In a joint statement with the U.S. Secret Service and IRS Criminal Investigation, the agency attributed the Binance theft to TraderTraitor, a state-aligned cluster that security vendors also track as Jade Sleet, Pressure Chollima, PUKCHONG, Slow Pisces and UNC4899. The Hacker News reported the attribution on November 1, 2026, the morning Binance began reopening withdrawals.
The scale is record-breaking. The Hacker News puts the haul at $6.43 billion across 11 blockchains, with 82% of the value on Ethereum and Bitcoin. The FBI’s wording is “more than $6 billion,” and earlier coverage, including ours, used about $6.3 billion. The gap most likely reflects volatile assets priced at different moments.
Either figure dwarfs the previous record, the $1.46 billion taken from Bybit in February 2025, a theft also attributed to TraderTraitor. Blockchain analytics firm Elliptic estimates that North Korea-linked actors have stolen more than $6.5 billion in crypto in recent years, and says of Binance: “This single incident almost doubles the total cryptoassets stolen by the regime.”
What the FBI did not say matters just as much. Neither the attribution nor the reporting around it explains how the attackers first got into Binance: no named system, no CVE, no root cause, no intrusion date. Treat any confident reconstruction of the entry point as speculation. Our earlier Binance business checks covered the first hours; this piece picks up from the attribution.
Binance company funds safety: what is frozen and what still moves?
About $2.85 billion of the stolen value is frozen, and the rest is moving. Tether, Circle, Ripple, Arbitrum and Optimism froze assets on-chain, which is why some headlines rounded the figure to “nearly $3 billion.”
“Frozen” has a narrow meaning here. Tether and Circle can blacklist an address inside their own USDT and USDC contracts, so those tokens stop moving. Native Bitcoin and Ether have no such switch, and a large share of the haul sat on those two chains. Frozen also does not mean returned: getting value back takes a legal process nobody has described publicly.
The FBI says the actors are converting proceeds primarily into Ethereum, and it expects the assets to be “further laundered by converting them using DeFi and instant swap services.” The agency also published the wallet addresses it ties to that laundering. We do not reproduce them here; take them from the FBI release itself.
On the customer side, Binance says deposit services stayed open and were “not affected by the incident.” Phase one of withdrawals ran between 06:00 and 09:00 UTC on November 1, and Binance later said all 15 networks were back. Its figures for 06:00 to 15:30 UTC that day: $4.649 billion withdrawn, $1.01 billion deposited, a net outflow of roughly $3.64 billion.
Customers moved money out as soon as they could. That is a rational treasury reaction, not proof of insolvency, and Binance said last week it would cover the losses. For a business, the useful question is narrower: how much of your working capital can one platform lock, and for how long? If the answer is “most of it, for days,” you have a concentration problem.
Keep the float you need for operations on the exchange and hold the rest somewhere you control. Three questions are still open:
- How much of the frozen $2.85 billion actually returns, and when.
- Where the value that cannot be frozen moves next through DeFi and swap services.
- Whether the FBI address list grows as laundering continues.
Who at your company can still send a withdrawal?
Find out today, because that list is your real exposure. Binance said its teams had “taken precautionary measures to safeguard the platform, conducted security assessments, and worked to verify the readiness of affected services” before reopening. That covers its side. Your side is the set of people, devices and keys that can move your balance.
- People. List everyone with withdrawal rights on company accounts, including the founder who opened the account years ago and the contractor whose access was never removed.
- Personal accounts. Ask whether company money sits in an employee’s personal Binance account for expenses or vendor payments. It happens more often than finance teams expect, and those accounts carry none of your controls.
- API keys. Review every key, its permissions and its IP restrictions. A trading bot rarely needs withdrawal rights.
- Allowlists. Confirm withdrawal address allowlists are on and contain only addresses you can explain.
- Devices. Note which laptops and phones hold 2FA apps, hardware wallets or live sessions for those accounts.
- The outage window. Reconcile every deposit and withdrawal from the pause through November 1 against your ledger, and keep screenshots of balances and notices.
Exchange API keys and signer credentials also leak into places nobody tracks: old repositories, CI variables, shared password vaults, chat history. A secrets and credential exposure assessment finds those copies before someone else does, and you can run it without knowing Binance’s root cause.
How does TraderTraitor reach the people who hold the keys?
Usually with a job offer. Recent reporting from SentinelOne, Zscaler ThreatLabz and Microsoft describes recruitment-themed approaches to people at cybersecurity, AI, blockchain and talent-recruitment companies, run through front companies. AI helps the operators write convincing lures, build fake personas and evade detection.
Microsoft describes Jade Sleet posing as recruiters for a spoofed “AI-powered blockchain intelligence company,” with tailored domains, social media profiles and industry knowledge. The “recruiters” pitched software engineering roles and scheduled interviews with anyone who engaged. Meanwhile, the operators ran two more front companies on comparable infrastructure. When one front company is exposed, the next is already operating.
Once the target engages, vendors report trojanized Terraform providers as the delivery vehicle, followed by a three-step chain:
- Bash loader. Checks whether the victim runs macOS, Linux or Windows and downloads the matching payload.
- FLATROOF. A cross-platform implant with a built-in Python information stealer that collects sensitive data from the machine.
- ROOFDECK. A backdoor that gives the operators full remote control and persistent access.
Terraform is a well-chosen attack vector. A provider is an executable plugin, not a passive config file. Terraform runs it with the local user’s permissions, so a poisoned provider can read that user’s files, environment variables and cloud credentials. On a DevOps engineer’s laptop, that often means production cloud accounts and CI secrets.
The recruiter pretext is not new. Lazarus Group’s Operation Dream Job and Famous Chollima’s Contagious Interview both used fake hiring to get victims to run malicious code. TraderTraitor itself has been active since at least 2020, and its record includes DMM Bitcoin, Bybit, KelpDAO and Bitget, with Binance now added.
None of this tradecraft has been named as the Binance entry point. It is the route this group keeps using to reach people whose machines can touch wallets, cloud accounts and build pipelines, which is why it belongs on your checklist.
What should IT check if a developer took a recruiter's coding test?
Check the machine before anyone touches that code again. From our own engagements: when we run recruiter-themed scenarios, the take-home task is almost always opened on the engineer’s main work laptop, the one with cloud CLI profiles, SSH keys, a password manager and often a browser wallet. Nobody files a job interview as a security event.
- Ask first. Send engineering and DevOps staff a short, no-blame question: has anyone done a blockchain or AI interview task in recent months, especially one involving Terraform?
- Do not run it again. Do not run terraform plan or terraform apply on a suspect machine to see what happens. Terraform loads provider executables and can rerun the malicious code.
- Preserve. Image the endpoint and keep the repository, lock file, provider cache and any CI logs before rebuilding.
- Review providers. In repositories and CI runners, compare the providers in lock files and local plugin caches with the ones your team approved. An unfamiliar namespace deserves a question.
- Assume credentials left. An information stealer means credential compromise, not just cleanup. From a clean admin host, revoke sessions and tokens, rotate cloud, CI and API keys, and audit new access keys, OAuth grants, runners and deploy keys.
The SentinelOne, Zscaler ThreatLabz and Microsoft reports carry the indicators for FLATROOF and ROOFDECK. Feed them into your EDR from the vendor advisories rather than copying lists from forums.
If you find signs of active misuse, such as a withdrawal nobody approved, an API key nobody created or a laptop behaving oddly, stop treating this as a tidy-up and handle it as an incident.
How do you screen against the FBI's laundering addresses?
Treat the FBI list as a starting watchlist for both directions of flow, not a finished blocklist. The funds are already being swapped into Ethereum, and every hop through a DeFi protocol or instant swap service creates addresses that are not on the list.
Regulated firms have a further reason to act. The EU applies FATF standards through the Transfer of Funds Regulation and its anti-money-laundering framework, so CASPs must run due diligence, report suspicious transactions and apply the Travel Rule. The checklist we would work through:
- Get the source list. Download it from the FBI release, record the date, and ignore copies circulating on social media.
- Load it on every chain you support. Add the addresses as a custom watchlist in your blockchain analytics or wallet screening tool, covering deposits and withdrawals, Ethereum first.
- Score indirect exposure. Alert on funds that arrive one or more hops from a listed address, not only on direct transfers. Route matches to manual review instead of automatic crediting.
- Look backward. Re-screen deposits received since the theft. Laundered value may already have reached you.
- Hold, do not bounce. If a deposit matches, hold it for review. Returning it to the sender can hand funds back to the launderer.
- Block outbound. Stop payouts and vendor payments to listed or high-exposure addresses until compliance clears them.
- Keep evidence. Preserve transaction hashes, timestamps, screening results and the analyst’s decision.
- Escalate through proper channels. Your MLRO files a suspicious transaction report with the national FIU (MOKAS in Cyprus). Freeze requests go through the relevant issuer or exchange.
- Check sanctions exposure. OFAC has designated North Korean state hacking groups and listed DPRK-linked wallet addresses in the past. Firms with a U.S. nexus may have hard obligations, so ask counsel.
- Refresh. The list will grow. Assign an owner to import updates and re-run step 4.
Smaller businesses that pay suppliers or accept customer payments in crypto can run a lighter version: check every new counterparty address with a reputable screening service before the first payment, and keep the result.
Why should EMIs and CASPs in Cyprus treat this as a DORA issue?
Because DORA expects them to test against this kind of attacker. Cyprus hosts a dense cluster of crypto-asset service providers holding or seeking MiCA authorization from CySEC, alongside electronic money institutions licensed by the Central Bank of Cyprus. EMIs and MiCA-authorized CASPs both fall within the scope of DORA, the EU Digital Operational Resilience Act.
DORA requires ICT risk management, incident classification and reporting, oversight of ICT third-party providers and a resilience testing program. Entities designated for threat-led penetration testing (TLPT) must run intelligence-led tests against live production. TraderTraitor’s playbook hits all of these at once: a person approached outside work, a stranger’s developer tool on a trusted laptop, credentials leaving the building.
A standard external pentest will not show whether that chain works against you. A scenario that starts where the group starts will: a recruiter message to a real engineer, a malicious take-home task, then a measured attempt to reach wallet infrastructure, CI secrets or the payments back office.
That is the job of a red team assessment, and for firms with formal obligations, DORA penetration testing and TLPT can be scoped around the same threat intelligence. The deliverable that matters is not the report. It is learning whether your detection fires before a signer’s laptop is owned.
FAQ
Did the FBI say North Korea stole from Binance?
Yes. The FBI, with the Secret Service and IRS Criminal Investigation, attributed the theft of more than $6 billion to North Korea's TraderTraitor group. The Hacker News puts the total at $6.43 billion; other outlets used about $6.3 billion, most likely because of pricing at different moments.
Is it safe for a business to keep money on Binance after the hack?
Binance has reopened withdrawals on all 15 networks and says deposits were not affected. The safer practice for any business is to keep only operating float on an exchange, restrict who can withdraw, and hold the rest in wallets or accounts you control.
How much of the Binance theft is frozen?
About $2.85 billion, frozen on-chain by Tether, Circle, Ripple, Arbitrum and Optimism. Native Bitcoin and Ether cannot be frozen by an issuer, and no frozen funds have been reported as returned.
What is TraderTraitor?
A North Korea-aligned hacking group active since at least 2020, also tracked as Jade Sleet, Pressure Chollima, PUKCHONG, Slow Pisces and UNC4899. It has been tied to thefts from DMM Bitcoin, Bybit, KelpDAO, Bitget and now Binance.
Was Binance hacked through a fake job offer?
Nobody has said so. No root cause, system or intrusion date has been published. The recruiter lures and trojanized Terraform providers come from separate vendor reporting on the group's recent activity.
How do I know if a crypto payment is going to a stolen wallet?
Screen the counterparty address with a blockchain analytics or wallet screening tool loaded with the FBI's published laundering addresses, including indirect exposure over several hops. Hold matches for compliance review and keep the evidence.
If company funds have moved without approval or a staff laptop looks compromised, our crypto hack incident response team can help you contain it and preserve the evidence.
Tell us what you're running
Scoping is free. We reply within one business day, and under 30 minutes for active incidents.
