Imagine visiting a familiar website belonging to a bank, technology company, news organization, or retailer. You recognize the company and have no reason to suspect that a third-party script could expose you to malicious software.
That is why the November 16, 2026 attack involving 178 organizations deserves attention.
According to Cybernews and researcher Scott Helme of Report URI, attackers distributed malicious JavaScript through Optimizely Web Experimentation, a service used by major organizations. Websites associated with Zoom, Salesforce, GitLab, IKEA, Equifax, HSBC, CNN, BBC, NPR and Peacock appeared among the affected organizations. The malicious code also included components targeting iPhones and iPads.
Recognizable organizations on the affected list
The Cybernews report identifies familiar names from many industries. In technology, these include Zoom, Salesforce, GitLab, Bitly and Optimizely. Financial names include HSBC, Equifax and Paychex. Retail and consumer brands include IKEA, Mattel and American Eagle.
News and entertainment names include CNN, BBC, Fox News, NPR and Peacock. In transportation and communications, the list includes Alaska Airlines, Hawaiian Airlines and Vodafone Australia. Other recognizable names include Honeywell Home, First Alert, Invisalign, Starbucks Canada, Cinnabon, Change.org, ASPCA and UNICEF USA.
These are examples, not the complete list. Some entries concern specific regional websites or services. Inclusion does not establish that a company’s internal systems were breached or that visitors were successfully infected. Readers can consult Report URI’s full investigation for the detailed inventory.
How did this happen?
Websites often depend on third-party services for analytics, testing, advertising and personalization. Optimizely allows companies to test changes to their websites using JavaScript delivered through its own infrastructure.
Optimizely said an attacker exploited a vulnerability in its Experimentation platform. According to BleepingComputer’s reporting, the weakness involved the Experimentation account signup process. Attackers inserted code into the Project JavaScript field of customer projects, so it arrived through Optimizely’s legitimate delivery infrastructure rather than through separate intrusions into every company’s servers. Optimizely said it fixed the vulnerability, removed injected code, revoked tokens, terminated sessions and secured affected accounts.
Report URI examined 1,611 Optimizely scripts and found 188 compromised scripts associated with 178 organizations.
How long did the attack last?
According to Report URI’s timeline, the first observed Optimizely injection occurred at 04:21 UTC on November 16, 2026. Most infected scripts were cleaned up that evening, and the final known infected script was cleaned by 23:11 UTC. That is an observed window of nearly 19 hours, not proof that every affected site was infected for the entire period. The researchers also observed earlier malicious activity involving other services.
This does not mean that the internal networks of 178 companies were breached. It means visitors could encounter malicious code through a shared third-party dependency. That distinction matters, but it does not make the risk to visitors insignificant.
What was the malware designed to do?
The malicious JavaScript could replace cryptocurrency wallet addresses with attacker-controlled addresses, potentially redirecting payments. It also attempted to collect payment card details from forms, access cookies available to JavaScript and capture screenshots.
Researchers identified approximately $7,150 in cryptocurrency transfers to wallets associated with the malicious infrastructure. Investigators have not established how much, if any, was stolen specifically from visitors to the affected Optimizely websites. The number of payment cards or browser sessions compromised also remains unknown.
Researchers found that the code attempted to load additional exploit components on Apple mobile devices. These are serious capabilities, but a delivered malicious script is not the same thing as a confirmed successful compromise of every visitor.
Why were iPhone and iPad users targeted?
Researchers identified delivery paths for the Coruna and DarkSword exploit kits, targeting vulnerable versions of iOS. Their analysis also identified a separate iOS 26 path that, at the time of investigation, appeared to fingerprint devices rather than demonstrate a successful exploit against that version.
Browser-based exploits can be especially concerning because they may not require someone to install an application or open an attachment. However, researchers have not established how many iPhones or iPads, if any, were successfully compromised in this incident.
Users should install current iOS and browser security updates rather than assume that an Apple device is automatically protected.
What happened after the attack was discovered?
Optimizely acknowledged that an unauthorized party exploited a vulnerability in Experimentation. The company reported fixing the vulnerability, removing injected code, securing affected accounts and adding protections against unauthorized scripts.
Some affected organizations took additional precautions. Reuters reported that Salesforce disabled Optimizely scripts while investigating, and Equifax stopped using the platform and said it found no evidence of compromise to its internal systems.
The full scope of visitor exposure and losses remains uncertain. Reuters and Help Net Security have also covered the incident.
What can website visitors do?
Keep operating systems and browsers updated. If you entered payment information on an affected website during the incident, review the relevant financial account for unusual activity. If you made cryptocurrency transfers, verify that the destination addresses and completed transactions match what you intended.
Remember that an HTTPS connection verifies an encrypted connection to a site; it does not guarantee that every third-party script on that site is safe.
A lesson from maintaining my own websites
This incident reminds me of something that happened while maintaining one of my own websites.
During the early 2000s, when I was developing websites, services offered free JavaScript utilities such as visitor counters. I used an account-based service whose script contacted its website whenever someone visited my page, allowing the counter to be updated.
Years later, Google contacted me to report that the support page of the SSI website had been blocked because of suspicious activity associated with potential malware. SSI stood for Superior Software, Inc., my father’s company. I investigated and discovered that the third-party service’s own website was also blocked. I traced the issue to the script I had installed and learned that the service had changed ownership.
I removed the script, notified Google that I had corrected the problem, and requested another review. Google rescanned my page and removed the block.
I don’t remember the name of the service, and it may no longer exist. I have no evidence that visitors to my website were infected. My experience was not identical to the Optimizely attack, but both incidents illustrate how relying on external code or services can create risks that website owners may not anticipate.
Even a script installed years earlier deserves attention when it continues contacting an outside service.
The larger problem: Trusting third-party code
I have written repeatedly about exposed databases, access control failures and other security problems. This incident demonstrates another side of the same broader issue: the risks created by dependencies that website owners do not fully control.
A company may protect its own servers and still expose visitors to malicious code through a trusted third-party service. Locally hosted scripts can reduce some external dependencies, but local hosting alone does not guarantee safety. Code still needs to be reviewed, updated and protected against unauthorized changes.
Website operators should inventory third-party scripts, restrict who can change them, monitor unexpected behavior and implement carefully configured Content Security Policies (CSPs). A CSP is a set of browser-enforced rules that can restrict which scripts run and where they can send data.
Report URI found that 68 affected organizations had no CSP, 50 had policies that permitted both execution and data exfiltration, and 17 had policies that allowed the payload to run but blocked its outgoing connections. Only 24 had policies restrictive enough to block the malicious payload. These categories do not account for every affected organization, but they demonstrate why simply having a CSP is not enough. Its rules must be appropriately restrictive.
Researchers also identified related malicious-script delivery through other third-party services, including Kissmetrics, StorifyMe and Minute Media. Similar code and infrastructure do not by themselves prove that every incident used the same access method or operator.
The lesson for website administrators and ordinary visitors is straightforward: a familiar name, an HTTPS connection and a trusted vendor are not substitutes for continued security oversight.
The Optimizely incident demonstrates how quickly trust in a shared service can become a route for widespread exposure.
Sources
Cybernews investigation
Report URI technical investigation
Reuters reporting
Help Net Security reporting
Related
Discover more from Jared's Technology podcast network
Subscribe to get the latest posts sent to your email.
When Trusted Websites Deliver Malware: 178 Organizations Caught in an Optimizely Attack
Imagine visiting a familiar website belonging to a bank, technology company, news organization, or retailer. You recognize the company and have no reason to suspect that a third-party script could expose you to malicious software.
That is why the November 16, 2026 attack involving 178 organizations deserves attention.
According to Cybernews and researcher Scott Helme of Report URI, attackers distributed malicious JavaScript through Optimizely Web Experimentation, a service used by major organizations. Websites associated with Zoom, Salesforce, GitLab, IKEA, Equifax, HSBC, CNN, BBC, NPR and Peacock appeared among the affected organizations. The malicious code also included components targeting iPhones and iPads.
Recognizable organizations on the affected list
The Cybernews report identifies familiar names from many industries. In technology, these include Zoom, Salesforce, GitLab, Bitly and Optimizely. Financial names include HSBC, Equifax and Paychex. Retail and consumer brands include IKEA, Mattel and American Eagle.
News and entertainment names include CNN, BBC, Fox News, NPR and Peacock. In transportation and communications, the list includes Alaska Airlines, Hawaiian Airlines and Vodafone Australia. Other recognizable names include Honeywell Home, First Alert, Invisalign, Starbucks Canada, Cinnabon, Change.org, ASPCA and UNICEF USA.
These are examples, not the complete list. Some entries concern specific regional websites or services. Inclusion does not establish that a company’s internal systems were breached or that visitors were successfully infected. Readers can consult Report URI’s full investigation for the detailed inventory.
How did this happen?
Websites often depend on third-party services for analytics, testing, advertising and personalization. Optimizely allows companies to test changes to their websites using JavaScript delivered through its own infrastructure.
Optimizely said an attacker exploited a vulnerability in its Experimentation platform. According to BleepingComputer’s reporting, the weakness involved the Experimentation account signup process. Attackers inserted code into the Project JavaScript field of customer projects, so it arrived through Optimizely’s legitimate delivery infrastructure rather than through separate intrusions into every company’s servers. Optimizely said it fixed the vulnerability, removed injected code, revoked tokens, terminated sessions and secured affected accounts.
Report URI examined 1,611 Optimizely scripts and found 188 compromised scripts associated with 178 organizations.
How long did the attack last?
According to Report URI’s timeline, the first observed Optimizely injection occurred at 04:21 UTC on November 16, 2026. Most infected scripts were cleaned up that evening, and the final known infected script was cleaned by 23:11 UTC. That is an observed window of nearly 19 hours, not proof that every affected site was infected for the entire period. The researchers also observed earlier malicious activity involving other services.
This does not mean that the internal networks of 178 companies were breached. It means visitors could encounter malicious code through a shared third-party dependency. That distinction matters, but it does not make the risk to visitors insignificant.
What was the malware designed to do?
The malicious JavaScript could replace cryptocurrency wallet addresses with attacker-controlled addresses, potentially redirecting payments. It also attempted to collect payment card details from forms, access cookies available to JavaScript and capture screenshots.
Researchers identified approximately $7,150 in cryptocurrency transfers to wallets associated with the malicious infrastructure. Investigators have not established how much, if any, was stolen specifically from visitors to the affected Optimizely websites. The number of payment cards or browser sessions compromised also remains unknown.
Researchers found that the code attempted to load additional exploit components on Apple mobile devices. These are serious capabilities, but a delivered malicious script is not the same thing as a confirmed successful compromise of every visitor.
Why were iPhone and iPad users targeted?
Researchers identified delivery paths for the Coruna and DarkSword exploit kits, targeting vulnerable versions of iOS. Their analysis also identified a separate iOS 26 path that, at the time of investigation, appeared to fingerprint devices rather than demonstrate a successful exploit against that version.
Browser-based exploits can be especially concerning because they may not require someone to install an application or open an attachment. However, researchers have not established how many iPhones or iPads, if any, were successfully compromised in this incident.
Users should install current iOS and browser security updates rather than assume that an Apple device is automatically protected.
What happened after the attack was discovered?
Optimizely acknowledged that an unauthorized party exploited a vulnerability in Experimentation. The company reported fixing the vulnerability, removing injected code, securing affected accounts and adding protections against unauthorized scripts.
Some affected organizations took additional precautions. Reuters reported that Salesforce disabled Optimizely scripts while investigating, and Equifax stopped using the platform and said it found no evidence of compromise to its internal systems.
The full scope of visitor exposure and losses remains uncertain. Reuters and Help Net Security have also covered the incident.
What can website visitors do?
Keep operating systems and browsers updated. If you entered payment information on an affected website during the incident, review the relevant financial account for unusual activity. If you made cryptocurrency transfers, verify that the destination addresses and completed transactions match what you intended.
Remember that an HTTPS connection verifies an encrypted connection to a site; it does not guarantee that every third-party script on that site is safe.
A lesson from maintaining my own websites
This incident reminds me of something that happened while maintaining one of my own websites.
During the early 2000s, when I was developing websites, services offered free JavaScript utilities such as visitor counters. I used an account-based service whose script contacted its website whenever someone visited my page, allowing the counter to be updated.
Years later, Google contacted me to report that the support page of the SSI website had been blocked because of suspicious activity associated with potential malware. SSI stood for Superior Software, Inc., my father’s company. I investigated and discovered that the third-party service’s own website was also blocked. I traced the issue to the script I had installed and learned that the service had changed ownership.
I removed the script, notified Google that I had corrected the problem, and requested another review. Google rescanned my page and removed the block.
I don’t remember the name of the service, and it may no longer exist. I have no evidence that visitors to my website were infected. My experience was not identical to the Optimizely attack, but both incidents illustrate how relying on external code or services can create risks that website owners may not anticipate.
Even a script installed years earlier deserves attention when it continues contacting an outside service.
The larger problem: Trusting third-party code
I have written repeatedly about exposed databases, access control failures and other security problems. This incident demonstrates another side of the same broader issue: the risks created by dependencies that website owners do not fully control.
A company may protect its own servers and still expose visitors to malicious code through a trusted third-party service. Locally hosted scripts can reduce some external dependencies, but local hosting alone does not guarantee safety. Code still needs to be reviewed, updated and protected against unauthorized changes.
Website operators should inventory third-party scripts, restrict who can change them, monitor unexpected behavior and implement carefully configured Content Security Policies (CSPs). A CSP is a set of browser-enforced rules that can restrict which scripts run and where they can send data.
Report URI found that 68 affected organizations had no CSP, 50 had policies that permitted both execution and data exfiltration, and 17 had policies that allowed the payload to run but blocked its outgoing connections. Only 24 had policies restrictive enough to block the malicious payload. These categories do not account for every affected organization, but they demonstrate why simply having a CSP is not enough. Its rules must be appropriately restrictive.
Researchers also identified related malicious-script delivery through other third-party services, including Kissmetrics, StorifyMe and Minute Media. Similar code and infrastructure do not by themselves prove that every incident used the same access method or operator.
The lesson for website administrators and ordinary visitors is straightforward: a familiar name, an HTTPS connection and a trusted vendor are not substitutes for continued security oversight.
The Optimizely incident demonstrates how quickly trust in a shared service can become a route for widespread exposure.
Sources
Cybernews investigation
Report URI technical investigation
Reuters reporting
Help Net Security reporting
Share this:
Like this:
Related
Discover more from Jared's Technology podcast network
Subscribe to get the latest posts sent to your email.
Published in article commentary