Optimizely Script Hijack Delivers Card Skimmers & iOS

Introduction
A supply‑chain intrusion targeting Optimizely's Web Experimentation platform has been disclosed, revealing that malicious actors were able to embed harmful code into scripts that downstream customers load from the service. The breach affected a broad cross‑section of high‑profile web properties, with monitoring firm Report URI flagging the activity across numerous domains. The incident underscores how vulnerabilities in third‑party script delivery can propagate threats to a wide audience, delivering both payment‑card theft payloads and mobile exploit kits.
How the Compromise Occurred
Investigators traced the origin to a weakness in Optimizely's script generation process. By exploiting this flaw, the attacker was able to modify the JavaScript that Optimizely provides to its clients before it reached the final website. The altered scripts executed additional instructions once a visitor accessed an affected page, effectively turning a trusted library into a vector for malicious activity. The method highlights the risk inherent in relying on a single source for critical front‑end functionality.
Because the malicious code was injected at the script level, it was served to every visitor of the compromised sites without requiring separate server‑side compromises. This approach allowed the attackers to maintain a low profile while achieving broad coverage, as the malicious payload was delivered through a channel that is typically considered safe.
Impact and Affected Organizations
Report URI identified at least 178 distinct domains that were serving the tampered Optimizely scripts. Among the notable names are CNN, the BBC and Zoom, all of which are widely used by global audiences. The presence of card‑skimming code means that visitors who entered payment information on these sites could have had their credentials captured. In addition, iOS exploit kits were delivered, suggesting an intent to compromise Apple devices through browser or OS vulnerabilities. The dual‑purpose payload indicates a sophisticated operation that seeks both immediate financial gain and longer‑term device control.
The breadth of the affected portfolio demonstrates how a single vendor compromise can cascade across multiple industries, including media, communications and collaboration services. Organizations that rely on Optimizely for A/B testing, personalization or other web‑experiment features were placed at risk simply by using the service, regardless of their own security posture.
Mitigation and Defensive Measures
Defenders should adopt a layered approach to protect against similar script‑based attacks. First, implement regular integrity checks on third‑party scripts. Automated tools can compare the current version of a library against a known‑good hash stored in a secure location, alerting security teams to any unauthorized modifications. Second, employ content security policies (CSP) that restrict inline script execution and limit the sources from which scripts may be loaded. By whitelisting only trusted domains, organizations can reduce the impact of compromised external libraries.
Third, integrate real‑time threat intelligence feeds that flag known malicious domains or URLs. If a visitor’s browser attempts to fetch resources from a blacklisted address, the CSP can block the request before the exploit kit is delivered. Fourth, maintain up‑to‑date browser extensions and operating systems, as the iOS exploit kits likely rely on unpatched vulnerabilities. Regular patching reduces the attack surface for mobile clients.
Finally, consider using subresource integrity (SRI) attributes when including external scripts. SRI allows a website to specify a cryptographic hash of the expected script content; browsers will ignore scripts whose hash does not match, effectively neutralizing tampered code. Deploying SRI for Optimizely and any other third‑party libraries provides an additional safety net.
Grivyonx Expert Analysis
The incident illustrates a growing trend where attackers target the software supply chain rather than individual endpoints. By compromising a widely used script library, the threat actor achieved massive distribution with minimal effort. Organizations must treat third‑party code with the same scrutiny they apply to their own applications, employing integrity verification and strict delivery policies. Continuous monitoring of script sources and rapid response to integrity failures are essential to mitigate future supply‑chain compromises.
Conclusion
As the reliance on external web services continues to expand, the security of those services becomes a critical factor in overall enterprise risk management. The Optimizely script hijack serves as a reminder that even well‑established platforms can be leveraged for malicious purposes, requiring vigilant oversight and robust defensive controls. Grivyonx's AI‑driven security automation and DevSecOps integration can help organizations detect anomalous script behavior and enforce strict supply‑chain policies at scale.
- #optimizely
- #supply chain attack
- #card skimmer
- #iOS exploit
- #cybersecurity
- #web script security



