Hundreds of websites deliver potent malware cocktail to unsuspecting visitors
- ID
- 47585
- Status
- summarized
- Published
- 18 Nov 2026, 6:32 AM
- Fetched
- 18 Nov 2026, 7:02 AM
- Provider
- Ars Technica
- Category
- technology
- Original URL
- https://arstechnica.com/security/2026/11/malicious-code-delivered-through-optimizely-hits-visitors-to-hundreds-of-sites/
- Source URL
- https://feeds.arstechnica.com/arstechnica/index
Summary
- Score
- 5.0
- Created
- 18 Nov 2026, 7:02 AM
- Tags
- Audience
- developersvibe_codersfounders
What happened
Ars Technica reports that malicious code delivered through Optimizely — a third-party script many sites embed for A/B testing and personalization — reached visitors on hundreds of websites, pushing what the piece calls a "malware cocktail" that includes cryptocurrency-theft payloads and iOS exploits. The available text is truncated after the opening section, so the specific compromised domain count, the timeline of the Optimizely compromise, the named malware families, and any vendor response are not present in what we have. The only community signal given is a 6-comment thread on the story.
Why it matters
The one decision-relevant fact here is the delivery vector, not the malware: the payload arrived through a third-party script tag rather than the sites' own code, so anyone whose pages load Optimizely or similar tag-manager/analytics snippets inherited the exposure without changing a line of their own repo. Before the meet, pull your list of third-party scripts and check which ones you cannot remove or self-host — that list is the actual blast radius. Because the article text is cut off, we cannot say from this source which Optimizely customers or regions were hit, when it started, or whether it is resolved, so don't plan remediation specifics off this item alone.
Discussion angle
Ask everyone to name the third-party scripts their production site loads that they could not audit this week — then debate whether a strict CSP plus self-hosting is realistic for a small team, or whether most of us are just accepting script-tag risk as a cost of doing business.