Thumbnail of the Search Engine Journal article on the Optimizely signup flaw

Optimizely Malware Incident, A Checklist for Teams Running A/B Tests

A malicious script reached visitors through a flaw in Optimizely's signup flow, and the fixes sit inside your own account and security…

Production

1 min read

What Should Teams Check After the Optimizely Breach?

Search Engine Journal's Matt G. Southern reports that an attacker used a flaw in the Optimizely signup flow to insert malicious JavaScript into customer projects, and that visitors to affected sites received it for a period on November 16. The code could swap crypto wallet addresses, watch forms for card details and load exploit kits aimed at older iOS devices. The article draws on Scott Helme's analysis of 178 organizations' snippets and explains which parts of the attack a trusted domain could not stop.

For brand builders, the lesson goes beyond one vendor. Third-party scripts run with the same reach as your own code, so a project setting inside a testing tool can become a checkout risk. The piece sets out practical steps: review custom project code, audit who can edit it, rotate credentials and check your Content Security Policy. Anyone who manages a website, a tag stack or an experimentation platform should read it this week.

Read Full Story

Source: searchenginejournal.com · Originally published

Published: Updated: