Blog · Industry news

Binance $6.3bn Hack Began With a Fake Job Interview

Share: https://www.ellixorlabs.com/blog/binance-hack-fake-job-interview-lessons (copy URL for iMessage or social)

Published (display in IST)

Updated (IST)

Developer looking at code on a laptop screen, as Binance links its $6.3bn hack to a fake coding test

Binance says North Korea-linked hackers used a fake job interview, a booby-trapped coding test and an internal AI tool to steal $6.3bn. Here is what founders should learn.

Cover photo: Tirza van Dijk / Unsplash via Wikimedia Commons, CC0. View source.

The biggest theft in crypto history did not start with a cracked vault. It started with a job offer. Binance says the $6.3bn heist on 29 October began when one of its engineers was lured into a fake hiring process and ran a booby-trapped coding assignment on his work laptop.

In its initial findings, published on 3 November, the world's largest crypto exchange described a "sophisticated, multi-stage campaign" built over months by attackers the FBI has linked to North Korea. For founders, the lesson travels well beyond crypto: the weakest point in a modern company is often a trusted laptop with too much access.

What happened

Short answer: attackers used social engineering, malware and a compromised internal AI tool to hop from one engineer's laptop to the system that signs Binance's hot wallet transactions, then drained wallets across several blockchains in a few hours.

According to Binance's account, as reported by The Register and CoinDesk, the groundwork was laid in stages:

  • June 2026: an engineer on the wallet DevOps team, searching for a popular AI coding tool, installed a tampered copy of Homebrew, the Mac package manager. Binance caught it, replaced the device and rotated credentials, but says the engineer's role and his colleagues had already been exposed.
  • September: a second engineer was approached on a legitimate job platform by a fake project director. A fake HR representative interviewed him on video and shared a social media account full of personal photos to build trust. In a second interview, a fake CEO on a chat app asked him to download an "assignment".
  • The payload: the code ran during setup and quietly swapped a legitimate developer tool for a malicious version. Binance says this zero-day malware was not caught by its endpoint security at the time.
  • 20 October: the attackers used the infected laptop and an internal AI tool to take control of two more wallet engineers' computers. One held a container deployment permission token.
  • 29 October: using that token, they deployed a container and ran the script that launched the theft. Funds began leaving at 20:05 UTC.
  • On Ethereum, the attacker abused EIP-7702, a feature that lets an account delegate execution rights to a smart contract, to gain control over a hot wallet. Because Binance's hot wallets use multi-party computation, there was no single key to revoke, and containment took until 00:10 UTC on 30 October, CoinDesk reported.

    Binance announced the findings in an article on its official X account:

    "29 October Binance Security Incident: Initial Findings and Response Update"

    Posted by @binance on X, 3 November 2026

    The exchange says about $2.85bn has been frozen, that 98% of the affected tokens have been replenished from company funds, and that users will not bear the loss. It also says it blocked 57 suspected North Korea-linked attempts this year. North Korea has denied involvement, the BBC reported.

    Why it matters for founders

    Strip away the crypto and this is a story about access. One developer laptop led to another, and a single long-lived token on one of them was enough to move billions. Most startups run on exactly this pattern: a few engineers, admin rights everywhere, and deploy keys sitting in a home folder.

    Fake interviews are not new, but they are getting better. Blockchain analytics firm Chainalysis says it has tied more than $14.3m in losses over the past 18 months to similar North Korea-linked fake interview schemes, and believes those smaller hits helped the attackers refine their playbook. For India's huge developer community, where take-home tests for overseas roles are routine, this is a very local risk.

    The AI angle deserves attention too. The first foothold came from a fake installer found while searching for an AI coding tool, and the attackers later moved through an internal AI tool. As teams wire assistants into code, chat and infrastructure, those tools become paths an intruder can walk. If you are adopting them, our take on the race to buy AI coding tools explains why they now sit so close to production.

    Practical steps any small team can take this month:

  • Treat interview tasks and unknown repositories as hostile. Open them in a disposable virtual machine or cloud sandbox, never on a work laptop.
  • Install developer tools only from official sites or verified package sources, and check you are not on a lookalike download page.
  • Keep deployment and cloud tokens short-lived, scoped to one job, and out of individual laptops wherever possible.
  • Require a second person to approve production deploys, permission changes and large payments.
  • Give internal AI tools the minimum access they need, and log what they do.
  • If you are hiring outside help, ask how they handle these basics. Our guide to choosing a web developer in India covers the questions worth raising, and our services page explains how we build systems with access controls designed in from day one.

    What to watch next

    Binance says this is an initial report and that some technical details will stay confidential. It has brought in independent cybersecurity experts to review the incident and plans a security research fund with AI and security firms. Expect a fuller post-mortem, more freezes or seizures as investigators trace the funds, and fresh scrutiny of EIP-7702 delegation and how exchanges secure hot wallets.

    Binance chief executive Richard Teng, speaking to CNBC, put the company's case this way:

    "The difference is verification, not just promises."

    Posted by @_RichardTeng on X, 3 November 2026

    For everyone else, the takeaway is simpler. Attackers are now patient enough to spend months building a fake company and a believable recruiter. Your defences need to assume that someone on your team will eventually run the wrong file, and make sure that one mistake cannot empty the till. If you want a second pair of eyes on how your systems are set up, talk to us.

    Frequently asked questions

    How did hackers steal $6.3bn from Binance?

    Binance says North Korea-linked attackers ran a months-long campaign. A fake job interview got malware onto an engineer's work laptop, then the attackers used an internal AI tool and a stolen deployment token to reach the hot wallet signing system on 29 October 2026.

    What is a fake job interview attack?

    It is a scam where attackers pose as recruiters or employers, build trust over one or more interviews, then ask the candidate to download a coding test or project. The download hides malware that gives the attackers access to the device and anything it can reach.

    How can a small startup protect itself from fake interview malware?

    Keep work laptops for work only, run unknown code in a throwaway virtual machine or cloud sandbox, keep deployment tokens short-lived and out of developer laptops, and require a second person to approve production deploys and large transfers.

    FAQ

    How did hackers steal $6.3bn from Binance?

    Binance says North Korea-linked attackers ran a months-long campaign. A fake job interview got malware onto an engineer's work laptop, then the attackers used an internal AI tool and a stolen deployment token to reach the hot wallet signing system on 29 October 2026.

    What is a fake job interview attack?

    It is a scam where attackers pose as recruiters or employers, build trust over one or more interviews, then ask the candidate to download a coding test or project. The download hides malware that gives the attackers access to the device and anything it can reach.

    How can a small startup protect itself from fake interview malware?

    Keep work laptops for work only, run unknown code in a throwaway virtual machine or cloud sandbox, keep deployment tokens short-lived and out of developer laptops, and require a second person to approve production deploys and large transfers.

    Talk to Ellixor Labs about this topic.

    Source: Binance / reporting