Configuration: Optimizely Snippet Serves Malware¶
Identifier:
optimizely_snippet_compromise
Scanner Support¶
| GraphQL Scanner | REST Scanner | WebApp Scanner | ASM Scanner | Automated Pentest |
|---|---|---|---|---|
Description¶
On 16 November 2026, attackers injected a loader into the Project JavaScript of at least 188 Optimizely Web projects, so the legitimate snippet served by Optimizely loaded a crypto address swapper, a card skimmer, a cookie and screenshot stealer, and iOS exploit kits on the customers' pages.
How we test: We read the page, follow the Optimizely snippet it references (cdn.optimizely.com, cdn-pci.optimizely.com, or a first-party /js/<project>.js), and match the published indicators in the snippet: the attacker's domains in plain text or base64, the payload's globals and loader channel code, and the attacker's wallets. Only snippets referenced in the page HTML are checked; a snippet added at runtime by a tag manager isn't seen. The page and the snippet are fetched without the scan's credentials or custom headers, so a page that needs a header to get past a WAF isn't checked.
Reference:
- https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
- https://www.stepsecurity.io/blog/optimjack-optimizely-hosted-scripts-crypto-clipper-card-skimmer
- https://status.optimizely.com/incidents/ftw0fh9wx43z
Configuration¶
Example¶
Example configuration:
Reference¶
skip¶
Type: boolean
Skip the test if true.