AI Weekly Malaysia

Back to items Summaries

Optimizely compromised, served malware on Zoom, GitLab

ID
47311
Status
summarized
Published
17 Nov 2026, 7:00 AM
Fetched
17 Nov 2026, 3:19 PM
Provider
Hacker News
Category
dev-community
Original URL
https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
Source URL
https://hnrss.org/best

Summary

Score
8.0
Created
17 Nov 2026, 3:19 PM
Tags
Audience
developersvibe_coderssaas_founders

What happened

On 16 November 2026, attackers wrote their own code into the Project JavaScript field of Optimizely Web customer projects, so malicious JS was served from cdn.optimizely.com to visitors of 178 organisations including Zoom, GitLab, Salesforce, BBC, CNN, IKEA, HSBC, Equifax, Ledger and Peacock. The payload swapped crypto wallet addresses, skimmed card data, stole cookies and screenshots, and on iOS delivered the Coruna and DarkSword exploit kits, with verified crypto theft already on-chain. Three loader variants were seen — a plain script tag to https://1688360.cc/track.js and the same URL base64-encoded and decoded via atob() — and by 21:52 UTC the code was down to 1 of 188 infected snippets, from 169 at 20:56 UTC.

Why it matters

The whole attack worked because the file stayed on cdn.optimizely.com with a valid certificate, so a CSP that allowlists Optimizely's CDN would not have blocked it — the payload arrived from a host you already trust. If you run Optimizely Web, go read the Project JavaScript field in each project dashboard directly rather than assuming your own code is clean, and treat integrity monitoring plus hash-pinned CSP as the control that would actually have caught this. Searching logs for '1688360.cc' misses the base64+atob variant, so detection needs to flag any newly injected script loader, not a known-bad domain.

Discussion angle

Your CSP allowlist trusted cdn.optimizely.com and that was the delivery vector — what is your actual baseline for detecting a change inside a third-party script you don't control, and would you have caught the base64 variant?

Top