How Were 178 Websites Hacked? Who Was Behind the Optimizely Cyberattack and When Did It Happen?

How did hackers compromise 178 organisations, who was affected and when did the Optimizely cyberattack happen? Get the timeline, affected websites and latest security update.

Published on by

How Were 178 Websites Hacked? Who Was Behind the Optimizely Cyberattack and When Did It Happen?

A cyberattack involving Optimizely exposed visitors of websites associated with 178 organisations to malicious code, including websites linked to CNN, BBC, Zoom, Salesforce, IKEA and HSBC.

The attackers exploited a vulnerability in Optimizely Web Experimentation, a platform businesses use to test website designs, personalise content and measure visitor behaviour. They inserted malicious JavaScript into customer projects, allowing the code to reach visitors through websites that relied on the service.

The malware was designed to steal cryptocurrency, capture payment card details, collect browser cookies and screenshots, and deliver exploit kits targeting vulnerable iPhones and iPads.

The incident came to public attention on November 16 and 17, 2026, after cybersecurity researchers identified the malicious scripts and Optimizely confirmed the security incident.

But how did the hackers compromise these websites? Who was responsible? Which organisations were affected? And has the vulnerability been fixed?

Here is what is known about the cyberattack.

1. How Were 178 Websites Hacked?

The attackers exploited a vulnerability in Optimizely Web Experimentation, a platform companies use to run website experiments and improve visitor experiences.

Websites using the service load JavaScript snippets from Optimizely's servers. These snippets allow businesses to test different website layouts, personalise content and measure how visitors interact with their pages.

According to cybersecurity researcher Scott Helme of Report URI, the attackers inserted malicious JavaScript into the Project JavaScript section of affected customer projects.

This section allows businesses to add custom JavaScript to their website experiments.

Instead of breaking into all 178 organisations individually, the attackers abused a shared third-party service to distribute their malicious code through websites already using Optimizely.

This is an example of a software supply-chain attack.

Because the injected scripts continued loading through Optimizely's legitimate content delivery network, visitors' browsers could receive the malicious code from a source they would normally trust.

What Did the Malicious Code Do?

Researchers identified several malicious functions within the injected JavaScript.

Cryptocurrency theft: The malware attempted to replace legitimate cryptocurrency wallet addresses with addresses controlled by the attackers. This could redirect payments to criminal wallets.

Payment card skimming: The malicious code attempted to capture payment card information, including card numbers, expiration dates and security codes entered into affected website forms.

Cookie theft: The scripts attempted to collect browser cookies, which can contain sensitive session information.

Screenshot collection: The malware could capture screenshots of webpages visited by users.

iPhone and iPad targeting: Researchers identified attempts to deliver Coruna and DarkSword iOS exploit kits to vulnerable Apple devices.

The attack was particularly concerning because visitors could encounter malicious code while browsing websites they normally considered trustworthy.

2. Who Was Behind the Optimizely Cyberattack?

The attack involved an unauthorised party exploiting a vulnerability in Optimizely's Experimentation platform.

However, the identity of the attacker had not been publicly verified as of November 17, 2026.

Cybersecurity researchers identified the malicious scripts and investigated the infrastructure used to distribute them. They also traced cryptocurrency transactions associated with attacker-controlled wallets.

These findings do not establish the real-world identity, nationality or organisational affiliation of the person responsible.

It would therefore be inaccurate to attribute the incident to a particular country or hacking group without additional evidence.

Who Discovered the Cyberattack?

Security researcher Scott Helme of Report URI identified the malicious JavaScript and investigated its distribution across websites using Optimizely.

His investigation examined 1,611 Optimizely scripts and identified 188 malicious scripts associated with 178 organisations.

Other cybersecurity researchers and security firms also investigated the incident, including Hudson Rock and StepSecurity.

Their findings helped explain how the malicious scripts were distributed and what they were designed to do.

Who Was Affected by the Cyberattack?

Researchers identified websites associated with 178 organisations across several industries, including technology, banking, retail, media, aviation and telecommunications.

Some of the reported organisations included:

OrganisationIndustry
CNNNews and media
BBCBroadcasting and news
ZoomVideo communications
SalesforceBusiness software
IKEARetail
HSBCBanking
EquifaxCredit reporting
GitLabSoftware development
LedgerCryptocurrency security
Air France-KLMAviation
VodafoneTelecommunications
PeacockStreaming and entertainment
StarbucksFood and beverage
ASOSOnline retail

