Optimizely script attack prompts a storefront audit
A malicious change to trusted third-party JavaScript reached visitors to 178 organisations through Optimizely Web on 16 November, according to Report URI’s investigation. For commerce operators, the…
A malicious change to trusted third-party JavaScript reached visitors to 178 organisations through Optimizely Web on 16 November, according to Report URI’s investigation. For commerce operators, the incident is a reason to review the scripts actually loaded by the storefront and who can change them.
What the researchers observed
Report URI found 188 infected snippets among 1,611 checked. The injected code sat in customer projects’ Project JavaScript and was delivered by the legitimate Optimizely CDN. The researchers reported cryptocurrency-address replacement, card skimming and other theft. Their report distinguishes card details entered in a site’s own fields from hosted payment iframes, which this skimmer could not read.
The researchers’ account does not establish that Shopify’s platform was compromised. Nor does an affected domain prove that every visitor lost information. Exposure depends on the code loaded, the page context and what a visitor did.
Check dependencies and access
Our recommendation is to inventory experimentation, analytics and other scripts on the pages customers actually use. Compare that inventory with the services the business still intends to run. Assign an owner to each dependency and check which people, tokens and integrations can modify it.
If your business uses Optimizely Web, have the responsible team review the project code and preserved logs against the investigator’s indicators. Escalate evidence of exposure through your incident-response process; do not treat removing one visible script as proof that the investigation is complete.
Review browser security policy with the developer responsible for the site. A policy that only reports violations is different from one that blocks them. Test changes against necessary storefront functions before deployment, and keep the distinction between storefront code and isolated payment components explicit.
More from News
See all →