Skip to content

Cybersecurity Insights

178 Websites Hit by Cyberattack: What Businesses Should Know About Website Security

Posted in Blog, News

178 Websites Hit by Cyberattack: What Businesses Should Know

Picture yourself visiting a bank, retailer, or popular tech company’s website. You know the brand, trust the business, and feel safe entering your payment details or logging in.

But what if the website was sending harmful code to your computer, and the company didn’t even know?

That concern drove a November 2026 cyberattack involving websites associated with 178 organizations, including well-known brands such as Zoom, CNN, BBC, HSBC, IKEA, Salesforce, Equifax, and GitLab.

The attackers didn’t break into each company’s network. Instead, they found a weakness in a third-party platform called Optimizely and used it to add harmful code to websites that depended on the service.

Researchers found code meant to steal payment details, gather browser data, redirect cryptocurrency payments, and target some older Apple devices.

It’s still unclear how many visitors were affected or what the financial impact is. Optimizely confirmed the issue, fixed it, and removed the harmful code.

The main takeaway for businesses is this: Your website can put customers at risk because of software and services you don’t directly control.

How Did the Attack Work?

Most business websites use outside services for things like analytics, customer chat, ads, payment processing, and marketing tools.

For example, Optimizely offers software that lets companies test different versions of their websites. A business might use it to see if a blue purchase button gets more clicks than a green one.

To do this, the website loads code from Optimizely into the visitor’s browser.

This code is called JavaScript. It helps websites show information, respond to clicks, process forms, and connect to other services.

The problem began when attackers found a weakness in Optimizely’s signup process. They used it to add harmful JavaScript to customer projects, so websites using the service could pass that code to visitors.

Security researchers found 188 infected scripts on websites linked to 178 organizations.

That number matters, but it doesn’t mean hackers broke into each company’s network. Instead, they used one shared service to reach visitors on many websites.

Here’s an example: A company hires a contractor to maintain its equipment. The contractor is trusted and allowed in the building. If someone takes over the contractor’s equipment, they could cause problems inside, even though the company never gave them a key.

This is why third-party website services can be a security risk. Your business might trust the service, but it can still be compromised.

What Could the Malicious Code Do?

The code found in this incident was made to steal information and mess with what happens in a visitor’s browser.

Here are some examples of what researchers discovered.

Stealing payment card information

Some of the harmful code was made to capture credit card details entered on affected websites.

This kind of attack is called digital skimming. It’s like having a hidden camera near a checkout counter. The customer makes a normal purchase, but someone secretly records the payment details.

The same thing can happen online. A website might look normal, but harmful code quietly collects information entered into a payment form.

For businesses that take online payments, this can cause financial, legal, regulatory, and reputation problems.

Changing cryptocurrency payment addresses

Researchers also found code meant to swap out cryptocurrency wallet addresses.

For example, a customer might copy a real wallet address from an invoice and paste it into a payment. Harmful code could swap that address for one controlled by an attacker.

The customer thinks the payment is going to the right person, but the money actually goes somewhere else.

It’s like someone secretly changing the mailing address on a check before it leaves your office. The payment seems fine, but it never gets to the right place.

Collecting browser information

The code was also made to collect browser cookies and take screenshots.

Cookies are small bits of information websites use to remember visitors and keep them logged in. If attackers get certain session info, they might access accounts without the usual login steps.

Screenshots can also reveal information shown on a visitor’s screen.

Researchers also found signs of attacks aimed at some older iPhones and iPads.

It’s important to know that finding harmful code doesn’t mean every visitor had information stolen or that every attack worked.

Why Third-Party Website Tools Deserve More Attention

Many businesses focus on protecting their website servers, employee computers, and internal networks. These are important steps, but they don’t cover every risk.

Think about how many outside services a typical business website might use:

  • Google Analytics or other visitor tracking tools.
  • Marketing and advertising platforms.
  • Customer chat and support services.
  • Payment processing integrations.
  • Website testing and personalization tools.
  • Tag management systems.
  • Outside libraries and website plugins.

Each service may add code to the visitor’s browser.

The more services a website uses, the more outside connections a business needs to watch and understand.

Imagine a restaurant that keeps its kitchen spotless but buys ingredients from different suppliers. The restaurant can keep its equipment clean and train staff well, but it still relies on those suppliers for safe ingredients.

Website security is similar. A company can protect its own systems well but still have issues if an outside service sends harmful code to its customers.

That’s why reviewing vendors should go beyond just asking if they have a security policy or do yearly penetration tests. Businesses need to know what each service can access, what data it handles, and what could happen if the provider is compromised.

What Can Businesses Do to Reduce the Risk?

Businesses don’t have to remove every outside service from their websites. Many of these tools are helpful and support daily operations.

However, companies should know what they’re using and have a plan to handle problems.

Here are six practical steps to consider.

  1. Know what scripts your website uses.

