In this case optimizely should have had better systems to spot a release like this (internal cool downs, check and balances, phased rolouts, automatic security checks). And sites that have massive user bases (cnn, bbc, etc..) have zero excuse to not have the same.
I would go so far as to say those sites should not be serving from vendors but should be vendoring their own scripts that they also are passing through security audits and serving them selves with cool downs.
How do these companies not have better dedication to protecting their users is beyond me.
It doesn't cost them anything but a "whoops" post when they fuck up, so the incentive is misaligned (as you noted under repercussions).
The cost is externalised onto everyone else not them so it's not going to change.
Who cares? Next week you forget about this and move on
I would go so far as to say those sites should not be serving from vendors but should be vendoring their own scripts that they also are passing through security audits and serving them selves with cool downs.
How do these companies not have better dedication to protecting their users is beyond me.
Anyone knows what this might be? Can you jailbreak from safari on those versions?
[edit] From the other link, it seems to be Coruna and DarkSword exploits
Currently says "Partial Outage Affecting Recommendations Tracking and Reporting"
> Your origin can be clean while your visitors are robbed — the compromise sits in the tag layer.
“yeah load this JS m, but it can’t load / random other JS referencing sketchy places”
Never load third-party JavaScript on your site. Zero exceptions.
Feels nice knowing several years ago I worked on forcing CSP (including removing unsafe-eval) on some customers for a site builder product, as they have to manually whitelist domains which limits the impact of these sorts of attacks...
This writeup https://blog.report-uri.com/worlds-largest-brands-infected-w... has a section on how CSP helped (or didn't) in this attack.
As an aside - I'm rabidly against "analytics" companies that come in and suggest that the right "getting started" choice is to drop untrusted JS they own (and can update at any time) onto your site.
It's "easy", but it completely breaks your security model.
If I were a lawyer... I'd be taking a serious look at putting optimizely into the meat grinder for recommending 'unsafe-eval' as a script source... it literally has "unsafe" in the fucking name for a reason. This alone should end the company. It won't, because this space is absolutely FILLED with scummy behavior, but it should.
---
A strict CSP is one of the most meaningful ways you have right now as a web developer to reduce attack surface. People should take advantage of it.
There's a reason browser vendors now force basically all extensions into a strict CSP by default... https://developer.chrome.com/docs/extensions/reference/manif... They won't even let you manually relax it anymore.
Common examples like analytics tools happily change their script bundles whenever they feel like it without just tagging a new version and letting you upgrade.
I wish SRI could be used more,
https://x.com/tehlike/status/1432082161125888003 https://x.com/tehlike/status/1467033965215109122
Only followers this account has approved can see its posts.
Somehow this sentence immediately flags this article as AI slop.
What is interesting is that the write access wasn't just for a single customer, but hundreds. So either tenancy isn't strong enough, or the level of access involved in the compromise was pretty severe.
I hope folks are re-evaluating that now.
We got 10MB of javascript (maybe 10 years ago...) because engineering needs to build one frontend with multi browser and multi screen support so they picked an off-the-shelf do-everything framework like Amber or Angular, or a react/redux build with 300 nested dependencies.
That’s why it needs to become criminal for a website to serve malware, including through third party channels like ad networks and analytics services. Serving shit websites is no different than knowingly, or negligently, dumping toxic waste and should be treated the same.
There should be standards that people have to live up to if they are going to provide a product, even for free, to others.
Open source is already expensive from a time standpoint, you wanna make it expensive from a monetary standpoint too?
We should also enforce antitrust laws.
I never really understood this idiom, because how can a PHB engineering manager (for example) be required to not understand their team's technology in order to retain their job? Surely if that manager knows their team's work inside out then they would be a more effective manager - which is good for everyone?
If I squint-my-brain, I can see how (for example) that anyone who works full-time as an SEO "consultant" in the year 2026 would only be if they actually believed that SEO tricks actually worked, which requires them to not understand how modern search-engines' spiders actually work (because it's my belief that "SEO" has been either nonsense bollocks - or a complete grift - since the mid-2010s). Am I close?
In this case, it's the dangers of the tracking and advertising frameworks being used for hostile purposes.
--Upton Sinclair
I know we really like mass incarceration in America. But maybe start with civil liability and a private right to enforcement?