1. News
  2. Alerts
  3. Polymarket · Hack
AlertPolymarket · Hack3 min read

Hackers drain about $2.7 million from Polymarket traders through a tampered website tool

A swapped-out speed-tracking script on Polymarket's site moved some traders' funds to hackers. Polymarket is paying back $3.9 million in total.

By the Dashline deskSource: The Hacker News
Hackers drain about $2.7 million from Polymarket traders through a tampered website tool
Photo: The Hacker News
Act this week
What happenedMalicious code replaced a page-speed script on Polymarket's site on October 29 and moved some signed-in traders' funds to hackers.
Who is affectedPolymarket traders who were signed in, especially with email or crypto wallet logins, and websites that load DebugBear's monitoring script.
What to do
  1. 1Reject any wallet signing request you did not expect.
  2. 2Check your Polymarket account and the status page for refund details.
  3. 3Use the status page form if your refund amount looks wrong.
  4. 4If you run a website, remove DebugBear's embed code and review other outside scripts.

Hackers got into Polymarket traders' accounts on October 29 without breaking into Polymarket itself. They replaced a small tool the site loaded from an outside company. That code sold some signed-in traders' positions and sent the money to the hackers. Polymarket says it is refunding about $2.7 million to 726 affected wallets.

What happened

Many websites load small pieces of code from other companies. Polymarket loaded a page-speed script from DebugBear, a company that measures how fast pages load for real visitors. Hackers took over DebugBear's web address through its domain registrar, the company that manages the address. That let them serve their own file in place of the real script, and the swapped file was Polymarket's copy.

Blockchain records show crypto worth about $2.64 million reached the hackers' wallet in under an hour. The first funds arrived at 17:10 UTC and the last at 18:02 UTC.

How the theft worked

The code borrowed the access a signed-in trader already had in an open Polymarket page. It then followed one of two paths, depending on how the trader signed in.

  • Crypto wallet logins: positions were moved straight to the hackers' wallet.
  • Email logins: positions were sold at ever-worse prices, then the money was moved out.

In both cases the code asked the account's own signer to approve its requests. Researchers say that alone does not prove a trader approved anything without seeing a prompt. A wallet provider may still ask the trader, refuse, or apply its own rules.

Who is affected

The main group is Polymarket traders who were signed in, especially with email or crypto wallet logins. Website owners are the second group. DebugBear has told customers of its monitoring product to remove its embed code from their sites.

There is some reassurance. Hudson Rock reviewed the malicious file without running it. It found no part that sends a password, a seed phrase or a private key to the hackers' server. Traders also do not need to file a claim to get money back.

What Polymarket is doing

Polymarket says it removed the script within the hour, cleared every cache, reset all active login sessions and paused trading until the site was clean. It has referred the case to law enforcement. By October 30, 689 of the 726 wallets had been refunded in full. The other 37 were being paid as they were checked.

Polymarket is also paying $1.19 million to about 5,500 wallets that lost money during the trading pause or had positions taken. In all, it is returning $3.9 million. It says it is bringing outside scripts back with extra safeguards.

What to do

The steps in the alert box above cover what traders and site owners should do now. The habit worth keeping is simple: if a wallet asks you to sign something you did not start, say no.

What is still unclear

DebugBear says its early findings point to an attack on one customer's website. It has seen no sign of a break-in to its own systems, though it is still looking. How the hackers got into the registrar account has not been explained.

The takeaway

Read every wallet signing request before you approve it, and reject any you did not expect, even on a site you trust.

More articles

You should really read these.

Next step

Let’s talk