Urgent.News

What's breaking now, across thousands of outlets.

Tech

FBI blames North Korea for record $6.3B Binance hack

US agency seeks private-sector help to block further money-laundering of stolen digital assets.

FBI blames North Korea for record $6.3B Binance hack

The FBI has accused North Korea, also known as the Democratic People’s Republic of Korea (DPRK), of being responsible for a massive $6.3 billion cyber theft from cryptocurrency exchange Binance. The agency referenced this specific malicious cyber activity as "TraderTraitor" and noted that the North Korean hackers have been converting stolen assets into Ether (ETH).

They expect these assets to be further laundered using decentralized finance (DeFi) and instant swap services. The FBI is seeking assistance from private sector entities such as THORNode operators, RPC node operators, instant exchange platforms, DeFi services, and blockchain analytics firms to block transactions involving these addresses.

North Korea-linked hackers are believed to have stolen around 60% of the value lost in crypto hacks in 2025, with proceeds used to fund the regime's nuclear and ballistic missile programs.

Written by urgent.news from Cointelegraph's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at cointelegraph.com →

More in Tech

Regular Expression Denial of Service (ReDoS) in JS & PHP: Spotting Catastrophic Backtracking

Here is a pattern I keep finding in slug and username validators: /^([a-z0-9]+-?)+$/ . It looks harmless and passes every unit test. Now send it thirty lowercase letters followed by an underscore.

  • ReDoS exploits vulnerabilities in regex engines, causing catastrophic backtracking.
  • Spot backtracking by identifying nested or overlapping quantifiers in patterns.
  • Fix vulnerabilities by rewriting patterns to be unambiguous and avoid super-linear backtracking.

The docs described the release we run, not the code a reader clones

A documentation page can be wrong in a specific way: it can describe the software that is running in production, not the software a reader gets when they clone the repository.

  • Documentation described running release, not cloned code
  • Users cloning repo faced failures, main branch worked
  • Documentation updated to reflect clone rules

More from Sunday 1 November →