On November 16, 2026, visitors to some of the most trusted websites on the internet were shown harmful code without knowing it. The event is now known as the Optimizely supply chain attack, and it reached sites run by Zoom, CNN, the BBC, Salesforce, GitLab, IKEA, HSBC, Equifax and many others. The good news is that the harmful code was removed within about a day, and there are clear, simple steps you can take today to protect your money and your accounts.
This guide explains what happened in plain words, which sites were involved, what the code tried to do, and how you can check your own accounts. It also covers what website owners can learn from the event.
Quick Answer: What Was the Optimizely Supply Chain Attack?
The Optimizely supply chain attack was a security incident in which an unauthorized party added harmful JavaScript code to website testing projects hosted on Optimizely. Optimizely is a tool that many companies use to test and personalize their web pages. Because the code was delivered through a service that these sites already trusted, it appeared on pages that were not directly broken into.
Researchers at Report URI found the harmful code in 188 of the 1,611 Optimizely scripts they checked. These scripts belonged to 178 organizations. The code was built to copy payment card details, swap cryptocurrency wallet addresses, collect some browser data, and push certain iPhone and iPad users toward older, unpatched weaknesses. Optimizely has confirmed the incident, says it fixed the weakness, and says it removed the added code.
What Is a Supply Chain Attack?
A Simple Way to Understand It
Think of a large grocery chain that buys its packaged salad from one supplier. If something goes wrong at the supplier, shoppers at every store can be affected, even though each store did everything right. A supply chain attack works the same way. Instead of breaking into many websites one by one, the attacker targets one shared service that many websites use.
Why Websites Rely on Third-Party Scripts
Most modern websites load small pieces of code from outside companies. These pieces handle things like analytics, chat boxes, ads, video players and page testing. This is normal and often very helpful. It lets a company improve its site without building every tool itself.
The tradeoff is that a website owner must trust that every outside script stays safe. When one of those outside services is tampered with, every site using it can be affected at the same time.
What Is Optimizely and Why Do Websites Use It?
Optimizely is a platform that helps companies run experiments on their websites. A news site might test two headlines to see which one readers prefer. A store might test two checkout layouts to see which one is easier to use. To do this, the site loads a small snippet of code from Optimizely. That snippet pulls in the test details and changes what visitors see.
Because it is so widely used, Optimizely scripts sit on many busy pages. That reach is why this incident drew so much attention. Anything that goes wrong in a tool like this can reach a very large number of visitors very quickly.
How the Optimizely Hack Unfolded on November 16, 2026
The Timeline in Plain Language
Security researchers have shared a timeline based on their own scans. All times below are in UTC, and the figures are preliminary.
- 4:21 a.m. The first harmful code was seen in the Optimizely snippet used by the BBC.
- Mid morning. An early version of the code that swaps crypto wallet addresses appeared.
- Early afternoon. A component that copies payment card details was added.
- Late afternoon. More infrastructure aimed at iPhone and iPad visitors was added.
- Evening. Report URI scanned widely and found the problem across many sites.
- Late evening. Optimizely and affected companies cleaned up the files. Report URI said all of the infected files it was monitoring were clean by 11:11 p.m. UTC.
- November 17. Optimizely published a notice confirming the incident.
The attacker changed the harmful code several times during the day, which is one reason researchers describe the incident as active and fast-moving.
Where the Harmful Code Was Placed
Researchers report that the harmful lines were added to a customer-editable section of Optimizely projects called Project JavaScript. The rest of each snippet looked normal. The files were still served from Optimizely’s own delivery network with its normal certificate, so web browsers treated them as trusted.
What Optimizely Has Said
In its notice, Optimizely said an unauthorized party used a weakness in its Experimentation product to add harmful JavaScript to some customer projects. The company says it fixed the weakness, removed the injected code from affected projects, and added more security measures. It continues to share updates on its status page.
Which Websites and Companies Were Affected?
Well-Known Names on the List
According to Report URI and several news outlets, organizations whose sites served the harmful code included Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, Peacock and Fox News. Optimizely’s own site was also reported among them. The total count most often cited is 178 organizations, and some outlets report slightly higher numbers. Optimizely has not yet published a full count of its own, so these numbers should be seen as a minimum.
What the Companies Have Said
Several companies took quick action. Zoom said it turned off Optimizely across its production sites as a precaution and had not found an impact on customer data. Salesforce said it was disabling Optimizely scripts while it looked into the changes. Equifax and Salesforce both said they had no evidence that customer data stored on their own systems was affected. These statements are encouraging, because they show that the companies’ core systems were not the entry point.
What Did the Malicious Code Try to Do?
Researchers describe the code as a toolkit with several parts. Here is what each part was designed to do.
Part One: A Payment Card Skimmer
A card skimmer is code that watches what you type into a payment form and tries to send a copy to the attacker. If you entered card details on an affected page while the code was active, those details may have been exposed. This is why checking your card statements is the first step in the protection list below.
Part Two: A Crypto Address Swapper
Often called a crypto clipper, this part looks for cryptocurrency wallet addresses on a web page and swaps them with addresses controlled by the attacker. A person who copies an address, or reads one from the page, could send funds to the wrong place without noticing. Researchers say the code held replacement addresses for several coins, including Bitcoin and Ethereum. Confirmed losses have not been fully reported, and early estimates from researchers were small, but those figures are still being reviewed.
Part Three: Cookie Collection and Screenshots
Report URI also reported that the toolkit could collect some browser cookies and capture screenshots of web pages. Cookies can keep you signed in to a site, so this is a reason to sign out and sign back in on important accounts as a precaution.
Part Four: iPhone and iPad Targeting
On Apple devices running older software, the code tried to load exploit kits that researchers named Coruna and DarkSword. These target known weaknesses that Apple has already fixed in newer updates. Report URI lists iOS 18.7.3 or later, and iOS 26.3 or later, as safe versions. Researchers note that no public figure exists for how many devices were actually affected, and some details of the iPhone portion are still being studied.
Why Updates Matter So Much
Software updates close the doors that exploit kits try to use. A device that is fully updated is much harder to affect, even when it visits a page that served harmful code.
A Reassuring Point for Many Readers
If your iPhone or iPad was already running a recent version of iOS, the iPhone portion of this toolkit was far less likely to work on your device.
Quick Reminder
Updating takes only a few minutes and is one of the best habits for staying safe online.
Is the Attack Over?
What Is Known
Optimizely says the weakness has been fixed and the injected code has been removed. Report URI’s monitoring agrees that the infected files it tracked were clean by late on November 16 and stayed clean afterward. Affected companies have also taken their own steps, such as turning off the script while they review it.
What Is Still Being Studied
Researchers have not yet shared how the attacker first gained the ability to change the Optimizely projects. The total number of visitors who loaded the code is also not yet known. Because of this, the most helpful approach is a calm one. Take the short checks below, and watch for updates from Optimizely and the sites you use.
How to Protect Your Accounts After the Optimizely Supply Chain Attack
The steps below are simple and take little time. You do not need special tools for any of them.
Step 1: Update Your Phone, Tablet and Browser
Open your device settings and install the latest software. On iPhone and iPad, go to Settings, then General, then Software Update. Also update your web browser to its newest version. Turning on automatic updates keeps you protected in the future.
Step 2: Review Your Card and Bank Statements
Look at charges made on or after November 16, 2026, especially if you shopped, paid a bill or joined a meeting that required payment on a site that may have been affected. Look for small charges you do not recognize, since small test charges are a common sign of misuse.
Step 3: Contact Your Card Issuer if Something Looks Wrong
Call the number on the back of your card or use your bank’s app. Ask about a replacement card number. Under federal rules in the United States, your protection depends on the type of card and how quickly you report. Credit card users are generally protected from most unauthorized charges when they report on time. Debit card rules have different time limits, so reporting early matters. Your card issuer can explain how the rules apply to you.
Step 4: Turn On Transaction Alerts
Most banks and card companies let you receive a text or app alert for every purchase. This gives you near real-time notice of any activity you did not make.
Step 5: Consider Virtual or One-Time Card Numbers
Many banks now offer virtual card numbers for online shopping. These are separate numbers linked to your real account, which you can turn off at any time without replacing your main card.
Step 6: Sign Out and Sign Back In to Important Accounts
Because the toolkit could collect some cookies, signing out of email, banking, work and shopping accounts and then signing in again can end old sessions. This is a quick and low-cost precaution.
Step 7: Strengthen Your Sign-In Settings
Use a unique password for each account, and consider a password manager to keep track of them. Turn on two-factor authentication wherever it is offered. Where possible, use passkeys, which are harder to steal than passwords.
Step 8: Check Your Credit Reports
You can view your credit reports for free at AnnualCreditReport.com, the central site that US law directs the three national credit bureaus to provide. If you ever suspect identity misuse, the Federal Trade Commission offers a recovery plan at IdentityTheft.gov. You may also choose to place a fraud alert or credit freeze, which is free.
Extra Steps for Cryptocurrency Users
Always Verify the Address Before Sending
If you sent or planned to send crypto on or around November 16, take extra care. Before approving any transaction, compare the full wallet address, not only the first and last few characters. Do this on your wallet app or a trusted device, and not only from the web page you were using.
Confirm With the Recipient
For any larger transfer, confirm the receiving address through a separate, trusted channel such as a phone call or a message you already know is genuine.
Use a Small Test Transaction
Sending a very small test amount first allows you to confirm that it arrives at the right place before you send the full amount.
Review Your Wallet History
Look through recent transactions for anything you do not recognize. If you find a problem, contact your exchange or wallet provider right away and consider filing a report with the FBI’s Internet Crime Complaint Center at ic3.gov.
Lessons for Website Owners and Business Teams
The Optimizely supply chain attack offers practical lessons for anyone who runs a website. The goal is to build good habits, not to worry.
Keep a List of Every Third-Party Script
Know which outside scripts run on your site, especially on pages that handle logins or payments. Remove any that are no longer needed.
Use a Content Security Policy
A Content Security Policy, often shortened to CSP, tells the browser which outside sources a page may contact. One researcher found that, among a sample of hosts tested after this event, only a small share had settings that stopped the harmful code from sending data out. This shows how helpful a well-built CSP can be. Test your settings carefully, since an incomplete policy can leave gaps.
Monitor Scripts for Unexpected Changes
Tools that watch what scripts do in real visitor browsers can spot sudden changes, as Report URI did in this case. Regular checks help you find issues sooner.
Limit Who Can Edit Script Settings
Give only the people who need it permission to edit testing and tag tools. Use strong sign-in controls on every vendor account and review access often.
Protect Payment Pages Extra Carefully
Payment pages deserve the highest level of care. Industry payment security standards, including PCI DSS version 4.0, ask organizations to manage and monitor the scripts on payment pages. Consider moving checkout to a hosted payment field that keeps third-party scripts away from card entry.
Prepare a Response Plan
Decide ahead of time who will turn off a vendor script, who will contact customers and who will speak with the vendor. Quick action, like the steps Zoom and Salesforce took, can reduce the time a site is exposed.
Why This Event Also Shows Progress
It is easy to read about a security incident and feel discouraged, but there are real positives here. An independent research team noticed the problem on the same day. The vendor confirmed it, fixed it and removed the code. Large companies acted quickly and shared updates. Shared public information also let everyday people take action within hours.
Each event like this helps the whole industry build stronger habits, from better monitoring to tighter access controls. For everyday users, the lesson is encouraging: a few simple routines, such as updating devices, watching statements and using strong sign-in settings, go a long way.
Frequently Asked Questions
Was Optimizely hacked?
Optimizely confirmed that an unauthorized party used a weakness in its Experimentation product to add harmful code to some customer projects. The company says it fixed the weakness and removed the code.
Were Zoom, CNN and the BBC hacked directly?
No. Based on public reports, the sites were not broken into directly. The harmful code reached visitors through the Optimizely scripts those sites used. Zoom and others have said they found no impact on customer data on their own systems.
Is it safe to use these websites now?
Researchers report that the infected files they monitored were clean by late November 16, and several companies disabled the script while they reviewed it. As always, keep your device updated and watch your statements.
How do I know if my information was taken?
There is no public list of affected visitors. The best approach is to review your card statements, check any crypto transactions made around November 16, and turn on alerts so you see activity as it happens.
Does updating my iPhone really help?
Yes. The iPhone portion of the toolkit targeted older iOS versions. Report URI lists iOS 18.7.3 or later, and iOS 26.3 or later, as safe versions.
What should I do if I see a charge I do not recognize?
Contact your card issuer right away, ask about a replacement card, and keep a record of the call. Reporting quickly gives you the strongest protection under the rules that apply to your card type.
What is the main takeaway?
This was a serious event, but the response was fast and the next steps are simple. Update your devices, review your accounts, and use strong sign-in protection.
About This Article and Its Sources
This article is based on public reports and statements from Report URI and researcher Scott Helme, Optimizely, Zoom, Salesforce, Equifax, BleepingComputer, Malwarebytes, Infosecurity Magazine, Help Net Security and other independent security researchers, published between November 16 and November 19, 2026. Some numbers, such as the count of affected organizations and the number of devices reached, are preliminary and may change as investigations continue. This article is for general information and is not legal, financial or security advice. For questions about your own accounts, please contact your bank, card issuer or a qualified professional. Check the Optimizely status page for the latest updates.
Final Thoughts
The Optimizely supply chain attack reminds us that trusted websites depend on many outside services, and that staying safe is a shared effort between companies and everyday people. Update your devices, review your statements, double-check crypto addresses, and use strong sign-in protection. These small habits make a big difference, and they will serve you well long after this event is behind us.
Leave a Reply
Your email address will not be published.
0 Comments On this Blog