Optimizely Supply-Chain Malware Attack Exposes 178 Global Websites: How Indian Users and Web Teams Can Protect Cards, Crypto, and iPhones
Visiting a trusted news portal or enterprise website normally feels safe, yet a supply-chain compromise disclosed on November 17, 2026 showed how a single compromised third-party script can turn major sites into silent malware distributors. Security researcher Scott Helme and StepSecurity revealed that attackers injected malicious JavaScript into 188 customer snippets hosted on Optimizely’s experimentation platform, affecting at least 178 organizations including Zoom, BBC, CNN, Salesforce, GitLab, IKEA, and HSBC.
The verdict is clear: although Optimizely purged the malicious code and suspended the attacker payload domain on November 17, visitors who browsed affected sites on November 16 or early November 17 face lingering risks. Depending on your device and browsing activity, the injected script swapped cryptocurrency wallet addresses, skimmed payment card details entered into custom checkout forms, harvested session cookies, and attempted to load the Coruna and DarkSword exploit kits onto unpatched iPhones and iPads.
1. How the OPTIMJACK Supply-Chain Attack Worked
Unlike traditional phishing sites that rely on lookalike domains, this campaign abused a trusted vendor content delivery network. According to forensic breakdowns published by Report URI and StepSecurity, the intrusion unfolded across four stages:
- Project JavaScript Injection: Attackers exploited an authorization flaw in Optimizely’s experimentation platform to write malicious loader tags directly into customer Project JavaScript fields. Because Optimizely’s CDN served the modified files under its own valid TLS certificate, browsers executed the payload without security warnings.
- Multi-Purpose Browser Payload: Once loaded, the external script scanned page text, form inputs, and clipboard contents to replace Bitcoin, Ethereum, TRON, Solana, and TON wallet addresses with attacker-controlled addresses. It also captured non-HttpOnly session cookies and rendered page screenshots using html2canvas.
- Custom Form Card Skimming: The script monitored form submissions and background fetch or XHR requests for Luhn-valid card numbers, expiry dates, and CVV codes typed directly into merchant-hosted checkout forms, though isolated third-party payment iframes such as Stripe or Adyen remained outside its reach.
- Targeted iOS Exploit Delivery: On Apple mobile devices, the payload fingerprinted the iOS version and attempted to trigger the Coruna exploit chain on iOS 13 through 17 or the DarkSword chain on iOS 18.x, while devices running iOS 18.7.3 or newer and iOS 26.3 or newer were immune to those chains.
2. Four Practical Steps to Secure Your Devices, Wallets, and Websites Today
Whether you are an everyday internet user in India or a developer managing web properties, run through these four concrete remediation steps immediately:
- Update iOS and clear active browser sessions on iPhone and Mac: Open Settings, tap General, select Software Update, and confirm your iPhone or iPad runs iOS 18.7.3 or newer, or iOS 26.3 or newer. Next, open Safari or Chrome, clear browsing history and website data from the past 48 hours, and sign out and back in to banking, cloud, and developer portals to invalidate any stolen session cookies.
- Audit card statements and crypto clipboard history: If you entered debit or credit card numbers directly into a web form rather than a UPI intent flow or isolated payment gateway on November 16 or 17, enable instant SMS and email transaction alerts in your bank app and review recent authorizations. Before sending any cryptocurrency transfer, verify the first six and last six characters of the pasted destination address inside your wallet app rather than trusting clipboard contents.
- Enforce Content Security Policy headers and Subresource Integrity on websites: If you manage a web application or WordPress site, restrict which external domains can execute scripts or receive form data by configuring a strict Content-Security-Policy header with explicit script-src and connect-src allowlists. Move payment collection into hosted payment iframes so third-party analytics or A/B testing scripts never share a DOM context with card fields.
- Audit third-party tag managers and rotate project API tokens: Log into Optimizely, Google Tag Manager, or any A/B testing dashboard your team operates, inspect custom JavaScript injection logs for unfamiliar external domains, enforce two-factor authentication for all workspace editors, and rotate API keys tied to experimentation projects.
3. Why Third-Party Scripts Remain a Blind Spot in Modern Web Security
Modern web teams routinely embed dozens of analytics, personalization, and A/B testing snippets without realizing that a single line of third-party JavaScript holds full read and write access to the browser DOM. Even rigorous vendor security questionnaires cannot stop a real-time compromise when malicious code is served directly from a vendor’s own CDN.
For Indian consumers, favoring UPI collect or intent flows and tokenized payment gateways over typing raw card numbers into unfamiliar web forms sharply reduces exposure to browser-based skimmers. For engineering and security teams, isolating checkout pages from marketing scripts and maintaining strict browser security headers turns a potential vendor breach into a contained non-event. Additional technical indicators and domain blocklists are available on Help Net Security.
