Optimizely Supply Chain Breach Exposes 178 Websites and Targets iOS Users

microwire.news - Add as a preferred source on Google

Like most people who work in tech, I run secure DNS, ad blockers, avoid unknown links, and check URLs before typing in a password. But the recent Optimizely breach is a sobering reminder that even if you do everything right on the surface, you’re not safe if the websites you trust are silently serving you malicious code.

Earlier this week, security researchers uncovered a massive supply chain attack that compromised 188 Optimizely scripts among 178 major organizations. Instead of hacking each company individually, the attackers leveraged a weakness in Optimizely’s experimentation platform and slipped malicious JavaScript into scripts used for normal website testing. Because millions of people visit these sites daily, researchers estimate the poisoned code loaded during roughly 34 million page visits on November 16, 2026.

Household Brands and Entities Caught in the Crossfire

What makes this incident so unsettling is the sheer caliber of the companies affected. Global household names like Zoom, CNN, BBC, IKEA, Salesforce, and Equifax all loaded the compromised scripts.

Closer to home here in the Asia-Pacific region, the list of affected organizations hits particularly close to daily life. Banking and financial services saw heavy exposure, including HSBC Hong Kong, HSBC Singapore, HSBC Australia, HSBC Malaysia, HSBC Taiwan, HSBC Vietnam, HSBC Philippines, Hang Seng Investment, Rest Super, Compare Club, and Energy Scout. Retail shoppers across the region were also in the path of the code through Crocs India, Levi’s Japan, Levi’s Indonesia, Levi’s Australia, Levi’s Malaysia, Levi’s Philippines, Levi’s Singapore, Levi’s Korea, and Levi’s New Zealand. Telecom, investment, healthcare, and automotive services rounded out the regional list, affecting Vodafone Australia, TPG Telecom, Betashares, Takeda, Takeda Oncology, and O’Brien Glass.

Seeing familiar regional banks and everyday retail stores on that roster drives home how invisible third-party dependencies really are. You can visit your local bank’s legitimate web address and still have third-party scripts executing silently in the background of your browser.

What the Malicious Code Actually Did to Visitors

Once loaded in a visitor’s browser, the injected JavaScript went to work trying to steal sensitive data. It was built to skim payment card numbers typed into checkout forms, capture browser session cookies that keep you logged into accounts, take screenshots, and silently swap copied cryptocurrency wallet addresses so funds went straight to the attackers. Researchers traced roughly $7,040 in stolen cryptocurrency to wallets tied to this operation on Monday alone, though the true number of skimmed credit cards is much harder to measure from the outside.

Even more concerning is how the script treated mobile visitors. If you browsed one of these affected sites on an iPhone or iPad, the malicious code checked your device and attempted to redirect older, unpatched versions of iOS and iPadOS toward an exploit kit designed to install malware. For those following the technical breakdown of how iPhone users were targeted in the website security breach, it is clear that keeping mobile operating systems current is no longer optional.

Optimizely confirmed on Tuesday that it patched the vulnerability, removed the injected code, revoked active tokens, and reset access for affected accounts. Several companies, including Equifax and Salesforce, quickly disabled the third-party scripts while investigating any potential customer impact. Still, the window of exposure already happened, leaving both businesses and everyday internet users looking for practical ways to protect themselves.

Practical Steps Organizations Can Take Right Now

If you manage a website or lead an engineering team, this breach proves that trusting a vendor is not the same as verifying their code. You do not need expensive proprietary software to lock down third-party scripts in your users’ browsers.

Start by implementing Subresource Integrity, an open web standard that forces browsers to check a cryptographic hash before executing any external JavaScript file. If a vendor’s script changes unexpectedly, the browser simply refuses to run it. Pair this with a strict Content Security Policy, another free, built-in browser defense that restricts which domains can load scripts and where your website is allowed to send form data. Even if malicious code slips onto your page, a well-tuned policy can block it from sending stolen credit card numbers to an external server.

Teams should also isolate sensitive payment pages from marketing and testing tools. Never load analytics or A/B testing scripts on checkout screens or login portals. Finally, open-source dependency scanners like OWASP Dependency-Check can help your developers audit third-party packages continuously before code ever reaches production.

Simple Habits to Protect Yourself as an End User

For the rest of us simply browsing the web, the takeaway is not to panic, because loading a compromised page does not automatically mean your data was stolen. However, taking a few basic precautions today is smart hygiene.

First, install pending updates on your phone, tablet, and computer immediately. Because this attack specifically hunted for older iOS vulnerabilities, running the latest software patch closes the door on those exploit kits. Second, if you logged into any of the affected websites on November 16, log out of all active sessions and change your password so any stolen session cookies become useless.

Third, consider using an open-source content blocker like uBlock Origin in your desktop browser, which routinely blocks third-party tracking and testing scripts by default. If you ever send cryptocurrency, double-check every character of the destination wallet address after pasting it to ensure clipboard hijackers have not altered it. Lastly, turn on real-time transaction alerts through your banking app and review your recent card statements over the next few weeks. When major websites suffer supply chain hiccups, a few minutes of quiet vigilance goes a long way.

###