Salesforce Investigates Optimizely Script Changes After November 16 Attack
Salesforce said it is investigating unauthorized modifications to scripts provided by Optimizely after an attacker exploited a vulnerability in the third-party experimentation platform on November 16, 2026. The attacker added malicious JavaScript to customer projects, according to the available incident description.
The disclosure points to a risk inherent in websites that rely on externally supplied code: a change at a vendor can affect scripts used within customer projects. The information provided does not specify which projects were affected, what the malicious code did, how long it was present or whether any customer data was accessed. Salesforce’s investigation is ongoing, and no further findings are available in the stated details.
What is known about the incident
- The incident involved Optimizely, identified as a third-party experimentation platform.
- An attacker exploited a vulnerability in Optimizely on November 16, 2026.
- The attacker added malicious JavaScript to customer projects.
- Salesforce is investigating unauthorized modifications to scripts supplied by Optimizely.
Those details establish the reported mechanism but do not answer key questions marketers and technology teams may have. The available account does not name impacted customers or quantify the scope of the activity. It also does not explain whether the issue affected a particular Optimizely product or version, when the vulnerability was discovered or addressed, or what steps customers should take. Those points should not be inferred from the fact that an investigation is underway.
For teams using experimentation and personalization tools, the episode is a reminder to account for third-party scripts in website security and incident-response planning. Such scripts can be integrated into customer projects to support testing or related functions, so organizations need a clear understanding of which vendors supply code and who is responsible for reviewing changes. This is general operational context, not a claim about the configuration of any affected project.
Questions for marketing technology teams
While further findings are pending, teams can use the report to review their own governance processes. That includes keeping an inventory of externally supplied scripts, identifying internal owners for vendor integrations, and knowing how to assess or pause a dependency if a security concern arises. Organizations should rely on verified guidance from the relevant providers rather than assume that a particular response or remediation has occurred.
Marketing leaders may also need to coordinate with security, engineering and procurement colleagues when assessing third-party platforms. A shared process can help teams establish who evaluates vendor notices, how changes to site code are monitored, and how business stakeholders are informed during an investigation. The available information does not indicate what measures Salesforce or Optimizely have taken beyond Salesforce’s stated investigation.
The incident underscores the importance of treating experimentation-platform integrations as part of the broader website supply chain. Its eventual scope and customer impact remain unclear based on the details currently provided. Until additional verified information is available, the confirmed facts are limited to the November 16 attack, the addition of malicious JavaScript to customer projects and Salesforce’s investigation of unauthorized changes to Optimizely-provided scripts.
