178+ global brands served malware, and not one of them was hacked
In-house web development and website maintenance in Dubai since 2011. Rated 4.9 from 201 Google reviews.
Request a script reviewOn Monday 16 November 2026, the websites of 178 large organisations handed malicious code to their own visitors. The BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM and Ledger were all on the list.
Here is the part that matters. None of them was hacked. Their servers were fine. Their passwords were fine. Their own code was never touched. The researcher who found it said it plainly: "Their own infrastructure was untouched; a vendor's script turned hostile and their sites served it to every visitor."
No UAE, Gulf or Middle East company has been named among the victims as of now. That is worth saying straight away, and it is also not the point. Almost every business website in the UAE loads code from outside companies, exactly as these 178 did.
Find out whose code is running on your website
Tomsher will produce an inventory of every third-party script your site loads, who controls each one, what it can reach, and which ones carry risk out of proportion to their value. You get the written findings whether or not any work follows.
If the review finds your script footprint is already small and well controlled, that is what the report will say.
What happened, explained simply
Think of your website as your shop. Over the years you have given a few outside companies a key, so they can update things for you without calling a developer every time. One does your analytics. One runs your chat window. One tests which version of a page sells better.
Those keys are normal. Every modern website hands them out. The companies use them to load small pieces of code onto your pages, and that code runs with the same access as everything else on your site.
On 16 November, someone got hold of the keys belonging to one of those companies. Optimizely makes a testing and personalisation tool, and an attacker was able to add their own code to customer accounts inside it. From that moment, every website using the tool loaded the attacker's code and showed it to visitors, automatically, all day.
Nobody broke into the BBC. Nobody guessed a password at HSBC. The attacker changed one thing in one supplier's system, and 178 websites passed it on for them. It ran for about seventeen hours before most sites were cleaned.
That is what a supply chain attack is. You are not the target. Something you rely on is, and you become the delivery van.
The confirmed facts, from the researchers and the vendor
These are the facts as the research and the vendor state them, and nothing beyond.
| What is established | Detail and source |
|---|---|
| Scale | 188 infected snippets belonging to 178 organisations, found among 1,611 snippets checked by Report URI. The researcher notes the real number is likely higher |
| Route in | Malicious JavaScript was added to customers' Optimizely project code and served from Optimizely's own content delivery network. Report URI states plainly that this was not a CDN cache-poisoning attack, because the network served exactly what it was given |
| Duration | First injection seen at 04:21 UTC, mass clean-up between roughly 20:40 and 21:10 UTC, one snippet still infected at 21:52 UTC. ZeroFox described it as running from about 4am UTC until around 9pm |
| Persistence | The payload was rebuilt 26 times during the day, which indicates active operation rather than a single drop |
| Who was hit | Report URI's sector breakdown puts banking and finance highest at 32 organisations, followed by technology and software at 23, retail and fashion at 20, streaming and entertainment at 12, and news and media at 10 |
| Self-hosting did not help | Customers serving the snippet from their own domain were affected too, because the content still came from the same Optimizely project |
| Money | Attacker wallets had received about USD 7,040 as at 19:25 UTC on 16 November, per Report URI. StepSecurity put it nearer USD 6,600. Both StepSecurity and Hudson Rock caution that the blockchain does not show which of those transfers came from visitors to the affected sites |
| Not yet explained | How the attacker obtained write access across many unrelated customer projects. Report URI said that is for Optimizely to explain, and at the time of writing no public explanation had been given |
One detail deserves more attention than it has received. Report URI found that Optimizely's own websites were affected, including its main site and its login page. A vendor whose product distributes code to hundreds of major brands was serving the same malicious code from its own front door.
What Optimizely has said
Optimizely published a single incident notice on its status page, titled Web Experimentation Security Incident, posted at 01:02 UTC on 17 November 2026. It states that an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects, that Optimizely has fixed the vulnerability and removed the injected code from affected projects, that it has taken steps to secure affected user accounts, and that it has put additional protections in place to prevent unauthorized code from being delivered.
Two things about that notice matter to a business reading this. The first is that at the time of writing it carried the status Monitoring rather than Resolved, with no later update posted. The second is that it does not say how the attacker got in. One outlet has reported that the flaw lay in a sign-up process, but that detail does not appear in Optimizely's own notice, so it is not repeated here as fact.
Anyone running Optimizely Web Experimentation should be reading that status page directly rather than relying on a summary, including this one.
Why this is worse than a normal website hack
In a normal hack there is something to blame. A weak password. An out-of-date plugin. A server left open. You find what went wrong, you fix it, and you move on.
This one takes that away. Scott Helme, the researcher who found it, put it directly: "The uncomfortable lesson is that none of the victims were breached." There was nothing for these companies to fix on their own systems. Years ago each of them made a sensible decision to use a well-known marketing tool. On one Monday, that decision served malware to every visitor.
That is the shape of a supply chain attack, and it is the same pattern as the cloud outages that have taken services down this year. The failure arrives through something you depend on and do not control, which is why the response belongs in architecture and vendor management rather than in a firewall. The Google Cloud outage that hit the London region made the same point about availability. This one makes it about integrity, which is worse, because an outage is obvious within minutes and a hostile script can run for seventeen hours while every page looks completely normal.
What it did to people who visited those websites
Described at the level a business owner needs, rather than a level that would help anyone repeat it.
| Effect on a visitor | What it meant in practice |
|---|---|
| Cryptocurrency addresses were swapped | Wallet addresses shown on the page, or copied from it, could be replaced with the attacker's, so a payment went to the wrong recipient |
| Card details were captured | A skimmer added during the day could read card details typed into a site's own payment form. Cards entered into a payment provider's hosted frame were out of reach, which is a meaningful argument for hosted payment pages |
| Session cookies and screenshots were taken | Cookies not marked HttpOnly, the page address and an image of the page could be sent to the attacker in some circumstances |
| iPhone and iPad visitors were targeted | Exploit kits were delivered to devices on older iOS versions. Security firms analysing it stated they had not demonstrated compromise of an actual device, so the delivery is confirmed and the outcome is not |
The reason this list should worry a business owner is not the money. About seven thousand dollars reached the attacker's wallets, and even that cannot be firmly tied to visitors of the affected sites. The reason is that for seventeen hours, major brands were the delivery mechanism for an attack on their own customers, and most of them learned about it from a researcher rather than from their own monitoring.
Your own website is probably doing the same thing
Most UAE business websites load code from between five and twenty outside companies. Most owners could not name half of them. The usual list looks like this.
- Analytics and tag managers. Often the deepest access of all, because a tag manager is explicitly designed to let someone add new code to your site without a developer.
- Advertising and remarketing pixels. Added once for a campaign and almost never removed when the campaign ends.
- Chat widgets and support tools. Loaded on every page, including checkout and account pages.
- Testing and personalisation platforms. The category involved in this incident, and by design they rewrite what the page shows.
- Booking, review, map and social embeds. Each one a separate company with its own security posture.
- Fonts, icons and convenience libraries. Usually harmless, occasionally the oldest and least reviewed thing on the site.
Every one of those is code you did not write. It runs with the same access as your own code. It changes whenever the supplier decides, and nobody tells you when it does. That is normal, and it is how the whole web works. The Optimizely incident is simply what it looks like when one of those suppliers is compromised.
Start with the inventory
Most businesses cannot name the code running on their own site
The first deliverable is a list. Every third-party script, who owns it, what it can see, whether it still earns its place, and which ones a reasonable business would remove this month. It is the lowest-cost piece of security work available and almost nobody has it.
Four things to check on your own website this week
Four questions. Any business with a website can answer them, and they are worth answering while this is fresh.
- Do you use Optimizely Web Experimentation. If so, your marketing team will know before your IT team does, because this is usually a marketing purchase. Check Optimizely's status page directly and contact your account manager for confirmation on your own projects.
- What else is loading on your site. Not what you think is loading. What is actually loading, today, on your live pages, including the tags someone added for a campaign in 2024.
- Which of those scripts touch a payment or login page. A chat widget on a blog post is a different risk from the same widget on a checkout. Most sites have never made that distinction.
- Who would notice. If a third-party script on your site changed at four in the morning, is there anything in place that would tell you, or would you find out when a customer or a researcher told you.
Question four is the one that separates the organisations in this story. Several of them are large, well-resourced companies with security teams, and they still learned about it from an external researcher. A smaller business with no monitoring at all would simply never have known.
What actually protects a website against this
There are proven protections for exactly this risk. They work. None of them is a switch you flick, and each one will break a live website if applied carelessly. That is the honest reason most sites do not have them.
| Control | What it does | What it does not do, and why it needs care |
|---|---|---|
| Content Security Policy | Tells the browser which sources are allowed to run code and where data may be sent. Report URI states that an appropriate policy in enforcement mode could have blocked key parts of this attack | It does not protect you from a script you have explicitly allowed, which is why permitting the vendor's own domain would not have helped here. Policies are also easy to write in a form that silently permits far more than intended, and a strict policy applied without testing takes functioning features offline |
| Subresource integrity | Lets the browser refuse a third-party file if its contents have changed from what you approved | It only works on files that do not legitimately change. Many marketing platforms update their files constantly by design, so this is a precise tool rather than a general one, and deciding where it applies is the actual work |
| Hosted payment pages | Keeps card entry inside the payment provider's own frame, out of reach of scripts on your page. This limited the damage in this incident | It does not protect anything else on the page, and some businesses have moved away from hosted frames for design reasons without recording the trade-off |
| Tag and script governance | A named owner for every script, a review before anything new is added, and removal when a campaign ends | It is a process rather than a technology, which is why it is the control most often skipped and the one that prevents the most incidents |
| Change monitoring | Alerts when the third-party code on your site changes unexpectedly | It detects rather than prevents. In this incident, detection within the first hour rather than the seventeenth would have been the whole difference |
| Cookie and session hygiene | Limits what a hostile script can read if one does run | It reduces the blast radius rather than stopping the attack, and it is usually a development change rather than a setting |
The specifications for these are public and well documented, and any competent developer can read them. What takes experience is deciding which apply to your site, in what order, and how to introduce them without taking working functionality offline on a live business website. That sequencing is the job, and it is the part a specification cannot give you.
What to put in your supplier agreements
The commercial lesson sits alongside the technical one. Every third-party script on your website is a supplier with write access to your customer-facing pages, and most businesses have never treated it that way in a contract.
- Notification. Does the vendor have an obligation to tell you about a security incident affecting the code they serve you, and in what timeframe. Several organisations in this story found out from a researcher's blog.
- Status transparency. Does the vendor run a public status page, and does it cover security incidents rather than only uptime. Optimizely does, which is to its credit, and it is how most customers learned the official position.
- Removal. How quickly can you switch a vendor's script off entirely, and does anyone on your side know how. Salesforce reportedly disabled scripts as a precaution while investigating, which is only possible if someone knows where the switch is.
- Scope. Is the vendor's code on every page, or only where it is needed. This is almost always a decision nobody made.
For UAE businesses handling personal data there is a further consideration. Federal Decree Law No. 45 of 2021 Regarding the Protection of Personal Data applies to processing through electronic systems, and a hostile script reading customer data from your pages is processing happening on your website, through a supplier you selected. That is a conversation worth having with your legal reviewer before an incident rather than during one.
How Tomsher helps with the code running on your site
This is ordinary web development and maintenance work rather than a specialist security product, which is the point. It belongs with the team that already looks after the site.
| What is involved | What it changes |
|---|---|
| Third-party script inventory | A written list of every script your site loads, its owner, its access and its business justification. Most clients remove two or three on the first pass |
| Risk mapping by page | Separating scripts running on a blog post from scripts running on checkout, login and account pages, which is where the same code carries very different consequences |
| Policy design and staged rollout | Designing a Content Security Policy for your site, testing it in report-only mode first and moving to enforcement once it is proven, so nothing breaks in production. See web development |
| Payment path review | Confirming card entry sits inside the provider's own frame and that nothing on the page can reach it. See payment gateway integration and ecommerce development |
| Ongoing monitoring and governance | Watching for unexpected changes to third-party code, reviewing new tag requests before they go live, and removing what campaigns leave behind. This runs under an annual maintenance contract, and the case for one is set out in why a website AMC matters in the UAE |
| Platform and plugin currency | Keeping the site's own code current, since third-party scripts are one supply chain and your platform and its plugins are another. See WordPress support and keeping WordPress updated |
| Architecture review | For businesses where the website carries revenue, looking at how the front end, the payment path and the data layer fit together. See ecommerce architecture and web application development |
Tomsher has built and maintained business websites from Dubai since 2011, works fully in house and is rated 4.9 out of 5 from 201 Google reviews. Related reading on operational security sits on business cybersecurity awareness, identifying phishing email and shortening certificate lifespans.
What a realistic assessment of your risk looks like
A review of this kind produces four things. An inventory of what is actually running on your site, a risk rating per script based on the pages it touches, a ranked list of what to remove, restrict or monitor, and a staged plan for the controls that fit your platform.
What it does not produce is a promise of immunity, and any supplier offering one after an incident like this should be treated carefully. A customer of a compromised vendor is exposed whoever built their website. What changes the outcome is how much third-party code is running in the first place, how tightly it is scoped, and how quickly anyone notices when it changes. Those three are within your control, and they are what the work addresses.
For most UAE businesses the first pass is quick and the findings are unglamorous. Scripts nobody can justify, a tag manager with more access than anyone realised, a chat widget loading on the payment page, and no alerting at all. Fixing that list is a good week's work and it removes most of the exposure this incident demonstrated.
Web, digital and AI, in house in Dubai
Find out what is running on your website
Send your website address and tell us which platform it runs on. Back comes an inventory of the third-party code your site loads, what each script can reach, which pages carry the most risk, and a ranked plan for reducing it.
M05, Wafi Residence, Oud Metha Road, Umm Hurair 2, Dubai. Fully in house, rated 4.9 out of 5 from 201 Google reviews.
Frequently asked questions
What was the Optimizely supply chain attack
On 16 November 2026, malicious JavaScript was added to customer projects in Optimizely Web Experimentation and served to visitors of 178 organisations' websites from Optimizely's own content delivery network. Security research firm Report URI found 188 infected snippets among 1,611 it checked, and noted the real number is likely higher. The organisations affected were not themselves breached. Their servers and code were untouched, and a tool they had embedded years earlier delivered the malicious code on their behalf for roughly seventeen hours.
Which companies were affected by the Optimizely incident
Reports name the BBC, CNN, Zoom, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, Peacock, TalkTalk and Smartsheet among others. Report URI's sector breakdown puts banking and finance highest with 32 organisations, then technology and software with 23, retail and fashion with 20, streaming and entertainment with 12, and news and media with 10. Report URI also found Optimizely's own websites affected, including its main site and its login page.
Were any UAE businesses affected
No UAE, Gulf or Middle East organisation has been named among the victims in the reports reviewed for this article, which covered the original research and four independent security publications. That does not mean none was affected, only that none has been named. It is also not the main risk for a UAE business. The relevant exposure is that almost every business website in the region loads third-party code it does not control, and this incident shows what happens when one of those suppliers is compromised.
What has Optimizely said about the incident
Optimizely published an incident notice on its status page titled Web Experimentation Security Incident, posted at 01:02 UTC on 17 November 2026. It states that an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects, that Optimizely has fixed the vulnerability and removed the injected code, that it has taken steps to secure affected user accounts, and that it has put additional protections in place. At the time of writing the notice carried the status Monitoring rather than Resolved, and it did not explain how the attacker obtained access.
How did the attackers get in
That has not been explained publicly. Report URI stated it did not know how the attacker obtained write access across many unrelated customer projects and that the explanation was for Optimizely to give. Optimizely's notice refers to a vulnerability in Experimentation without describing it. One publication has reported that the flaw lay in a sign-up process, but that detail does not appear in Optimizely's own statement, so it should be treated as unconfirmed until the vendor publishes a root cause.
What could the malicious code actually do
Four things, as described by the researchers. It could replace cryptocurrency wallet addresses shown or copied on a page, so payments went to the attacker. It could capture card details typed into a site's own payment form, though cards entered into a payment provider's hosted frame were out of reach. It could send session cookies not marked HttpOnly, the page address and a screenshot of the page. And it attempted to deliver exploit kits to iPhone and iPad visitors on older iOS versions, although the firms analysing it stated they had not demonstrated compromise of an actual device.
How much money was stolen
Report URI found attacker wallets had received about USD 7,040 as at 19:25 UTC on 16 November, and StepSecurity put the figure nearer USD 6,600. Both StepSecurity and Hudson Rock have cautioned that the blockchain does not show which of those transfers came from visitors to the affected sites, so the amount actually taken from those visitors is not established. The volume of card details, cookies and session data taken is not known, and Report URI said plainly it cannot see those numbers from outside.
Would hosting the script on our own domain have protected us
No, and this is one of the most useful findings in the research. Report URI found that customers serving the snippet from their own domain were affected too, because the content still came from the same Optimizely project. Serving a third-party file from your own address changes where the browser fetches it from, not who controls what is in it. The protection comes from controlling what the code is permitted to do, not from where it is hosted.
Would a Content Security Policy have stopped this
Partly, and only if correctly configured. Report URI states that an appropriate policy in enforcement mode could have blocked key parts of the attack before they succeeded. The limitation is important though. A policy that permits the vendor's own domain, as most would, does not stop malicious code arriving from that vendor. Policies also need to be tested in report-only mode before enforcement, because a strict policy applied without testing takes working features offline on a live site.
How many third-party scripts does a typical business website run
Most UAE business websites load code from somewhere between five and twenty third parties, including analytics, tag managers, advertising pixels, chat widgets, testing platforms, review and map embeds and font libraries. Each one runs with the same access to your pages as your own code and updates whenever the supplier chooses. Very few business owners can name them all, which is why an inventory is usually the first and most revealing piece of work.
What should a UAE business do about this now
Establish four things. Whether you use Optimizely Web Experimentation, in which case check the vendor's status page and speak to your account manager. What third-party code is actually loading on your live pages today. Which of those scripts run on payment, login and account pages, where the consequences differ. And whether anything would alert you if third-party code on your site changed unexpectedly. Several large organisations in this incident learned about it from an external researcher rather than their own monitoring.
Can Tomsher review our website for this kind of risk
Yes. The work covers an inventory of every third-party script your site loads, a risk rating based on which pages each one touches, a ranked list of what to remove, restrict or monitor, and a staged plan for controls such as a Content Security Policy introduced in report-only mode before enforcement so nothing breaks. Ongoing monitoring and tag governance run under an annual maintenance contract. Tomsher has built and maintained business websites from Dubai since 2011, works fully in house and is rated 4.9 out of 5 from 201 Google reviews.
Sources
- Optimizely service status, Web Experimentation Security Incident. The primary source for the vendor's position, the wording of its statement, the affected component and the incident status at the time of writing. status.optimizely.com
- Report URI, World's Largest Brands Infected With Malware Via Optimizely, by Scott Helme, 16 November 2026. The original research and the source for the counts, the timeline, the sector breakdown, the wallet figure, the finding on self-hosted snippets, the Content Security Policy assessment and the finding that Optimizely's own sites were affected. blog.report-uri.com
- TechTarget, Optimizely supply chain attack turns trusted scripts against 178 orgs, by Alissa Irei, 17 November 2026. The source for the quotes from Scott Helme on none of the victims being breached, and for comment from Peter Lowe of ZeroFox and George Gerchow of IANS and Bedrock Data. techtarget.com
- The Hacker News, by Swati Khandelwal, 17 November 2026. Independent confirmation of the counts and timeline, the Cynet assessment on iOS impact, and the report of a Smartsheet script being re-infected after cleaning. thehackernews.com
- The Register, by Carly Page, 17 November 2026. Independent confirmation of the counts and the Optimizely statement. Its report that the flaw lay in a sign-up process does not appear in Optimizely's own notice and is not treated as established here. theregister.com
- Help Net Security, by Sinisa Markovic, 17 November 2026. Independent confirmation of the counts and statement, the Hudson Rock caution on attributing cryptocurrency transfers, and the report that Salesforce told Reuters it was investigating and had disabled scripts as a precaution. helpnetsecurity.com
All sources were read on 18 November 2026. Figures and wording are quoted as published on that date. Optimizely had not published a root cause analysis at the time of writing, and the incident notice carried the status Monitoring. Anyone using Optimizely Web Experimentation should check the vendor's status page directly for the current position.
About the author
Related services and reading
Keeping a business website current, controlled and monitored.
By Digital Team. Updated on 18-11-2026
Optimizely supply chain attack 2026 Optimizely malware attack Optimizely security incident third party script security website supply chain attack malicious JavaScript injection website security UAE third party website vulnerabilities
19-11-2026
Best AI Development Company in Abu Dhabi, How to Choose the Right Partner for Your Business
18-11-2026
Best AI development company in Dubai
17-11-2026
Best AI consulting services in Abu Dhabi
16-11-2026
Best Ecommerce consulting services in Dubai
14-11-2026





