The Ledger
Bitquery Reports $2.73M Lost Across 737 Polymarket Accounts
Bitquery’s on-chain analysis reports that 737 Polymarket accounts lost about $2.73 million in withdrawals on Oct. 29. Polymarket says a compromised vendor script affected some users and says it is returning $3.9 million, including funds taken and pause-related losses.

“A third-party vendor whose performance-monitoring script loaded on polymarket.com was compromised.”
Polymarket, in its Oct. 30 incident update
Polymarket says an attacker replaced a vendor’s performance-monitoring script with code targeting users. The company says that, for some people who had the site open during a short window, the code used their active sessions to sell positions and move funds from their wallets. Blockchain analytics firm Bitquery reports that 737 accounts lost about $2.73 million during a one-hour period on Oct. 29. Polymarket’s status-page update says it is returning $3.9 million to traders.
What the compromised script could do
Polymarket said the vendor’s performance-monitoring script loaded on Polymarket.com. The attacker replaced it with code built to target the platform’s users. The company says that, for people who had the site open during a short window, the script used their active sessions to sell positions and move funds out of wallets. Bitquery’s analysis does not independently establish how the approvals behind the withdrawals were made or who made them.
Bitquery’s on-chain analysis found that withdrawals carried valid approvals and went through Polymarket’s own relayer. Its report says no smart contract was broken. That describes how the transactions were processed; Bitquery says the chain record does not show who made the approvals or how.
737 accounts lost about $2.73 million
Bitquery places the withdrawals between 17:10 and 18:10 UTC on Oct. 29. It reports that 737 accounts lost about $2.73 million in that hour and separately identifies 985 drains on the main route. Bitquery says its on-chain figures are based on Polygon and Ethereum data.
The incident record says Polymarket identified unauthorized activity at 17:38 UTC and marked the incident resolved at 18:06 UTC. The company says it removed the compromised script, cleared caches, paused trading and its relayer to stop further drains, then reset active login sessions. It also says it referred the case to law enforcement and is investigating the attacker.
Polymarket says refunds total $3.9 million
In its Oct. 30 update, Polymarket said 95% of affected wallets had been refunded in full through a combination of reimbursements and goodwill payments. The company says the $3.9 million total includes $2.7 million for funds taken and another $1.2 million to cover pause-related losses.
Polymarket said it would also pay traders for positions taken during the attack if the script moved or force-sold them, valuing the positions when they were taken and including slippage. For pause-related losses, it covered the difference from a position’s value when trading paused if the trader held that position at the time and it lost value because a market ended during the pause or the trader sold right after trading reopened. The company says it identified eligible wallets using on-chain and trading data, without requiring users to submit a claim.
A front-end incident, with cause not independently established
The incident involved a third-party script loaded on Polymarket.com, according to the company. Bitquery’s analysis found valid approvals and withdrawals processed through Polymarket’s relayer, and says no smart contract was broken. The report says its on-chain findings cannot establish who made the approvals or how they were made.
Polymarket says it is redeploying third-party scripts with additional integrity controls and monitoring, including stronger content security policy, version pinning and sandboxing. The company’s update gives its refund figures, while Bitquery’s analysis records the scale of the withdrawals. Bitquery reports that 737 accounts lost about $2.73 million during the one-hour period on Oct. 29.
Sources
- Original source · Status page Polymarket Status status.polymarket.com
Other pages read
- Bitquery bitquery.io