-
Polymarket stopped trading on its international platform on October 29, 2026, after attackers made unauthorized sales and withdrawals from user accounts.
-
Researchers linked the attack to a bad script from DebugBear, a website performance monitoring service.
-
Blockchain trackers estimate losses near $2.7 million, but Polymarket has not confirmed that figure, and the company promises to repay affected traders.
Polymarket paused trading on its international platform on October 29, 2026. Attackers had carried out unauthorized transactions and pulled money out of user accounts. Several traders raised the alarm first. They saw their prediction-market positions sold without their approval. Some also found withdrawals they never approved.
The attack targeted traders who were logged in to the platform. The company later blamed a hacked outside service provider. Polymarket says it has fixed the problem. It also says it will pay back the people who lost money.
Polymarket Halts Trading as Traders Report Missing Funds
Polymarket explained the problem in an update on its official status page. According to the company, one of its third-party service providers had been compromised. Polymarket then restricted trading while it looked into the attack.
Its status page became the main place where the company shared updates. The company also said it had sent the matter to law enforcement. It promised to reimburse every user hurt by the incident. The update gave users three key facts. A provider was compromised, trading was restricted, and police had the case.
The platform first moved its exchange into cancel-only mode. Users could still cancel their open orders in this mode. They could not place any new trades. Polymarket also paused its relayer actions. Relayers are the tools that send signed transactions to the blockchain.
Polymarket later said it had found and fixed the issue. It kept trading halted for a short time as a precaution. The status page recorded the incident as resolved at 7:05 PM UTC on October 29. The disruption lasted about one hour. Trading then resumed.
Rogue Script from a Monitoring Service Blamed for the Attack
Cybersecurity researchers traced the attack to a hacked script from DebugBear. This company runs a website performance monitoring service. Website owners can add its tools to their pages. The tools track how a site performs and how users experience it. They work by running JavaScript on the pages that visitors open.
According to researchers at Hudson Rock, the bad JavaScript hunted for active Polymarket sessions. It then used the trading permissions that logged-in users already held. The code did not depend only on stolen passwords or private keys. It tried to use sessions that were already signed in. In short, the attackers aimed at active permissions instead of passwords. Think of a signed-in session as an open door. The script walked through it instead of picking the lock.
Reports say the script tried to sell users’ prediction-market positions. It then tried to send the money to a wallet that the attackers controlled. Depending on the account, it could also try to move prediction-market tokens straight to another address.
One news report said a reporter studied a copy of the script. The code could check user balances, sell positions, and move assets. Researchers also found a crypto wallet address inside the code. The script named that address as the place to send stolen funds.
DebugBear later admitted it was dealing with an ongoing security incident. The company told customers of its Real User Monitoring product to remove the monitoring JavaScript from their websites. It gave this advice while it investigated the compromise.
Losses Near $2.7 Million as Polymarket Promises Repayment
Blockchain investigations give a rough idea of the damage. Polymarket has not confirmed the exact loss. Reports say investigators tracked about $2.7 million in losses after the incident. Other estimates from blockchain security researchers point to roughly $2.71 million. Bubblemaps, a blockchain analytics firm, estimated that around 700 users were affected.
Bubblemaps’ estimate counts people, not dollars. Polymarket has not confirmed that user count either. Three sources gave three views of the harm. One counted the money lost, one offered a similar estimate, and one counted the victims. These numbers come from independent investigations. They are not an official loss figure from Polymarket.
Polymarket has confirmed that the issue on its international platform is fixed. Its status update lists the compromise, the trading pause, and the repair. It also announced that it will fully reimburse the affected traders.
The attack raises fresh worries about outside services built into crypto platforms. A platform’s own systems can stay safe. Even so, bad code from an outside provider can reach signed-in sessions. That code can then trigger unauthorized transactions.
This is not the first time Polymarket has faced a problem like this. In June 2026, another hacked vendor reportedly let malicious code reach the platform’s pages, causing users to lose millions of dollars. Polymarket later confirmed a $3 million loss after a vendor injected malicious code.
The latest attack shows why companies should closely monitor their third-party software. They should also review the scripts running on their pages. Limiting the permissions that third-party tools receive is another key step.