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.
Incidents
A flaw in Optimizely's signup process let an attacker act as an admin on customer accounts and alter scripts served on at least 178 organizations' sites.

On November 17, Optimizely disclosed a security incident affecting its Web Experimentation service. A flaw in the signup process allowed an unauthorized party to act as an existing user with administrator privileges on certain customer accounts and modify the JavaScript code in their projects. Palo Alto Networks Unit 42 and Netskope have described the malicious code, which reached the websites of at least 178 organizations.
According to Optimizely’s report, the first malicious changes to project code were made on November 16 at 07:51 UTC. The company detected the activity at 13:34, closed the vulnerability at 16:10, and by 22:24 had removed the injected code from all affected projects. Optimizely said no passwords were stolen; the attacker relied on publicly available information and a brute-force method to impersonate users. The company has engaged Mandiant to conduct an independent investigation.
Unit 42 and Netskope reported that the modified script was served from Optimizely’s own infrastructure. Their findings include theft of payment card data from web forms, swapping of cryptocurrency wallet addresses, and attempts to deliver tools that exploit vulnerabilities in Apple devices. Netskope noted that its telemetry came from a subset of its own customers, and that a recorded request to attacker infrastructure does not by itself prove a device was successfully compromised.
Optimizely stated that the incident affected only Web Experimentation; it found no impact on Feature Experimentation, its SDKs, or the legacy Full Stack service. The mere presence of the Optimizely script on a website does not mean that a customer’s project was modified. The company is confirming affected customers on an individual basis.
Organizations using Optimizely Web Experimentation should confirm directly with the vendor whether their projects were affected. The report gives an overall window of changes from 07:51 to 22:24 UTC on November 16, but Optimizely is providing exact time windows to each affected customer.
This incident shows that third-party code running in the user’s browser can compromise the security of an entire website. Penetration testing helps assess how third-party scripts are controlled and what data they can access.
Sources: Optimizely – incident report, Palo Alto Networks Unit 42, Netskope Threat Labs
Read more
A hijacked third-party JavaScript file enabled unauthorized actions on Polymarket accounts. The platform confirmed the incident and paused trading.
Coles is investigating a cybersecurity incident. So far it has found no evidence that customer, employee or supplier data was compromised or exfiltrated.
Stolen credentials let attackers push malicious Claude Code extension versions to Cursor's marketplace and access some of its customer data.
A free consultation with one of our experts — no obligation, in full confidence.
Let's talkWe'd like to use Google Analytics cookies to see how many people visit the site and which content is useful. We'll only set them if you agree. You can change your decision at any time via the “Cookie settings” link in the footer. Cookies Policy