1. News
  2. Alerts
  3. Polymarket · Breach
AlertPolymarket · Breach2 min read

Polymarket pauses trading after hackers hijack a hidden website tool

Polymarket stopped trading for about an hour after hackers used an outside website tool to push crypto-stealing code. About $2.5 million was traced to the attacker.

By the Dashline deskSource: BleepingComputer
Polymarket pauses trading after hackers hijack a hidden website tool
Photo: Sebastiaan ter Burg from Utrecht, The Netherlands, CC BY-SA 2.0
Act this week
What happenedHackers compromised DebugBear, a third-party website monitoring service, and used it to send crypto-stealing code to Polymarket users.
Who is affectedPolymarket.com traders who were logged in, and any website that uses DebugBear's real user monitoring script.
What to do
  1. 1Check your Polymarket balance, positions and transaction history for anything you did not do.
  2. 2Contact Polymarket support if you see unfamiliar activity, since it says affected traders will be reimbursed.
  3. 3Keep only what you need to trade on any crypto platform and move the rest to a wallet you control.
  4. 4If you run a website that uses DebugBear, remove its embed code as the company advised.

Polymarket, a prediction market platform where people trade on how events turn out, halted trading for about an hour on Thursday. Hackers had slipped crypto-stealing code onto its website through an outside tool. About $2.5 million in assets has been traced to a wallet believed to belong to the attacker. Polymarket says everyone affected will be reimbursed.

What happened

The weak link was not Polymarket's own systems. It was DebugBear, a service that tracks how fast websites load. Sites that use it add a small piece of code, called JavaScript, to their pages. Hackers compromised DebugBear and used that channel to send harmful code to Polymarket visitors. Polymarket put its exchange into cancel-only mode at 2:05 p.m. ET. It marked the issue resolved at 3:05 p.m. ET.

What the code did

According to BleepingComputer's analysis, the script checked whether a visitor was logged in to Polymarket. If so, it tried to use that person's existing session and Polymarket's own trading tools to move money. For some users it tried to sell their positions automatically. For others it tried to send their prediction-market tokens straight to the attacker's wallet. It also tried to convert crypto holdings into assets that could be moved.

The script also reported account details, wallet addresses and balances back to DebugBear's servers. That raises questions about how much access the attackers had to the company's systems.

Who it affects

The main group is traders who were logged in to Polymarket.com, the company's international platform. Any other website that uses DebugBear's real user monitoring script could also be exposed. DebugBear has told customers to remove that code from their sites. Nothing in the reporting points to risk for people who do not use Polymarket.com.

What to do

The alert box above lists the steps. The short version: look over your account for anything you did not do, and contact support if something looks wrong.

What is not known yet

Polymarket has not said how many users were affected, how much was actually stolen, or how reimbursement will work. The dollar figures also differ by source. BleepingComputer saw the suspected attacker wallet send about 28.6 million POL, worth roughly $2.57 million, to three other wallets. Hudson Rock, a security research firm, said the wallet held about $2.19 million when it looked.

DebugBear's own website was down at the time of writing, showing a Cloudflare error. It is unclear whether that is part of its cleanup or another effect of the attack. BleepingComputer has asked both companies for comment.

The takeaway

A tool a website borrows from another company can put your crypto at risk, so keep only what you need to trade on any platform.

More articles

You should really read these.

Next step

Let’s talk