Incidents

Polymarket Halts Trading After Supply Chain Attack Through Third-Party Script

A hijacked third-party JavaScript file enabled unauthorized actions on Polymarket accounts. The platform confirmed the incident and paused trading.

Polymarket Halts Trading After Supply Chain Attack Through Third-Party Script

On October 29, Polymarket confirmed a security incident involving a compromised third-party vendor and temporarily halted trading. Analysis of the malicious script showed that it could carry out actions through a user’s active session and move that user’s assets.

What happened

According to an analysis by Hudson Rock and reporting by BleepingComputer, the code was delivered through the infrastructure of DebugBear, a website performance monitoring service. Scripts like this run in the visitor’s browser and can access the context of the page they are embedded in.

The researchers said the code targeted users who were logged in to Polymarket. It could check their holdings, sell their positions, and try to transfer their assets. BleepingComputer analyzed a copy of the script separately from the researchers’ report.

Polymarket said it had fixed the problem and referred the matter to law enforcement. Its status history shows a disruption on October 29 from 18:05 to 19:05 UTC. The incident was then marked as resolved.

What we know about the impact

No confirmed total loss or number of affected users has been published. The amounts visible in the wallet identified by the researchers should not be taken as the total stolen. A wallet’s balance alone does not show where all of the funds came from.

The incident also matters for companies outside the crypto industry. A third-party vendor’s code can run in the same browser where a customer uses a site’s most sensitive features.

What to do now

  • Users should review their transaction history and report any unfamiliar transactions through the platform’s official channels.
  • Administrators of websites that use DebugBear should check the vendor’s notices and confirm whether its code is present on their sites.
  • Website owners should take inventory of their third-party scripts and decide how to disable them quickly in an emergency.
  • During incident analysis, preserve copies of the scripts, the logs, and the timestamps of any integration changes.

SecurHUB commentary

An application security review should include code supplied by partners. Application penetration testing helps determine what a script running in a logged-in customer’s session is able to do.

Sources: Polymarket, Hudson Rock, BleepingComputer

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk