Optimizely has disclosed a separate security incident involving its Configured Commerce platform after an unauthorized third party accessed a legacy build and deployment server that the company was preparing to retire.
The company said the access occurred between November 10 and 12, 2026, and that it detected the activity on November 12. In an update published November 21, Optimizely said it removed an injected script from two sites only and permanently shut down the compromised server. The company said it had secured its environment and brought in independent third-party experts to assist with an ongoing forensic investigation.
Optimizely has not named the two sites, described the script’s behavior or said whether customer data was accessed or taken. Its public statement does not identify the affected customers or explain how the intruder gained access to the legacy server.
The company said the incident is unrelated to the Web Experimentation security incident disclosed earlier in November. That separate event involved an attacker exploiting a flaw in the product’s account signup flow to impersonate users on targeted customer accounts and insert malicious JavaScript into their projects. Abijita previously reported on the Web Experimentation incident after researchers found infected Optimizely snippets across 178 organizations.
The new disclosure adds to a series of software supply-chain incidents in which malicious code was introduced through a vendor’s infrastructure rather than directly into each customer site. A previous attack on the WordPress plugins OptinMonster, TrustPulse and PushEngage also used a vendor’s content delivery network to distribute malicious JavaScript, as Abijita reported.
Optimizely’s service status page continues to list the Configured Commerce incident as unresolved, while its regional Configured Commerce components are marked operational. The company has not provided a timetable for completing the investigation or said whether additional sites were affected.
Optimizely Discloses Separate Configured Commerce Breach



