Keeper Security has been recognized in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management (PAM), the Gartner evaluation of vendors in the PAM market. Gartner
On November 16, 2026, security researchers disclosed a cyber attack involving Optimizely, a platform businesses use to test and personalize their websites. Report URI identified malicious JavaScript in website scripts associated with 178 organizations, including Zoom, the BBC, CNN, Salesforce, GitLab, IKEA and HSBC.
Optimizely confirmed that an attacker exploited a vulnerability to add malicious code to customer projects. The company says it has fixed the vulnerability and removed the injected code. As of November 17, the full impact on website visitors remains unclear.
What you should know about the Optimizely cyber attack
- Report URI found 188 infected Optimizely scripts associated with 178 organizations.
- The malicious code could replace cryptocurrency wallet addresses, skim payment card details, collect browser-accessible cookies and capture webpage screenshots.
- Some payloads targeted iPhones and iPads through the Coruna and DarkSword exploit kits.
- Optimizely says it fixed the vulnerability, removed the injected code and took steps to secure affected accounts.
- Salesforce confirmed unauthorized changes to Optimizely scripts on certain websites and said it was verifying that those scripts were disabled.
- The number of affected visitors and the extent of successful data theft or device compromise remain unclear. The findings do not establish that every organization’s internal systems or every visitor’s device was compromised.
The impact of the Optimizely cyber attack
The attack exposed a risk in the software that organizations embed in their websites. A vendor’s script can become a delivery mechanism for malicious code, reaching visitors through a website they already trust.
BleepingComputer’s analysis confirmed code designed to substitute attackers’ cryptocurrency addresses and capture payment information. It also identified functionality to collect cookies and screenshots. However, the number of affected visitors and the extent of successful data theft or device compromise have not been established.
For visitors, the potential consequences include fraudulent card transactions, diverted cryptocurrency transfers and exposure of browser-accessible information.
What to do if you visited an affected website
If you visited an affected website during the attack, take these steps:
- Monitor payment accounts: If you entered card details, review transactions and report suspicious charges to your card issuer.
- Check cryptocurrency transfers: Verify that any transfers went to the intended wallet addresses.
- Update your devices: Install the latest available operating system updates on your iPhone or iPad.
- Review account activity: Check for unfamiliar logins or account changes. If you notice suspicious activity, follow the service’s account recovery guidance.
You can check Report URI’s list of affected websites to see if you visited one. Other sites may also have been affected.
What organizations can learn from the Optimizely cyber attack
The incident highlights the need to assess both the code third parties deliver and the access that lets changes reach production websites.
Treat third-party scripts as part of your attack surface
Website testing, analytics and marketing tools deserve security review alongside other production software. OWASP’s third-party JavaScript guidance identifies risks including unauthorized code execution and disclosure of sensitive information.
Maintain an inventory of third-party scripts, document their business owners and remove unnecessary integrations. Monitor changes to scripts and their behavior. Where compatible, use Subresource Integrity to check approved script versions and a Content Security Policy to restrict script execution and outbound connections. These controls require careful configuration, particularly when vendor scripts change frequently.
Limit access to website publishing tools
Review who can edit experiments, publish tags and change scripts across your website platforms. Give employees and vendors only the permissions their roles require, remove unused accounts and enforce Multi-Factor Authentication (MFA) wherever supported.
Apply the same scrutiny to integration tokens and other machine credentials. Limit their permissions and revoke unused access. These measures improve security, but reports link this attack to a vulnerability and do not confirm that stolen passwords were involved.
Prepare to contain a compromised integration
Incident response plans should explain how to disable a third-party integration, preserve evidence and identify affected pages. Assign responsibility for coordinating with the vendor and notifying customers.
For organizations using Optimizely, Report URI recommends reviewing project code and account access, rotating credentials and treating session tokens or secrets in cookies accessible to JavaScript as exposed. Removing malicious code should be followed by an assessment of what it could have accessed.
Strengthen access security across your organization
The Optimizely cyber attack shows why organizations need visibility into third-party code and control over the accounts that manage critical systems. Script monitoring, secure configurations and access governance each address a different part of that risk.
KeeperPAM® helps organizations protect credentials in a zero-knowledge vault, enforce Role-Based Access Controls (RBAC) and manage privileged sessions with auditing and recording. These capabilities strengthen access security as part of a broader defense that includes application security and third-party risk management.
Request a KeeperPAM demo to learn how Keeper can help secure access to your organization’s critical resources.