Skip to content
Crypto.world

The Ledger

Polymarket Restores Trading After One-Hour Third-Party Security Halt

Polymarket paused trading on its international platform for about an hour on October 29 after a third-party provider was compromised. Hudson Rock researchers found wallet-draining code in a script served from DebugBear infrastructure, but the number of affected traders and total losses remain unverified.

Polymarket Restores Trading After One-Hour Third-Party Security Halt

Polymarket’s international exchange paused trading for about an hour on October 29 after the company found that a third-party provider had been compromised. The outage began at 6:05 p.m. UTC, according to the platform’s status history, which marked the incident resolved at 7:05 p.m. UTC. Polymarket said it fixed the issue, referred the incident to law enforcement and would reimburse affected traders.

Cancel-only mode preceded the halt

Polymarket first placed the exchange in cancel-only mode, allowing users to cancel orders while blocking new orders and trades; it also paused relayer actions during its investigation. At 6:37 p.m. UTC, the company’s status page said it had identified and fixed the issue affecting Polymarket.com, then halted trading as a precaution while it brought the platform back online. The page recorded the incident as resolved at 7:05 p.m. UTC.

“One of our third party providers was compromised, and we have referred this to relevant law enforcement,” Polymarket said on its status page. The Associated Press reported that the company referred the incident to a law enforcement agency in the United Kingdom and that trading resumed Thursday afternoon. Polymarket’s public notice did not name the provider or describe how the compromise occurred.

Researchers found a suspect monitoring script

Hudson Rock researchers said they retrieved and examined a 15,187-byte JavaScript file served from a DebugBear domain. Their analysis found code that searched for Polymarket’s logged-in trading client and signer, inspected account positions and attempted to sell or transfer assets to a designated address. The firm said its two downloads returned identical files, but it did not execute the code or test whether the attempted transactions succeeded.

The researchers also found a Polymarket production-build record describing removal of the DebugBear monitoring script. That record supports that the integration was removed from the observed build, Hudson Rock wrote, but does not establish exactly when the change was deployed or how long users were exposed. The researchers said the initial compromise method, number of affected users and total losses attributable to the incident were still unknown.

The loss total is not confirmed

A balance snapshot examined by Hudson Rock showed about $2.19 million in assets at an address hard-coded in the script as its fallback recipient. The researchers cautioned that the balance was not a verified tally of stolen funds: they had not traced the assets transaction by transaction or confirmed that the holdings came from Polymarket users. It should not be treated as the breach’s loss figure.

Polymarket has promised to make affected traders whole, but its status notice does not explain how users can establish eligibility or when reimbursements will be completed. The company has not publicly identified the compromised provider in that notice. Those details, along with the number of affected accounts and a verified loss total, remain unanswered.

Sources

  1. Original source · Status page Polymarket Status status.polymarket.com

Other pages read

  1. The Associated Press apnews.com
  2. Hudson Rock / InfoStealers infostealers.com

Related stories

Explore

More articles