On Sunday 16 November, someone opened the BBC website, or Zoom, or IKEA. The page looked normal. Somewhere in the background, a small file loaded, the way it does on thousands of sites every day.
That day, the file had been changed.
The file belonged to Optimizely, a platform companies use to test different versions of their web pages. In its incident report, Optimizely says an attacker abused a flaw in the account signup flow of its Web Experimentation product, posed as existing users and added malicious JavaScript to customer projects.
How far did one changed file travel?
Security researcher Scott Helme of Report URI checked 1,611 Optimizely snippets and found 188 infected, belonging to 178 organisations, with the real number likely higher. His list includes Zoom, the BBC, CNN, Salesforce, IKEA, HSBC and Equifax.
Being on that list means the snippet carried the code, not that a given site's customers lost data.
According to Report URI, the script swapped cryptocurrency wallet addresses, skimmed cards typed into a site's own forms, took cookies and screenshots, and sent exploit kits to iPhones and iPads. Palo Alto Networks' Unit 42 named the campaign OPTIMJACK.
The code was served from Optimizely's own address, under Optimizely's own certificate. None of the 178 organisations had to be breached. As TechTarget put it, the malware reached visitors "without directly breaching the companies themselves."
Optimizely says it closed the flaw that afternoon and removed the code from every project by 22:24 UTC. SOCRadar counts nearly 19 hours of exposure and about $7,150 received by the attacker's wallets. Nobody has counted the skimmed cards.
Why does one supplier reach so many sites?
Think about what each of those websites was trusting. It was a supplier's file, loaded on every page view, with the power to change what visitors saw, and the sites' own servers had nothing to do with it.
One account at one supplier was enough to reach 178 organisations at once.
The same shape runs through a lot of this week's news. One place holds something complete, a script, a mailbox, a folder of client files, and everyone who depends on it has the same bad day.
What is Untrace?
Untrace would not have stopped this attack. It does not protect web pages or the scripts they load, and that is a different layer from the one Optimizely runs.
What Untrace changes is the same dependency, for stored files. Untrace is file storage designed so that no single storage location ever holds enough to rebuild a file.
Each file is encrypted in the browser and divided into six shards stored in six locations: Dubai, Zurich, Doha, South Carolina, the EU and the US. Any three shards rebuild the file.
What problems does Untrace solve?
One location is not the whole file. Anyone who gets into a single location finds encrypted shards and no document.
One location going down does not lock you out. With any three of six shards enough, a file still opens when one location is offline.
The storage cannot read what it holds. Files are encrypted before they leave the browser, and opening one takes the user's passkey.
On 16 November, a single supplier was trusted by 178 organisations. For your files, Untrace is built so that no single location carries that much trust.
Originally published at untrace.network.

Top comments (0)