Optimizely compromise injected malicious scripts into Salesforce sites (opens in a new tab)
You will learn how a third-party script vendor was used to inject malicious JavaScript into 178 sites, including several Salesforce domains, and what to audit on your own Salesforce-powered sites in response.
- Attackers add code to Project JavaScript field
- Optimizely CDN passes code to site visitors
- Visitors' browsers run the injected script
- Script swaps crypto addresses, takes card data
Malicious JavaScript was injected into Optimizely’s Web experimentation platform and served to visitors of 178 organizations on November 16, including Salesforce. The code was designed to swap cryptocurrency addresses for the attacker’s own, collect payment card information, and target iOS devices with additional exploit chains. Salesforce says its own systems were not compromised, but it disabled Optimizely scripts across preview and production instances as a precaution while it investigates.
The attackers reportedly placed code in a “Project JavaScript” field in customer Optimizely accounts, which the vendor’s content delivery network then passed on to visitors. It is not yet clear how the attackers gained write access to those accounts. Optimizely has said it fixed the vulnerability, removed the injected code from affected projects, and added security measures. Equifax has stopped using Optimizely altogether.
The affected Salesforce domains named in the research were evergage.com, exacttarget.com, pardot.com and salesforce-scrt.com, along with four others not named. The article treats the incident as a lesson in supply chain risk: a secure platform can still be brought down by a vendor script running on its pages. It suggests auditing the third-party scripts on Experience Cloud and Commerce Cloud storefronts, removing any that are no longer used, and investigating any that nobody in the organization can account for.
For end users, the article recommends updating iOS devices to 18.7.3 or later, or to iOS 26.3 or later, depending on what the device supports.
Read the original at Salesforce Ben (opens in a new tab)