Optimizely Hack Put Card Skimmer on 178 Sites: What to Do
Share: https://www.ellixorlabs.com/blog/optimizely-malware-attack-178-sites-what-to-do (copy URL for iMessage or social)
Published (display in IST)
Updated (IST)

Malicious code reached Zoom, the BBC, CNN, HSBC and more than 170 other organisations through Optimizely on 16 November, swapping crypto addresses and skimming cards. Here is what to check now.
Malicious code was added to the website scripts of at least 178 organisations on 16 November 2026, including Zoom, the BBC, CNN, HSBC, GitLab, IKEA and Crocs India, after an attacker abused a flaw in Optimizely, a service big brands use to test changes to their websites. For several hours, visitors to affected pages could have had cryptocurrency wallet addresses swapped, card details typed into on-site forms skimmed and, on older iPhones, been targeted with exploit kits. Optimizely confirmed the incident in a status page notice at 01:02 UTC on 17 November (06:32 IST), saying it had fixed the vulnerability and removed the injected code. The brands' own code was not changed. The malware arrived through a script their sites already trusted, which is why any business that loads outside JavaScript should pay attention.
What happened to Optimizely's scripts?
The attack was uncovered by security researcher Scott Helme, whose company Report URI sells script monitoring tools, and set out in a detailed write-up. Optimizely Web works by having each customer site load a JavaScript file, called a snippet, from Optimizely's servers. Customers can add their own custom code, called Project JavaScript, which runs on every page. Report URI says the attacker added a line to that field which pulled in a script from an outside domain, so the file still came from cdn.optimizely.com with Optimizely's certificate. It first saw the injection at 04:21 UTC on 16 November, found 188 infected snippets belonging to 178 organisations among the 1,611 it checked, and by 21:52 UTC only one was still infected. BleepingComputer separately confirmed the script loading on sites including Zoom, GitLab, the BBC and Salesforce. An Optimizely spokesperson told Gizmodo that an unauthorised party "exploited a vulnerability in the Experimentation account signup flow" and that the company had "blocked access to the vulnerable path and deployed a fix." Optimizely has not said how many customers were affected.
The payload, which Report URI says was rebuilt 26 times during the day, did several things at once. It scanned pages, form fields and the clipboard for wallet addresses on networks such as Bitcoin, Ethereum, Solana and Tron and replaced them with the attacker's, so a copied address could paste as someone else's. From 13:43 UTC it also watched for card numbers, expiry dates and security codes entered in a site's own forms. Cards typed into payment boxes hosted by providers such as Stripe or Adyen were out of its reach. It could send cookies not protected by the HttpOnly setting, plus a screenshot of the page, to the attacker, and on iPhones and iPads it tried to load the Coruna and DarkSword exploit kits. Report URI counted about $7,040 in cryptocurrency received by the attacker's wallets by 19:25 UTC, but could not see how many cards or cookies were taken.
What should visitors and website owners do now?
If you used a large brand's website on 16 November, a few checks are enough for most people. If you sent cryptocurrency that day, compare the destination address in your wallet history with the one you meant to use, because blockchain transfers generally cannot be reversed. If you typed card details into a site's own checkout or form that day, watch your statements and ask your bank for a new card if anything looks unfamiliar. On an iPhone or iPad, install the latest update from Settings, General, Software Update. Report URI says the exploit kit's own comments describe iOS 18.7.3 and later, and iOS 26.3 and later, as patched, and that pages on iOS 18.6 or earlier reloaded every 60 seconds to retry the attack. Signing out of important accounts and back in again also replaces old session cookies.
If your business uses Optimizely Web, Report URI advises opening every project's Project JavaScript and every experiment's custom code, searching for 1688360.cc, atob( and anything your team did not write, reviewing which users, API tokens and integrations can write to the account, and rotating credentials. Treat cards entered in your own form fields on 16 November, and secrets held in cookies without HttpOnly, as exposed. The wider lesson applies to any site that loads analytics, chat, testing or ad scripts: a trusted supplier can change what runs on your pages without you deploying anything. A content security policy (CSP) is a browser rule listing where scripts may load from and send data. Of the affected organisations Report URI could assess, 24 had one strict enough to block the payload and 68 had none at all. Keep card entry inside your payment provider's hosted fields, limit who can publish custom code in marketing tools, and track third-party scripts as part of regular website maintenance. Bitly, whose hijacked old short links we covered on 16 November, was also on Report URI's list.
Frequently asked questions
Which websites were affected by the Optimizely malware attack? Report URI found the malicious code in Optimizely scripts used by 178 organisations, including Zoom, the BBC, CNN, HSBC, Salesforce, GitLab, IKEA, Equifax, Ledger and Crocs India, and says the real number is likely higher. Almost every script was cleaned by late on 16 November (UTC), and Optimizely says the injected code has been removed.
I visited Zoom or the BBC on 16 November. Is my card or crypto at risk? Only if, on an affected page that day, you typed card details into the site's own form, copied or sent a crypto wallet address, or browsed on an older iPhone. Check wallet transfers and card statements and update iOS. Report URI says cards entered in hosted payment boxes such as Stripe were out of the code's reach.
How can a business stop third-party scripts being hijacked? Limit who can publish custom code in tools such as Optimizely, review users and API tokens, and use a strict content security policy that lists where scripts may load from and send data. Monitor changes to third-party scripts, and keep card entry inside your payment provider's hosted fields.
If you are not sure which outside scripts run on your website or checkout, talk to our team. Our web applications team can review your third-party scripts, content security policy and payment flow.
FAQ
Which websites were affected by the Optimizely malware attack?
Report URI found the malicious code in Optimizely scripts used by 178 organisations, including Zoom, the BBC, CNN, HSBC, Salesforce, GitLab, IKEA, Equifax, Ledger and Crocs India, and says the real number is likely higher. Almost every script was cleaned by late on 16 November (UTC), and Optimizely says the injected code has been removed.
I visited Zoom or the BBC on 16 November. Is my card or crypto at risk?
Only if, on an affected page that day, you typed card details into the site's own form, copied or sent a crypto wallet address, or browsed on an older iPhone. Check wallet transfers and card statements and update iOS. Report URI says cards entered in hosted payment boxes such as Stripe were out of the code's reach.
How can a business stop third-party scripts being hijacked?
Limit who can publish custom code in tools such as Optimizely, review users and API tokens, and use a strict content security policy that lists where scripts may load from and send data. Monitor changes to third-party scripts, and keep card entry inside your payment provider's hosted fields.
Talk to Ellixor Labs about this topic.
Source: Optimizely