Optimizely posted a security notice on Nov. 17 saying an unauthorized party had exploited a vulnerability in its Experimentation product and used it to add malicious JavaScript to some customer projects. For marketing teams that use the product, the affected code sat in a place they edit.
What happened
Optimizely’s status page says the company fixed the vulnerability, removed the injected code from affected projects, secured affected user accounts and added protections against unauthorized code being delivered. It does not say how many customers were affected or how the attacker gained access. Security vendor Report URI, which sells script monitoring, published its own count: malicious code served to visitors of 178 organisations on Nov. 16, found in 188 of the 1,611 Optimizely Web snippets it checked. It says the code was written into the Project JavaScript field, custom code a customer adds in the dashboard that runs on every page, and that the rest of each snippet was untouched.
Why it matters to marketing
A testing or personalization snippet loads on every page, including checkout, from a host the site already trusts. Report URI says the payload swapped cryptocurrency wallet addresses, skimmed card details typed into a site’s own forms and, on iPhones and iPads, tried to deliver iOS exploit kits. Optimizely’s notice does not describe the payload.
What to check this week
In our reading, access to a script field belongs on the marketing operations checklist next to analytics tracking and experiment programmes. List who and what can write to it, including API tokens. Report URI advises opening every Project JavaScript and each experiment’s custom code, and rotating credentials. Ask your security team for a script policy that lists only the hosts the page needs.
Source: Optimizely status page, Web Experimentation Security Incident