Latest / Decrypted: The UK Cyber Briefing / Polymarket's losses began with a third-party monitoring script
Transcript
- 0:03Good morning, and welcome to Decrypted.
- 0:05I'm Belinder. It's Monday, the second of November, twenty twenty-six, and this is the morning edition.
- 0:11Polymarket's losses began with a third-party monitoring script.
- 0:16On 29 October, the prediction market Polymarket halted trading after users reported money leaving their accounts.
- 0:25Polymarket's own code wasn't blamed.
- 0:27Researchers pointed instead at a script loaded from a website monitoring supplier.
- 0:32And that's a lesson any UK organisation with a login or checkout page can use this week.
- 0:37So, what actually happened?
- 0:41Polymarket said one of its third-party providers had been compromised, and that affected traders would be made
- 0:46whole. Hudson Rock, a threat intelligence firm, then examined a script served from DebugBear's servers and found
- 0:53wallet-draining code. SecurityWeek describes DebugBear as a UK-based performance monitoring company.
- 1:00DebugBear said it was impacted by an ongoing security incident, and told customers to remove its snippet.
- 1:06Polymarket's build records show the script removed at 17:59 U T C on 29 October.
- 1:12Loss estimates differ. About $2.
- 1:1519 million, $2.65 million and $2.
- 1:1971 million, depending on who's counting.
- 1:22None is a verified total, and how the script was tampered with is still unknown.
- 1:28Why could a monitoring tool do this?
- 1:30Think of it like giving the meter reader a key to your house, then letting them change what the key does whenever
- 1:35they like. Your browser runs a supplier's script with the same authority as the site's own code.
- 1:41Hudson Rock found no routine that steals passwords or seed phrases.
- 1:45The script did something neater.
- 1:47It found the live trading tools in the logged-in page, then either sold positions and moved the proceeds, or
- 1:54sent position tokens to an attacker's address.
- 1:56It's a forger who never needs the safe combination, because the cashier has already opened the till.
- 2:03So what does the defender see?
- 2:05Very little. The site's code hadn't changed, and the malicious file lived on a supplier's server.
- 2:11Hudson Rock noted that a scan recorded Polymarket loading the script, and allowing its host in the content security
- 2:17policy. That's the browser's list of outside sources permitted to run.
- 2:21The list worked as designed.
- 2:23It simply trusted the supplier completely.
- 2:25The visible symptoms were odd orders, and customers asking where their money went.
- 2:30SecurityWeek notes an earlier compromise of a third-party provider at Polymarket in June.
- 2:35Repeats like that suggest the supplier relationship, not one bad file, is the weak point.
- 2:41So what's the Secure by Design lesson?
- 2:44Keep third-party code out of any page where money moves or people sign in.
- 2:49Hudson Rock advises removing unnecessary third-party scripts from logged-in and signing flows.
- 2:55It also advises pairing Subresource Integrity, which makes the browser refuse a file whose fingerprint has changed,
- 3:02with a restrictive policy.
- 3:03There's a cost. Monitoring moves to public pages, or you host a fixed copy yourself.
- 3:09Fingerprint pinning breaks suppliers that change live scripts, so you need versioned files, and a review each
- 3:15time they change. And someone must keep an inventory of every script on login and payment pages, and own it.
- 3:23For a UK director, the question this week is simple.
- 3:26Can your team list every outside script on those pages, and say who approved each one?
- 3:32As always, this is opinion, not advice.
- 3:36That was Decrypted, with me, Belinder.
- 3:39The written version and every source are linked in the show notes.
- 3:43Thanks for listening. Stay patched, and stay sceptical.