The identification of these organisations does not mean hackers independently breached all their internal networks or databases.

The investigation concerned malicious scripts distributed through affected Optimizely projects. It did not establish that every visitor to every listed website was successfully compromised.

3. When Did the Optimizely Cyberattack Happen?

The malicious JavaScript was served to visitors of affected organisations on November 16, 2026.

Report URI identified the incident and investigated the compromised scripts. Optimizely subsequently confirmed that an unauthorised party had exploited a vulnerability in its Experimentation platform.

The incident received wider media attention on November 17, 2026.

The following timeline summarises the major developments:

DateDevelopment
November 16, 2026Malicious JavaScript was served to visitors through affected Optimizely projects
November 16, 2026Report URI identified and investigated the malicious scripts
November 16, 2026Researchers reported cryptocurrency transactions reaching attacker-controlled wallets
November 16, 2026Remediation efforts removed most of the identified malicious scripts
November 17, 2026Optimizely confirmed the security incident and announced remediation
November 17, 2026Reports brought the incident to wider public attention

The November 16 date refers to the observed malicious activity. It does not necessarily establish the exact moment the attacker first gained access to the affected projects.

When Did Optimizely Fix the Vulnerability?

Optimizely confirmed that it had fixed the vulnerability and removed injected code from affected customer projects.

The company also said it had taken steps to secure affected user accounts and introduced additional protections to prevent unauthorised code from being delivered.

Report URI reported that most of the identified malicious scripts had been removed by the evening of November 16.

However, removing malicious code does not automatically reverse information that may already have been stolen.

4. Was CNN Hacked?

CNN was among the organisations identified in the investigation of the malicious Optimizely scripts.

However, this does not establish that hackers penetrated CNN's internal network, editorial systems or databases.

The reported incident involved malicious JavaScript distributed through a third-party website experimentation platform.

This distinction matters because a website can serve malicious external code without its entire internal infrastructure being breached.

5. Was BBC Hacked?

The BBC was also among the organisations associated with affected Optimizely scripts.

The discovery does not establish that hackers gained access to the BBC's internal systems or databases.

The same distinction applies to Zoom, Salesforce, IKEA and the other organisations identified by researchers.

The investigation focused on malicious code delivered through affected website scripts, not confirmed breaches of every company's internal network.

6. Were iPhone Users Targeted?

Yes. Researchers identified attempts to deliver Coruna and DarkSword exploit kits targeting Apple iPhones and iPads.

These exploit kits were designed to target vulnerable versions of Apple's iOS operating system.

However, the presence of an exploit kit in the malicious code does not prove that every visitor using an iPhone was infected.

The number of devices successfully compromised through this campaign had not been established in the public reporting available on November 17, 2026.

Apple device users should install available security updates and avoid ignoring software update notifications.

7. Was Cryptocurrency Actually Stolen?

Researchers reported cryptocurrency transactions reaching wallets associated with the attackers.

StepSecurity and other investigators reported approximately $7,040 in cryptocurrency reaching attacker-controlled wallets during the incident.

The malicious JavaScript was designed to replace legitimate wallet addresses with attacker-controlled addresses.

For example, someone intending to send cryptocurrency to a legitimate recipient could unknowingly send it to a different address if the malware replaced the copied wallet address.

Cryptocurrency transactions are generally difficult to reverse, making this type of attack particularly dangerous.

The reported cryptocurrency amount does not represent the total possible financial impact of payment card theft, cookie collection or other malicious activity.

8. Is the Optimizely Cyberattack Still Happening?

Optimizely said it had fixed the vulnerability, removed injected code from affected projects and introduced additional security protections.

Report URI also reported that most of the identified malicious scripts had been cleaned up by the evening of November 16.

However, remediation does not necessarily mean every possible consequence has been resolved.

Affected organisations may still need to investigate potential information exposure, suspicious account activity and customer impact.

Visitors should continue monitoring sensitive accounts and financial transactions, particularly if they entered payment information or conducted cryptocurrency transactions on affected websites during the exposure period.

9. What Should You Do If You Visited an Affected Website?

Visiting one of the affected websites does not automatically mean your phone or computer was infected.

The level of risk depends on the malicious code delivered, the page visited, the device being used and whether you performed an activity targeted by the malware.

