Optimizely Supply Chain Attack: What It Means for NIS2 and DORA Third-Party Risk
In late 2025, a supply chain attack on Optimizely, a widely used digital experience platform, sent shockwaves through the cybersecurity community. Attackers exploited a vulnerability in Optimizely's Web Experimentation service to inject malicious JavaScript into customer websites, affecting at least 178 organizations, including CNN, the BBC, Zoom, and Salesforce. The injected code was designed to steal payment card data, replace cryptocurrency addresses, and deliver iOS exploit kits. This incident underscores the growing threat of third-party script vulnerabilities and the critical need for robust vendor risk management—especially for EU organizations bound by NIS2 and DORA.
How the Optimizely Supply Chain Attack Worked
The attack exploited a flaw in Optimizely's Experimentation account signup flow, allowing attackers to inject malicious JavaScript into customer projects. This script then loaded a payload from a remote server, enabling a range of malicious activities:
- Payment card skimming: Capturing sensitive payment information entered on affected sites.
- Cryptocurrency address replacement: Swapping wallet addresses to redirect transactions to attacker-controlled accounts.
- iOS exploit kits: Delivering exploits (reported as Coruna and DarkSword) to compromise visitors' devices.
- Data exfiltration: Collecting cookies, URLs, and screenshots to gather further intelligence.
Security researcher Scott Helme identified 188 infected scripts across 178 organizations. Optimizely responded swiftly by blocking the vulnerable path, removing the injected code, revoking tokens, and resetting access for affected accounts. Salesforce, one of the affected customers, disabled Optimizely scripts across its preview and production instances as a precaution. While the cleanup reduced the number of infected scripts to one as of November 16, the incident left many wondering about the security of third-party scripts.
The Risks of Third-Party Scripts
Third-party scripts are ubiquitous in modern web development. They power analytics, advertising, experimentation, and customer support. However, they also introduce significant security and compliance risks:
- Expanded attack surface: Each third-party script is a potential entry point for attackers. A vulnerability in any one of them can compromise the entire website.
- Lack of visibility: Many organizations lack full visibility into the scripts running on their sites, making it difficult to detect malicious changes.
- Regulatory exposure: Under regulations like NIS2 and DORA, organizations are accountable for the security of their supply chain, including third-party scripts. A breach can lead to hefty fines and reputational damage.
The Optimizely incident is a stark reminder that even trusted vendors can become vectors for attack. As Scott Helme noted, "the malicious script also collected cookies, URLs, and screenshots," highlighting the data theft potential.
Compliance Implications Under NIS2 and DORA
For EU organizations, the Optimizely attack raises serious compliance questions. Both NIS2 (Directive (EU) 2022/2555) and DORA (Regulation (EU) 2022/2554) impose stringent requirements on third-party risk management.
NIS2: Supply Chain Security
NIS2, which must be transposed into national law by 17 October 2024, applies to essential and important entities across 18 sectors. It explicitly requires organizations to address supply chain security, including the security of third-party service providers. Key obligations include:
- Conducting risk assessments of suppliers and service providers.
- Implementing incident reporting (24-hour early warning, 72-hour notification).
- Ensuring management accountability for cybersecurity.
Penalties for non-compliance can reach up to €10 million or 2% of global turnover for essential entities.
DORA: Third-Party ICT Risk Management
DORA, applicable from 17 January 2025, focuses on digital operational resilience for financial entities. It mandates robust third-party ICT risk management, including:
- Due diligence and contractual arrangements with ICT providers.
- Regular testing of digital operational resilience, including threat-led penetration testing.
- Incident reporting and information sharing.
Financial entities must ensure that their third-party providers, including those offering web experimentation tools, meet DORA's stringent requirements.
Actionable Steps for Vendor Risk Management and Script Monitoring
To mitigate the risks exposed by the Optimizely attack, organizations should adopt a proactive approach to vendor risk management and script monitoring.
1. Inventory and Classify Third-Party Scripts
Begin by cataloging all third-party scripts running on your websites. Classify them by criticality and data access. Tools like OneTrust can help with consent management, ensuring that scripts are only loaded with proper user consent, which is also a GDPR requirement.
2. Implement Continuous Script Monitoring
Deploy solutions that continuously monitor third-party scripts for unauthorized changes. Look for tools that can detect anomalies, such as new domains or unexpected code modifications. CrowdStrike offers threat detection capabilities that can be extended to web scripts.
3. Enforce Vendor Due Diligence
Before onboarding a vendor, conduct thorough due diligence. Assess their security posture, incident response plans, and compliance with standards like ISO 27001. This is a core requirement under NIS2 and DORA. For guidance on vendor assessments, see our EU AI Act compliance roadmap (though focused on AI, the vendor risk principles apply broadly).
4. Develop a Robust Incident Response Plan
Ensure your incident response plan covers supply chain attacks. This includes procedures for quickly disabling compromised scripts, notifying affected parties, and meeting regulatory reporting deadlines. Under NIS2, early warning must be issued within 24 hours of becoming aware of an incident.
5. Leverage Continuous Compliance Monitoring
Manual oversight is no longer sufficient. Automated continuous compliance monitoring platforms can help. For instance, AIGovHub's CCM module can monitor third-party scripts and alert you to anomalies, while also tracking compliance with NIS2 and DORA requirements. It integrates with ERP systems and provides real-time visibility into your supply chain risk.
How AIGovHub's CCM Module Can Help
AIGovHub's Continuous Compliance Monitoring (CCM) module is designed to address exactly these challenges. It provides:
- Real-time script monitoring: Detects unauthorized changes to third-party scripts and alerts you immediately.
- Vendor risk scoring: Continuously assesses vendors against NIS2 and DORA criteria.
- Automated evidence collection: Gathers and stores evidence of compliance for audits.
- Integration with ERP and security tools: Connects with your existing stack to provide a holistic view.
By using AIGovHub CCM, organizations can ensure they meet the stringent third-party risk management requirements of NIS2 and DORA, while also protecting their digital assets from supply chain attacks.
Key Takeaways
- The Optimizely supply chain attack exploited a vulnerability in a third-party service to inject malicious JavaScript into customer websites, affecting 178 organizations.
- Third-party scripts pose significant security and compliance risks, including data theft and regulatory penalties.
- NIS2 and DORA mandate robust third-party risk management, including supply chain security and incident reporting.
- Organizations must inventory scripts, implement continuous monitoring, conduct vendor due diligence, and prepare incident response plans.
- Tools like AIGovHub CCM, OneTrust, and CrowdStrike can help automate and streamline these efforts.
Assess Your Supply Chain Risk Today
Don't wait for the next supply chain attack to expose your organization. Take proactive steps to assess and mitigate your third-party risk. AIGovHub offers a suite of tools, including the Vendor Due Diligence Questionnaire Generator and the Incident Assessment Tool, to help you evaluate vendors and respond to incidents effectively. Contact us to learn how AIGovHub can help you achieve continuous compliance and resilience.
This content is for informational purposes only and does not constitute legal advice.