Urgent.News

What's breaking now, across thousands of outlets.

Tech

Binance says resuming withdrawals after major hack

WASHINGTON (UNITED STATES) - Binance said Sunday that it had resumed withdrawals after a major hack that affected more than $6 billion in funds.

Binance announced on Sunday that it had resumed withdrawals following a major hack that affected over $6 billion in funds. The world's largest cryptocurrency exchange by daily trading volumes temporarily suspended user withdrawals after the attack. The company began restoring the first batch of network withdrawals for the $BTC bitcoin network in phase one.

Binance stated that they were implementing a phased approach, prioritizing tokens based on user demand from the past week to ensure a careful restoration while conducting stability and security checks before reopening access. The company had set aside over $6.34 billion in reserves to cover the estimated losses from the hack, which is believed to be the largest-ever cryptocurrency heist.

Binance emphasized that user funds remained safe and they would absorb the financial impact of the stolen funds, not their users. The FBI attributed the attack to North Korea, confirming earlier suspicions that the Pyongyang-affiliated group TraderTraitor was responsible. This hack follows a series of high-profile cyber thefts linked to North Korea, which is believed to use its formidable hacking capabilities to generate funds that may aid its weapons program.

The news of the cyberattack led to a sharp decline in the prices of most major cryptocurrencies on Friday.

Written by urgent.news from Bangkok Post'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 bangkokpost.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

Production mode caught the join race my dev tests missed

Trace is a collaborative code execution visualizer, two people watching the same code run, live. This week I finished its deploy slice.

  • Dev mode missed bug in join race condition
  • Fix implemented with join lock to serialize actions
  • Regression test confirmed fix and added leak detection

More from Sunday 1 November →