Polymarket, the crypto-based prediction market, says one of its third-party providers was compromised on October 29. Malicious code used traders' logged-in sessions to sell their positions and move funds out of their accounts. One on-chain tally puts the damage at 995 accounts and about $2.65 million. The company briefly halted trading on its international platform and has promised to reimburse those affected. This is the second time in four months that a compromised supplier has turned Polymarket's own website against its users.
What happened on October 29
As reports of drained wallets spread on social media, Polymarket put its exchange into cancel-only mode. In this mode users can withdraw existing orders, but no new orders or trades are processed. It also paused relayer actions. A relayer is a service that submits signed wallet transactions to the blockchain on users' behalf. Crypto Briefing reported that users were told not to connect wallets or sign transactions while the situation was unclear.
According to crypto.news, Polymarket's status page shows a halt from 18:05 to 19:05 UTC. At 18:37 UTC the company said it had found and fixed the problem, that a third-party provider had been compromised, and that the matter had been referred to law enforcement. Trading resumed at 19:05 UTC. The incident notice covered the international platform only and did not name Polymarket's separate US exchange.
How the attack worked
This was a front-end supply-chain attack, not a break-in to Polymarket's smart contracts. Many websites load small pieces of code from outside vendors, for example to measure page speed or track errors. If an attacker compromises one of those vendors, their code runs inside the real website with the same access as the site's own code.
Researchers linked the incident to a performance-monitoring script loaded by Polymarket's site. The recovered code tried to reach the trading client and the signer, the component that authorises wallet actions, inside an active session. Because victims had already opened the genuine site and logged in, they did not need to click a phishing link. Reuters, citing a person familiar with the matter, identified the supplier as DebugBear, a UK firm whose real-user monitoring product works through JavaScript embedded in customers' websites. DebugBear acknowledged an ongoing security incident and told customers to remove that embed code.
Crypto Briefing noted that there was no evidence of a flaw in Polymarket's core contracts. Traders use non-custodial proxy wallets on the Polygon network, and trades settle in pUSD, a token backed 1:1 by the USDC stablecoin. The weak point was the website that sits between users and that on-chain system.
How much was lost: the figures differ
There is no official loss total yet, and the public estimates do not fully match. U.Today cited blockchain analyst Conor Grogan, who counted 995 drained accounts and losses of $2,654,211.42. The largest single losses were about $341,000 and $307,000. Grogan said the attacker converted all the stolen funds into POL, Polygon's native token, probably to stop them from being frozen.
A separate observer, StarPlatinum, tracked a suspected recipient wallet. It started receiving funds at about 17:05 UTC, roughly an hour before the official halt. It held about $412,000 by 17:25, $2.02 million by 17:50 and about $2.68 million by 18:05, or around 28.6 million POL.
Individual claims are harder to reconcile. A trader posting as Car said about $800,000 had disappeared from his account, that all his positions had been sold, and that a friend had lost $600,000. Those figures are larger than the biggest losses in Grogan's tally, and none of the sources explains the gap. Polymarket has not confirmed individual amounts or adopted any outside estimate.
The way users lost money also varied. Some reported assets transferred out, and others reported positions sold before they meant to close them. A screenshot shared during the incident showed a signing request tied to Polymarket's domain, with a "DepositWallet" field and Polygon's chain identifier. It did not show a completed transaction.
A repeat of June
The breach follows a similar attack in June, when hackers compromised a different vendor and injected malicious JavaScript into Polymarket's front end. Reports of that loss differ slightly. U.Today puts it at about $2.94 million from at least 11 wallets, and Crypto Briefing at roughly $3 million in pUSD from fewer than 15 wallets. Crypto Briefing also lists a May breach of an internal POL wallet, with losses estimated at $573,200 to $700,000.
After those incidents, Polymarket said it had stepped up monitoring of third-party scripts. A second vendor-based attack within months raises questions about whether those controls were enough. Other firms are reacting too. Trust Wallet CEO Felix Fan said his wallet was not affected by the Polymarket or Binance attacks. He added that the company has drawn up new operating procedures and code-hardening plans, though it has not published the details.
What affected traders should do now
- Use official channels only. Polymarket's public statements and status page are the authoritative sources for reimbursement news. Treat unsolicited links or messages offering refunds with caution.
- Review your account activity. Note any positions sold or funds moved between about 17:00 and 19:05 UTC on October 29, so you can compare them with whatever compensation process Polymarket announces.
- Be careful with signature prompts. This attack ran inside the real website, so a familiar page is not proof that a signing request is safe. Read what you are approving.
Reimbursement has been promised but not fully defined. Polymarket says "anyone who has been impacted will be made whole." It has not said whether sold positions will be valued at their price before the attack, at the price they were sold for, or by some other method. It also has not said that refunds have been paid.
What to watch
- Reimbursement terms: how Polymarket values positions sold without the owner's consent, and when payouts begin.
- A final loss figure from Polymarket, and whether it matches the roughly $2.65 million to $2.68 million estimates from on-chain observers.
- The full investigation: how the supplier was compromised, which DebugBear has not yet explained publicly, and what Polymarket will change in how its site loads outside code.
- The UK law-enforcement referral and the movement of the roughly 28.6 million POL linked to the suspected attacker wallet, which can be traced on Polygon.
- Other DebugBear customers: whether any other sites that embedded the monitoring script report similar problems.
