Nobody Hacked CNN. The Attacker Changed One JavaScript File.
Автор: Marcos Santos
Загружено: 2026-11-17
Просмотров: 71
Описание:
On Monday, November 16, 2026, visitors of CNN, the BBC, Zoom and 175 other organizations were served malicious JavaScript. None of those companies was breached. The attacker changed one file at Optimizely, an A/B testing vendor whose script was already running on all of those sites.
In this video I go through what happened hour by hour, rebuild the attack in a small lab (everything fake, running on my machine), show how a Content Security Policy blocks it, and leave a checklist for your own site.
Chapters
0:00 What happened on Monday
0:26 What we'll cover
0:48 What Optimizely does on a page
1:39 The timeline, hour by hour
2:56 What the code did in the browser
3:45 Lab: the attack
4:41 Lab: the defense
5:16 Who was protected (the numbers)
6:10 What we still don't know
6:51 My checklist
7:54 The lesson
The checklist
1. Inventory every third-party script on your site
2. Ask if each one needs to run on every page (checkout and login first)
3. Add a Content Security Policy, starting in report-only mode
4. Use a hosted payment frame for card data
5. If you use Optimizely: review Project JavaScript and experiment code, rotate access tokens
If you only visited one of the affected sites: update iOS to 18.7.3 or later (or 26.3 or later) and watch your card statement.
Sources
Report URI (Scott Helme): https://blog.report-uri.com/worlds-la...
The Register: https://www.theregister.com/cyber-cri...
Socket: https://socket.dev/blog/optimizely-su...
Malwarebytes: https://www.malwarebytes.com/blog/new...
Notes
Almost every number comes from Report URI's write-up. They sell a product that detects this kind of attack.
The lab uses fake names and a harmless payload that only changes one text on the page.
The point about Subresource Integrity is my own view.
#cybersecurity #appsec #supplychainattack
Повторяем попытку...
Доступные форматы для скачивания:
Скачать видео
-
Информация по загрузке: