Urgent.News

What's breaking now, across thousands of outlets.

Tech

Binance says malicious code, fake job interview led to $6.3B hack

Binance said Tuesday that a $6.3 billion hack of the world's largest cryptocurrency exchange was the result of a "multi-stage campaign," including a malicious software download and a fake job interview. Hackers, whom both the FBI and outside analysts have linked to North Korea, moved billions of dollars' worth of crypto out of Binance wallets...

Binance says malicious code, fake job interview led to $6.3B hack

Binance revealed a massive $6.43 billion theft that resulted from a sophisticated multi-stage cyberattack targeting its internal infrastructure. The breach occurred through a series of coordinated actions, exploiting both technical vulnerabilities and social engineering tactics.

In June 2026, an engineer known as "Engineer A" inadvertently downloaded a trojanized Homebrew installer, which introduced a dangerous program into the company's wallet systems. While Binance promptly changed access keys and isolated the affected team, the breach exposed critical information to the attackers.

A month later, in September 2026, the attackers shifted their focus to "Engineer B." Through a deceptive recruitment process on a job search platform, Engineer B was lured into a series of deceptive interviews with individuals posing as HR and the company's CEO. The ultimate objective was to convince Engineer B to download a malicious code sample, which successfully compromised his computer.

On October 20, 2026, the perpetrators utilized Engineer B's compromised device, along with the access obtained from Engineer A, to infiltrate the company's internal AI tool. This enabled them to gain control over Engineer C, another team member. Between October 29 and 30, they leveraged stolen credentials from Engineer A to execute a malicious program, exploiting access to an internal transaction authorization service.

Through these actions, the attackers were able to execute unauthorized transfers and siphon off $6.43 billion in funds. In response, Binance took immediate action to contain the breach. By November 3, they had rebuilt the affected wallet system, updated their AI and access control systems, and replaced the compromised devices. The company also revoked old digital keys, conducted comprehensive security audits, and enhanced their ability to detect unusual behavior.

Additionally, Binance is collaborating with law enforcement and security experts to track and freeze any stolen assets.

Written by urgent.news from Dev.to'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 thehill.com →

More in Tech

Guardrails for vibe coders: PreToolUse rules that stop rm -rf and secret leaks

Originally published at pilothouse.dev/blog/guardrails-for-vibe-coders . Vibe coding works until the agent runs rm -rf on the wrong folder, prints your .env into the transcript, or force-pushes over a…

  • PreToolUse hooks prevent destructive commands like rm -rf
  • Rules engine implemented for coding agents to enforce safety
  • Guardrails block secret leaks and access to production databases

Pricing Flag Rollbacks — Choosing Real-Time Metrics Dashboard Tools Safely

The least complex tool that can answer “should I roll this pricing rule back?” is usually the right starting point: a metrics store with a query API, a dashboard, and alerts tied to the decision.

  • Focus on price-rule exposure, checkout starts, payments, failures, and cancellations.
  • Use multiple evaluation windows for meaningful comparisons and analysis.
  • Separate event streams from metrics to retain detailed payment failure information.

How to Prevent Duplicate POS Sales from Skewing Inventory with Python and SQLite

A point-of-sale register sells two pairs of boots. The inventory worker deducts two units and commits the change. Then the worker crashes before it acknowledges the message.

  • Create Python program using SQLite to handle sales and check for processed sales
  • Run program, perform sale, then try running again with same event ID to ignore duplicate
  • Handle errors for sales referencing non-existent SKUs or making inventory negative

More from Tuesday 3 November →