Adnan Canturk.
Security

Binance and Polymarket, 29 October 2026: what happened, the first 72 hours, and how to prevent it

13 min readTürkçe oku

Last updated:

Binance and Polymarket breaches of 29 October 2026: what happened, the first 72 hours and prevention

Within three hours on the evening of 29 October 2026, two of the best-known names in crypto had a very bad night. Polymarket halted trading after a monitoring script it loaded from a vendor was replaced with malicious code, and Binance paused withdrawals after funds left its hot wallets in what it later estimated as about 6.3 billion dollars of impact. Neither incident needed a smart contract bug. Both turned access that the victim already trusted into the attack. This post explains what happened, how each chain worked at a high level, what to do in the first 72 hours if something similar hits you, and the server and application controls that break both chains.

TL;DR

  • Polymarket: a DebugBear real-user-monitoring script on polymarket.com was replaced with malicious JavaScript that abused logged-in trading sessions; about 2.5 million dollars was traced to the attacker, and Polymarket says affected users will be made whole.
  • Binance: its preliminary view is that a compromised DevOps engineer’s laptop led to a service container that submitted unauthorized withdrawals; Binance estimates about 6.3 billion dollars of impact, about 3 billion frozen, and says it found no sign of leaked private keys.
  • Neither chain broke cryptography. One abused a trusted device and pipeline, the other a trusted script and session.
  • The first hour decides the damage: pause the money path, cut the compromised component out, and preserve evidence before rebuilding.
  • The controls that break both chains are boring and proven: managed admin devices, short-lived access, second approval for high-value actions, velocity limits, a short list of third-party scripts with SRI and CSP, and tested kill switches.

What happened on 29 October 2026?

29 October 2026, two incidents in one eveningALL TIMES UTC, FROM PUBLIC REPORTS17:0018:0019:0020:0021:0022:0023:00POLYMARKETUsers report drained accountsDebugBear script removedCancel-only modeTrading backBINANCEHot wallet outflows beginCircle and Tether freezeBinance: investigatingWithdrawals pausedSOURCES: BLEEPINGCOMPUTER, TRM LABS VIA YAHOO FINANCE, ISSUER STATEMENTS. FIGURES STILL MOVING.
Timeline of the Polymarket and Binance incidents on 29 October 2026 in UTC, from first reports to the trading halt and the withdrawal pause

The Polymarket incident came first. Users began reporting drained accounts in the late afternoon UTC. Between 17:50 and 17:56 UTC the attacker’s wallet made a burst of transactions against Polymarket’s token contract, and at 17:59 UTC Polymarket shipped a production build whose commit message removed the DebugBear RUM script. Six minutes later the exchange went into cancel-only mode, trading was halted as a precaution, and it was back online at about 19:05 UTC.

The Binance incident started roughly an hour after that. According to TRM Labs, outflows from Binance hot wallets began at about 20:05 UTC, with most transfers inside about 20 minutes. By 21:25 UTC Circle had frozen more than 800 million USDC and Tether more than 1.567 billion USDT linked to the theft, and Binance had said it was investigating a potential security issue. Withdrawals were paused that evening. Early on 30 October Binance put the total impact at about 6.3 billion dollars, said about 3 billion was frozen on-chain, and promised to cover losses from its SAFU fund and company funds.

No source has linked the two incidents. They share a date and a pattern, not an attacker.

How did the Polymarket attack work?

DebugBear is a UK web performance monitoring company. Its real-user-monitoring product works the way most analytics and monitoring tools work: the customer pastes a script tag into the page, and the browser loads JavaScript from the vendor’s server on every visit. That script runs with exactly the same trust as the site’s own code.

On 29 October the file served from DebugBear’s infrastructure was replaced. According to BleepingComputer and Hudson Rock, the malicious version checked whether the visitor was logged in to Polymarket, looked at their balance and positions, and then used the session that was already open to sell positions or move tokens to an attacker-controlled address. It reported results back to a DebugBear subdomain. Nobody’s password or seed phrase had to be stolen, because the page itself already had the authority to act.

About 2.5 million dollars was traced to the suspected attacker wallet, with other trackers putting the total between about 2.2 and 2.75 million across roughly 700 addresses. Polymarket has not published its own figure, has said that “anyone who has been impacted will be made whole”, and has referred the case to law enforcement. DebugBear has told customers of its RUM product to remove the embed code from their websites.

How did the Binance incident work?

Binance’s account is preliminary and second-hand so far, so treat this section as the current best picture rather than a final root cause. Reports quoting Binance say its investigation points to a compromised DevOps engineer’s laptop. From there, an attacker may have reached a service container that is allowed to submit withdrawal transactions, and used it to submit unauthorized ones. Binance says it found no evidence that wallet private keys leaked, and that it revoked the affected address authorization.

TRM Labs says the activity spanned ten blockchains, which points to a compromise of the signing infrastructure rather than of one wallet. On Ethereum, reports describe the attacker using EIP-7702, an account feature that lets a wallet delegate execution to contract code, so that a hot wallet pointed at a malicious contract that swept incoming funds. On other chains, assets moved through ordinary signed transactions.

