A vulnerability in Optimizely’s experimentation service was leveraged to plant malware across 178 organizations’ sites, leading the vendor to issue an emergency patch and warn about the risks of third‑party scripts.
A critical flaw in Optimizely’s experimentation platform was weaponized by threat actors, allowing them to inject malicious JavaScript into the pages of 178 separate organizations.
How the vulnerability was exploited
The bug resided in the way Optimizely’s script loader handled third‑party code, permitting attackers to append arbitrary JavaScript that executed in the context of any site using the service. By compromising a single Optimizely account, the perpetrators were able to push malicious payloads to every client that relied on the platform for A/B testing and personalization.
Security researchers observed the injected code redirecting visitors to phishing pages, harvesting credentials, and loading cryptomining scripts. Because the malicious script was served from Optimizely’s trusted domain, many browsers and security tools failed to flag the activity.
Scope of the impact
The compromised sites spanned a range of industries, including e‑commerce, media, and SaaS providers. While the exact list of affected organizations has not been publicly disclosed, the breach demonstrates the systemic risk posed by shared third‑party infrastructure.
- Malware delivery via injected JavaScript
- Credential harvesting through fake login forms
- Unauthorized cryptomining on visitor browsers
Vendor response and mitigation
Optimizely responded within hours, releasing an emergency patch that hardened the script loading process and revoked compromised API keys. The company also issued guidance for customers to audit their implementations, rotate credentials, and monitor network traffic for anomalous script calls.
Customers are advised to implement strict Content Security Policy (CSP) rules, employ subresource integrity checks, and regularly review third‑party script permissions to reduce the attack surface.
For more insights on securing third‑party integrations, see the Technology section on uxc.news.
Read the full analysis on AskSumanta’s coverage of the Optimizely breach: AskSumanta coverage of Optimizely breach.
Track coverage on Momentum · More in Technology.
Comments
No comments yet.