Between outages and cyber security incidents, the web is an interesting place at the moment, with massive websites unwittingly caught in another incident this week.
Nearly 200 sites have been caught in an unusual hack that has seen a piece of code used to change and optimise webpages for business, turning that optimisation code into something far more insidious: a way to steal.
The hack was picked up by a security researcher working at a web monitoring service, Scott Helme, who found what would normally have been a small part of websites become a much bigger deal.
The code comes from a platform called “Optimizely”, and while this script is normally a mechanism for large companies to change a site and test different approaches for different users, the script was broken into and manipulated by someone from outside the company.
Instead of simply changing elements on the page, the script was made into a hacker’s toolkit, finding ways to skim credit cards from forms, looking for crypto wallet addresses being entered by users and replacing them with that of the attacker, and essentially stealing money.
The hack appears largely motivated by the theft of cryptocurrency, and appears to have affected at least 178 organisations and their sites, including that of IKEA internationally and Vodafone in Australia, to name a few. By the time this was published, Optimizely says the code had been cleaned up across the affected sites, which may provide some peace of mind.
But the question remains: how did this happen, and could anyone have blocked it before it happened?
The “how” will come down to Optimizely which ran the script all of these sites shared in common, which released this statement to its status page:
“Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We’ve fixed the vulnerability and removed the injected code from affected projects. We’ve also taken steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered.”
Could anything have blocked it
That brings everything to the prevention, and the question of whether anything could have stopped the hacked scripts from running. The businesses running the sites may have other avenues to consider, but as consumers, we’re all largely none-the-wiser.
Curiously, only a few things might have stopped the script from running, and it might signal why it’s just so important to keep your phones updated.
Some browsers might have skipped it entirely. Privacy-focused web browsers could have theoretically blocked the script from running, as different web browsers handle scripts differently for privacy. That might have had an impact, but we just don’t know (yet).
The hacked and malicious code in question relied on specific flaws found in older iPhone and iPad operating systems, something Apple patched in iOS 18.7.3 and iOS 26.3. We’re now technically on iOS 27, and an updated iPhone and iPad might have been protected from part of the attack, but might not have stopped other aspects, such as the capture of card details.
Ultimately, if you’re at all concerned, log into your bank and find out whether anything is missing, or alternatively into any wallets you might be concerned about. If you’ve made any transfers, particularly at sites where the script was found to run, it might be an idea to keep an eye on things.
The problem is that this bit of code was never supposed to be modified in this way, and there would have simply been no way for a user to know or realise it’s happening.
Between the sheer regularity with which breaches and hacks are occurring lately, it’s all too easy to consider hacks the new norm. Money is clearly the motivation, and it means we’re all at risk, and may need to keep everything updated just to ensure at least one line of defence is handled.