TRM Labs and Chainalysis attribute the operation to TraderTraitor, a North Korean group linked by the FBI to the 1.5 billion dollar Bybit theft of February 2025. Binance has not confirmed the attribution. Stablecoin issuers, Ripple, World Liberty Financial and the Arbitrum Security Council froze or blocked part of the funds, while the attacker swapped some stablecoins into ETH and BTC, which issuers cannot freeze.

What do the two incidents have in common?

Question Polymarket Binance
Entry point A vendor’s script, loaded on every page view An engineer’s laptop (preliminary)
Trusted thing abused The logged-in session in the user’s browser A service container allowed to submit withdrawals
Bug in a smart contract? No No
Keys stolen? No passwords or seed phrases reported No evidence of leaked private keys, per Binance
Losses About 2.2 to 2.75 million dollars About 6.3 billion dollars estimated, about 3 billion frozen
Stopped by Removing the script, cancel-only mode, trading halt Pausing withdrawals, issuer freezes, revoking authorization
Attribution None published TraderTraitor, per TRM Labs and Chainalysis

The common thread is a trust boundary drawn in the wrong place. Polymarket trusted a vendor’s code as if it were its own. Binance, on its preliminary account, let a path that started at a laptop end in the ability to move money. In both cases the systems did exactly what they were allowed to do, and that is why the attacks were fast.

What do the numbers say, and what do they not?

The 6.3 billion dollar figure is Binance’s own estimate, and TRM Labs counts about 6.36 billion across ten chains. It is not an audited loss: part of it is frozen, part may be recovered through court orders, and Binance says customer balances are covered. Polymarket’s 2.5 million is a trace of the attacker wallet, not an official count of victims. Several questions are still open on 30 October: Binance’s full attack path and post-mortem, when every network reopens for withdrawals, how the DebugBear file was tampered with, how long it was live, and whether any other DebugBear customer received it. We will update this post when the companies publish their own reports.

The first 72 hours if something similar hits you

Most organisations will never hold six billion dollars in a hot wallet, but almost every one has a laptop with production access and a page that loads someone else’s script. If either of those turns against you, the order of work matters more than the speed of any single step.

Hour 0 to 1: stop the bleeding

  1. Pause the money or data path. Payouts, withdrawals, bulk exports, outbound transfers. Polymarket went to cancel-only mode in about six minutes; Binance paused withdrawals. A pause you can apply without a deploy is worth more than any forensic tool.
  2. Cut the compromised component out. Remove the third-party script from the page, or isolate the laptop from the network and revoke its VPN, SSH certificate and SSO sessions.
  3. Revoke what the component could use. Rotate the credentials, tokens and API keys it could reach. Invalidate every user session if a script could act inside the browser.
  4. Preserve evidence before you clean. Take a disk image or memory capture of the laptop, keep web server and CDN logs, and save a copy of the malicious script exactly as it was served.

Hour 1 to 24: understand and contain

  1. Find every place the component reached. Bastion logs, container audit logs, signing service logs, CDN access logs.
  2. Ask the people who can freeze. In crypto that means stablecoin issuers and exchanges; for card or bank payments it means your processor. Freezes worked here because they were requested within the hour.
  3. Tell users what you know and what to do. Short, factual, and with a clear statement on reimbursement if you have one. Warn about phishing, because attackers follow incidents with fake support messages.
  4. Report to law enforcement and, where required, your regulator or data protection authority.

Hour 24 to 72: rebuild and reopen carefully

  1. Rebuild, do not clean. Reinstall the laptop, redeploy the container from a known-good image, and re-issue every credential from scratch.
  2. Reopen in steps. One network, one product or one region at a time, with lower limits and extra monitoring.
  3. Publish a preliminary timeline, and promise a full post-mortem with a date.

Prevention on the server and operations side

  • Treat admin laptops as production. Full disk encryption, EDR, automatic updates, and a separate browser profile or a separate device for production work. A laptop that can reach the signing pipeline is part of the signing pipeline.
  • Never keep long-lived access on the laptop. Reach production through a bastion or VPN with multi-factor login, using SSH certificates that expire within hours and hardware keys for signing. A stolen laptop should hold nothing that still works tomorrow.
  • Split the power to move value. The container that submits a withdrawal should not be the one that approves it. High-value actions need a second person or a separate system to approve, ideally on a different device.
  • Put velocity limits in code. Maximum amount per hour, delays for new destination addresses, and an automatic pause when volume jumps. Binance’s outflows took about 20 minutes; a limit that triggers in two would have changed the size of the loss.
  • Watch the egress, not only the login. Alert on unusual destinations and unusual volume from wallets, databases and file stores, not only on failed logins.
  • Keep the kernel and the host hardened. Privilege escalation on the laptop or the container host is often the step between a phishing click and production. Our five-setting kernel hardening guide is a good baseline.