If you visited an affected website, consider taking these precautions:

  1. Update your devices: Install the latest available security updates for your iPhone, iPad, computer and browser.
  2. Check cryptocurrency transactions: Review recent transfers and verify that wallet addresses match the intended recipients.
  3. Monitor payment cards: Look for unfamiliar transactions on bank statements and card accounts.
  4. Review important accounts: Check for suspicious login sessions, unfamiliar devices or unexpected account changes.
  5. Change compromised passwords: If you identify suspicious activity, change the affected passwords using the official websites or applications.
  6. Enable multi-factor authentication: Add another layer of protection to important accounts.
  7. Contact your financial provider: Report unauthorised transactions through your bank or cryptocurrency provider's official support channel.

Never share your cryptocurrency recovery phrase or private keys with anyone claiming to help recover stolen funds.

Frequently Asked Questions

How were 178 websites hacked?

Hackers exploited a vulnerability in Optimizely Web Experimentation and inserted malicious JavaScript into customer projects. Websites loading the affected scripts could then deliver the malicious code to visitors.

Who hacked CNN and BBC?

The identity of the attacker responsible for the Optimizely incident had not been publicly verified as of November 17, 2026. CNN and BBC were among the organisations associated with affected scripts.

Who was affected by the Optimizely cyberattack?

Researchers identified 178 organisations, including CNN, BBC, Zoom, Salesforce, IKEA, HSBC, Equifax and GitLab.

When did the Optimizely cyberattack happen?

Malicious JavaScript was served to visitors of affected organisations on November 16, 2026. Optimizely confirmed the security incident on November 17.

Was CNN's internal network hacked?

The investigation identified CNN among organisations associated with malicious Optimizely scripts. It did not establish that CNN's internal network or databases were breached.

Was the BBC website infected with malware?

The BBC was among the organisations associated with affected Optimizely scripts. This does not establish that every BBC visitor was infected.

Has Optimizely fixed the cyberattack?

Optimizely said it fixed the vulnerability, removed injected code from affected projects, secured affected accounts and introduced additional protections.

Were iPhones infected by the cyberattack?

The malicious scripts attempted to deliver Coruna and DarkSword exploit kits targeting vulnerable Apple devices. The number of devices successfully compromised was not established.

How much cryptocurrency did hackers steal?

Researchers reported approximately $7,040 reaching attacker-controlled wallets. This figure does not account for possible losses involving payment cards or other information.

Final Takeaway

The Optimizely cyberattack happened because an unauthorised attacker exploited a vulnerability in a trusted website experimentation platform and inserted malicious JavaScript into customer projects.

Researchers identified 188 malicious scripts associated with 178 organisations, including CNN, BBC, Zoom, Salesforce, IKEA and HSBC.

The incident demonstrated how compromising a single third-party service can expose visitors across numerous otherwise trusted websites.

Although Optimizely confirmed that it had fixed the vulnerability and removed the injected code, the total number of visitors whose information or devices were successfully compromised remained unknown.

Read our earlier report: Cyberattack Hits 178 Organisations: CNN, BBC and Zoom Visitors Targeted by Malware

Sources and Further Reading

Related Articles

Video Editorial Context: Watch and review key insights and reporting regarding Malware Attack Hits 178 Major Organizations Worldwide | NewsX World. This verified video provides essential context and primary source footage supporting our coverage.

Videos in this article

Watch editorial video coverage: How Were 178 Websites Hacked? Who Was Behind the Optimizely Cyberattack and When Did It Happen?

More on this Story & Related In-Depth Reports

technology

United Airlines Outage: Why Flights Were Delayed, What Happened and Latest Update

United Airlines Outage: Why Flights Were Delayed, What Happened and Latest Update United Airlines experienced a widespre...

technology

Propranolol Extended-Release Capsules Recall: Lot Number, Metal Contamination Risk and What to Do

Propranolol Extended Release Capsules Recall: Lot Number, Metal Contamination Risk and What to Do Propranolol extended r...

technology

Is the NSA Down? What Happened to NSA Net and Its Classified Communications Network?

Is the NSA Down? What Happened to NSA Net and Its Classified Communications Network? Is the US National Security Agency ...

technology

Cyberattack Hits 178 Organisations: CNN, BBC and Zoom Visitors Targeted by Malware

Cyberattack Hits 178 Organisations: CNN, BBC and Zoom Visitors Targeted by Malware A major cybersecurity incident has af...