Start by listing every outside service that adds code to your website. This includes analytics, ads, chat, payment tools, and marketing integrations.

Ask yourself: Do we still need this service?

Old plugins and unused scripts can add unnecessary risk. If your business doesn’t use a tool anymore, remove it.

  1. Limit what outside services can access.

Not every website tool needs access to all your information.

A marketing tool might need to track website traffic, but it probably doesn’t need access to payment info. A chat feature may need to show a support window, but it shouldn’t have access to everything on the page.

Only give each service the access it needs to work.

  1. Use website security controls.

Tools like Content Security Policy (CSP) help website owners control which sources can load scripts.

It’s like having a guest list. Instead of letting anyone into a building, you choose who can enter.

Another option is Subresource Integrity (SRI), which lets a browser check if certain outside files have changed. It works for some scripts, but not every website integration.

These controls can help, but they are not a complete solution. A trusted service that gets compromised may still deliver harmful code.

  1. Watch for unexpected changes.

Businesses should have a way to spot unusual changes to the scripts their websites use.

For example, if a payment page suddenly talks to an unfamiliar website, someone should check it out.

It’s like checking who comes into your office and making sure no one changes equipment or security steps without permission.

  1. Have a plan if a vendor is compromised.

What if a company that provides one of your website tools reports a security incident?

Can you quickly turn off the service? Who decides that? Can your website keep running without it? How will you find out if customer information was exposed?

It’s much easier to answer these questions before something happens.

  1. Review payment-page security.

Businesses that take credit cards online should pay close attention to the scripts running on their payment pages.

PCI DSS 4.x sets rules for payment-page scripts and for spotting unauthorized changes. The exact rules that apply depend on your company’s payment setup.

Businesses need to know which rules apply to them and check if their current security measures are enough.

Why Website Penetration Testing Is Important

A website penetration test checks for security gaps that attackers might use to steal information, disrupt your business, or put your customers at risk.

A thorough assessment goes beyond checking if your website works. It also reviews how your site uses outside services, payment tools, user data, and security features.

For example, a tester might check if sensitive data is exposed to third-party scripts, if your website’s security settings are set up correctly, and if attackers could change key website functions.

It’s important to know what an assessment covers. Testing your website doesn’t automatically check the internal systems of every outside provider you use. Those might need their own reviews.

At Tanner Security, our Web Application Penetration Testing helps businesses find weaknesses in their applications and see where they can improve.

If your business takes online payments, our PCI DSS Consulting Services and PCI DSS 4.0.1 Compliance Consulting can help you review your payment security and understand the rules that apply.

Know What Your Website Depends On

The Optimizely incident shows that keeping your business website safe means more than just protecting your own servers and computers.

Each outside service, plugin, or script your website uses adds another connection you need to understand.

You don’t have to stop using third-party tools. But you should know what they do, what information they can access, and what you can do if one of them is compromised.

Your website is often the front door to your business. Be sure you know who else has a key.

If you want an independent review of your website’s security, contact Tanner Security at 866-851-8018 or visit our contact page.

Schedule a Call

Name*
Please let us know what's on your mind. Have a question for us? Ask away.

178 Websites Hit by Cyberattack FAQ

Attackers exploited a weakness in Optimizely’s website experimentation platform and used it to add malicious JavaScript to customer projects. Researchers identified 188 infected scripts across websites associated with 178 organizations.

No. The incident involved malicious code delivered through a shared third-party website service. This does not mean attackers independently broke into the internal networks of all 178 companies.

It happens when attackers compromise a software provider, website tool, or other outside service that a business relies on. They use that trusted connection to create security problems for the provider’s customers.

It is code that a website loads from an outside provider. Common examples include analytics tools, chat features, advertising services, and website testing platforms.

Yes. Depending on the website and its security controls, malicious code running in a visitor’s browser may be able to capture information entered into payment forms.

Digital skimming occurs when malicious code on a website captures sensitive information visitors enter. It is similar to using a hidden device to collect payment card details at a physical checkout counter.

Depending on how a website is built and what access a script receives, it may be able to interact with information displayed or entered on the page. Businesses should limit that access wherever possible.

Yes. A compromised third-party script can deliver malicious code to website visitors even when the company’s internal network and web servers have not been directly breached.

A web application penetration test can examine how a website uses outside scripts and whether those connections create security weaknesses. It does not automatically include a full assessment of the outside provider’s own systems.

Yes. PCI DSS 4.x includes requirements for managing and monitoring scripts used on payment pages. The specific requirements depend on the company’s payment environment.

Businesses should maintain an ongoing inventory and review scripts whenever they add a new service, change an existing integration, redesign a website, or learn that a provider has experienced a security incident.

The business should identify whether it uses the affected service, review the provider’s security notice, determine whether malicious code reached its website, and disable or remove affected components when appropriate. It should also investigate potential customer exposure and determine whether notification requirements apply.