Prevention in the application

  • Keep the list of third-party scripts short. Every analytics, monitoring, chat or A/B testing tag can read and change everything on the page. Logged-in pages that can move money should carry as few as possible, ideally none.
  • Self-host or pin what remains. Copy the vendor’s script to your own server and update it deliberately, or load it with Subresource Integrity (an integrity hash), so that a changed file is refused by the browser instead of executed.
  • Deploy a Content Security Policy. script-src limits where code can load from, and connect-src limits where the page can send data. The Polymarket script reported back to a vendor subdomain; a tight connect-src makes that harder to hide.
  • Ask again before sensitive actions. Withdrawals, transfers, payout address changes and API key creation should require a passkey or second factor, not only an existing session. A script can ride a session; it cannot touch a passkey.
  • Have a kill switch for every vendor. A feature flag or a configuration value that removes a tag without a full deploy. Polymarket’s fix was a build; for most teams a flag is faster.

Check your own setup

Tick what is already true for your servers and your web application. The list below shows what to close first.

A field note from our own setup

We looked at these two blogs and our own operations through the lens of both incidents. On the application side, neither adnancanturk.com nor erkanozdogan.com loads a single third-party script: no analytics tag, no monitoring snippet, no font CDN. Everything the browser runs comes from our own server, so a compromised vendor file has nothing to hide in. On the operations side, our servers are reached only through a jump host and a VPN with a second factor, and SSH access is moving to short-lived certificates from our own certificate authority, so a lost laptop does not carry keys that keep working. That is not because we expected a DebugBear-style attack. It is because the cheapest third-party script to secure is the one you never load, and the cheapest key to rotate is the one that expires on its own.

If you use Binance or Polymarket

Use only the official apps and websites, and ignore anyone who contacts you about “recovering” funds; incidents like this are always followed by phishing. Watch the official status pages for withdrawal and reimbursement updates. Polymarket users can review their account activity for the afternoon of 29 October; reports so far say the script abused open sessions, so revoking token approvals is not the documented fix. Nothing in this post is financial advice.

The short version

Neither of the 29 October incidents broke cryptography or a smart contract. One turned a monitoring script into an attacker inside the user’s browser, the other reportedly turned an engineer’s laptop into a path to the withdrawal system. Both were possible because something was trusted more than it needed to be. Shorter vendor lists, short-lived access, a second approval for anything that moves value, hard limits and a tested pause button would have broken each chain at more than one link.

FAQ: Binance and Polymarket, October 2026

What happened to Polymarket on 29 October 2026?

A real-user-monitoring script from DebugBear, loaded on polymarket.com, was replaced with malicious JavaScript. It used logged-in sessions to sell positions or move tokens to the attacker. About 2.5 million dollars was traced, trading was halted for about an hour, and Polymarket says affected users will be made whole.

How much did Binance lose in the October 2026 incident?

Binance estimated about 6.3 billion dollars of impact and TRM Labs about 6.36 billion across ten blockchains. About 3 billion was frozen on-chain, and Binance says it will cover user losses from its SAFU fund and company funds. The figure is an estimate, not an audited loss.

Was the Binance incident caused by a hacked laptop?

That is Binance’s preliminary view as reported by the press: a compromised DevOps engineer’s laptop may have given access to a service container that submitted unauthorized withdrawals. Binance has not published a full post-mortem, so the attack path is not yet confirmed.

Were Binance private keys stolen?

Binance says it found no evidence that wallet private keys leaked. The reported mechanism abused systems that were already allowed to request and sign withdrawals, and on Ethereum an EIP-7702 delegation pointed a hot wallet at a malicious contract.

Are the Binance and Polymarket incidents connected?

No link has been established. They happened about three hours apart with different mechanisms: a vendor script supply chain at Polymarket and a suspected device and signing pipeline compromise at Binance. Analysts attribute only the Binance theft, to TraderTraitor.

Who is TraderTraitor?

TraderTraitor is a North Korean state-linked group that the FBI tied to the 1.5 billion dollar Bybit theft in February 2025. TRM Labs and Chainalysis attribute the Binance operation to it; Binance and law enforcement have not confirmed this publicly.

Should Polymarket users revoke token approvals?

Reports describe the script abusing open trading sessions, not approvals users had signed, so revoking approvals is not the documented remedy. Review account activity for 29 October and follow Polymarket’s official reimbursement guidance.

How can a website protect itself from a compromised third-party script?

Remove scripts you do not need, self-host or pin the rest with Subresource Integrity, and enforce a Content Security Policy with tight script-src and connect-src. Require a passkey or second factor for sensitive actions, so a script riding a session cannot complete them.

What should a company do in the first hour of a breach?

Pause the path that moves money or data, cut out the compromised component, revoke the credentials and sessions it could use, and preserve evidence before cleaning anything. Then contact parties who can freeze funds and tell users what you know.

How should admin laptops be secured to prevent incidents like Binance’s?

Manage them like servers: disk encryption, EDR, automatic updates and no personal browsing in the production profile. Reach production only through a bastion with multi-factor login and short-lived SSH certificates, and require a second approval for high-value actions.

Sources