Urgent.News

What's breaking now, across thousands of outlets.

Tech

Binance hack prompts Thai scrutiny

The Thai unit of Binance, the world's largest cryptocurrency exchange, has assured customers that their assets remain safe after its parent company was hacked in what is being dubbed the biggest crypto heist in history.

A U.S. blockchain intelligence firm has identified North Korean hackers, known as TraderTraitor, as the perpetrators of a staggering $6.36 billion cryptocurrency heist from Binance, the world's largest crypto exchange. The attack, which occurred on Thursday, saw the hackers move digital assets across 10 blockchain networks, with most funds stolen within a mere 20 minutes.

TRM Labs, the firm responsible for the analysis, expressed high confidence in their attribution to North Korean hackers, pointing to similarities with previous operations. The group reportedly began preparations for the attack at least 36 hours prior, gaining access to systems used to authorize cryptocurrency transfers. As a result, Binance is left with roughly $2.4 billion worth of Bitcoin and Ethereum still under hacker control.

The U.S. government has previously linked North Korea to illicit activities involving cryptocurrency networks in countries like China, Russia, Cambodia, and Vietnam. Binance CEO Richard Teng assured that the company is actively working to resolve the situation and is fully committed to covering all losses through their reserves. President Donald Trump acknowledged that the FBI and law enforcement authorities are investigating the incident, but the origins of the stolen funds remain uncertain.

Written by urgent.news from Yonhap News'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

Your Agent's Tool Layer Is a Public API. Design It Like One.

The first agent I put in front of real users had eleven tools and a system prompt that said "ask for confirmation before doing anything destructive." It worked in staging for six weeks.

  • Classify tools based on side effects: read, write, or destructive; never domain-based.
  • Derive idempotent keys from run and arguments, pass downstream to ensure idempotency and robustness.

Get a debug console on failing docker container launches.

Using docker compose I am building an image: docker compose build someservice Or directly via docker for example: docker build .

  • Identify failing container using "docker ps -a".
  • Create new image from failing container with "docker commit".
  • Run new image in detached mode with interactive shell.

More from Friday 30 October →