Urgent.News

What's breaking now, across thousands of outlets.

Tech

Binance says resuming withdrawals after major hack

WASHINGTON: Binance said on Sunday that it had resumed withdrawals after a major hack that affected more than US$6 billion in funds.

Binance says resuming withdrawals after major hack

Binance announced on Sunday that withdrawals have resumed following a major hack that compromised over US$6 billion in funds. The exchange, which is the world's largest by daily trading volumes, had previously suspended user withdrawals due to the attack. The first batch of network withdrawals began with the Bitcoin network, as stated on the company's official X account.

Earlier reports indicated that Binance was preparing to resume the first phase of withdrawals between 0600 and 0900 GMT on Sunday. The company explained its phased approach, prioritizing tokens based on user demand from the past week to ensure a careful, stable, and secure reopening of each network and asset pair.

Binance disclosed on Saturday that it had allocated more than US$6.34 billion in company funds to cover losses from the hack, which is believed to be the largest crypto heist in history. The firm emphasized that user funds remain secure and that it will absorb the financial impact of the stolen assets, not the users. The FBI linked the attack to North Korea, confirming earlier suspicions from private investigators and analysts that a group called TraderTraitor, believed to be Pyongyang-affiliated, was responsible.

The hack follows a series of high-profile cyber thefts linked to North Korea, a hacking operation that has amassed a significant amount of funds potentially used to finance its weapons program. These developments led to a sharp drop in the prices of most major cryptocurrencies on Friday.

Written by urgent.news from New Straits Times'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 nst.com.my →

More in Tech

A PKCS#11 key can be protected and still be over-authorized

A PKCS#11 key can be protected and still be over-authorized Moving a signing key into an HSM changes where the key material lives.

  • PKCS#11 keys can be protected yet over-authorized.
  • CKAALWAYSAUTHENTICATE requires PIN for every key usage.
  • Application, not HSM, determines key authorization for business transactions.

FHIR Validation Doesn't Tell You What to Do Next, So I Built a Decision Layer

A FHIR resource can pass validation and still be the wrong thing to act on. I built a small decision layer for that gap: it takes parsed FHIR R4 resources, sends a flattened state to TypeSafe AI's Jev…

  • FHIR validation alone doesn't dictate next steps for a resource
  • Decision layer processes parsed FHIR R4 resources to determine action
  • Model achieves 0.814 to 0.922 accuracy on 204 synthetic records

Deterministic Runtime Governance: Moving from Paper Compliance to Machine Reality (BIGF)

In traditional enterprise IT, governance follows a broken rhythm: developers push code, and compliance teams check Word documents once a year during an audit.

  • BIGF replaces subjective compliance with deterministic runtime enforcement
  • Policy-as-Code translates mandates into machine-executable parameters
  • Authority function halts operations when thresholds are breached

More from Sunday 1 November →