A recent cyberattack affecting 178 organisations raises an important question for UK businesses: if your customers are exposed to malicious code through a trusted supplier, could your company still be held responsible?
Most businesses understand that cybercriminals can steal information, disrupt operations and cause significant financial losses. But what happens when an attack doesn't originate within your own systems?
What happens when the vulnerability belongs to a supplier, the malicious code is delivered through a service you trust, and your customers are the ones exposed?
The answer is more complicated than simply deciding who was hacked.
Your business may not be responsible for the attack itself, but it could still face consequences if it failed to take reasonable steps to protect the people affected.
A Cyberattack That Reached 178 Organisations
On 16 November 2026, cybersecurity researchers uncovered a supply-chain attack involving Optimizely, a platform used by businesses to test, personalise and optimise their websites.
Researchers identified 188 infected JavaScript files associated with 178 organisations, including major names such as the BBC, CNN, Zoom, IKEA and Salesforce.
The attackers had introduced malicious code into a trusted third-party service. When affected websites loaded that service, visitors could be exposed to code designed to replace cryptocurrency wallet addresses, capture payment information, steal browser data and target vulnerable Apple devices.
Optimizely subsequently confirmed that attackers had exploited a vulnerability in its Experimentation account signup process. The company said it had blocked the vulnerable route, removed the malicious code and taken further security measures.
The incident demonstrates how a vulnerability in one supplier can create risks for customers across many otherwise unrelated organisations.
It also raises an important question.
If someone suffers financial loss or has their information compromised while using your website, does it matter that somebody else introduced the malicious code?
Being the Victim of an Attack Does Not Automatically Remove Responsibility
When a business experiences a cyberattack, the immediate responsibility for the criminal activity lies with the attacker.
However, legal responsibility for protecting personal information is a separate issue.
Under UK data protection law, organisations processing personal data must implement appropriate technical and organisational security measures.
This includes considering risks introduced by third-party suppliers.
For example, a company might use an external provider for its website, customer relationship management system, online forms, analytics or payment processing.
The company may not control every aspect of that supplier's infrastructure. Nevertheless, where it acts as a data controller, it remains responsible for complying with its own data protection obligations.
That doesn't mean the business must prevent every conceivable attack. The law takes a risk-based approach, considering factors such as the sensitivity of the information, the likelihood and severity of potential harm, available security measures and the costs of implementation.
The distinction is important.
A cyberattack does not automatically prove that a business failed in its responsibilities. But the fact that an attack originated with a supplier does not automatically excuse the business either.
Could a Customer Take Legal Action Against Your Business?
Potentially, yes. Consider a hypothetical situation.
A customer visits a company's website to complete a transaction. Unknown to the company, malicious code has been introduced through an external website service.
The customer enters sensitive information, which is subsequently intercepted by an attacker.
The customer suffers financial loss and wants to know who is responsible.
They may be able to pursue compensation if they can establish a valid legal claim.
Under Article 82 of the UK GDPR, an individual who suffers material or non-material damage resulting from an infringement of the regulation may have a right to compensation.
However, compensation is not automatic. The individual must establish the relevant infringement, resulting damage and the necessary connection between them.
The business's security arrangements, supplier oversight and response to the incident could all become relevant.
For example, questions might include:
Did the company understand which external services were operating on its website?
Were suppliers appropriately assessed before being introduced?
Were reasonable technical security measures in place?
Were vulnerabilities and potential security incidents monitored?
Did the organisation respond appropriately when the threat was identified?
The answers could help determine whether the company had taken appropriate precautions.
Importantly, this does not establish that any of the organisations affected by the Optimizely incident are legally liable. That would require a separate assessment of the facts and applicable law.
The Hidden Risks in Everyday Business Software
Most organisations rely on more external technology than they realise.
A typical business might use Microsoft 365 for communication, a cloud-based accounting platform, a CRM, website analytics, online booking software and various plugins.
Each system serves a purpose. Many improve productivity and reduce operational costs.
However, they can also introduce dependencies and security risks that need to be managed.
Consider a website plugin installed several years ago.
It may still be operating in the background, collecting information or loading external scripts, even though nobody within the business remembers why it was introduced.
If that supplier experiences a security incident, the consequences could extend beyond the supplier itself.
This is why cybersecurity should not be viewed solely as protecting company laptops, servers and passwords.
It also involves understanding the technology that your organisation depends upon.
What Are Reasonable Steps to Protect Your Business and Customers?
There is no single security checklist that guarantees protection against every attack.
However, there are practical measures businesses can take to reduce risk and demonstrate a considered approach to cybersecurity.
1. Understand your technology and suppliers
Maintain an accurate record of the systems, services, integrations and third-party applications your business uses.
For websites, this should include externally loaded scripts, plugins and services that can interact with customer information.
2. Review supplier security
Before adopting a new service, consider the supplier's security practices, access requirements, data handling arrangements and incident response processes.
Review existing suppliers periodically, particularly those handling sensitive information.
3. Control access and permissions
Limit who can install software, modify website code, introduce integrations or access sensitive business information.
Apply appropriate access controls and multifactor authentication wherever possible.
4. Monitor and maintain systems
Keep supported software updated, review vulnerabilities and use appropriate monitoring to identify suspicious activity.
For websites, additional protections such as Content Security Policy and third-party script monitoring may help detect or restrict malicious behaviour.
5. Prepare for incidents before they happen
Have a documented plan covering how the business will identify, investigate, contain and recover from security incidents.
Where personal data is affected, the plan should also address assessing whether notification to the Information Commissioner's Office or affected individuals is required.
6. Regularly assess your overall IT risk
Cybersecurity risks change as businesses grow, adopt new technology and work with different suppliers.
Regular reviews help identify weaknesses before they become serious problems.
Cybersecurity Is Also About Accountability
The Optimizely incident highlights a difficult reality for modern businesses.
You can choose a reputable supplier, maintain your own systems and invest in cybersecurity, yet still face risks introduced through services outside your direct control.
The objective isn't to eliminate every possible threat. That isn't realistic.
Instead, businesses need to understand their exposure, make informed decisions about the technology they use and take security measures appropriate to the risks.
If an incident occurs, being able to demonstrate those decisions may be just as important as explaining how the attack happened.
Ultimately, customers expect the businesses they deal with to take the protection of their information seriously.
You may not be able to control every cybercriminal or every supplier vulnerability. But you can control how seriously your business manages the risks.
How Sunrise Technologies Can Help
At Sunrise Technologies, we help businesses understand and manage their IT risks through managed IT support, cybersecurity services, compliance guidance and proactive technology management.
Our Business IT Risk Assessment examines five important areas:
Compliance
Technology
Risk management
Operational resilience
Foundational security
The assessment is designed to help organisations identify potential weaknesses, understand their exposure and prioritise practical improvements. Whether your business is concerned about third-party suppliers, outdated systems, cybersecurity threats or business continuity, understanding your current position is an important first step.
How confident are you that your business has taken reasonable steps to protect its systems, information and customers?
This article provides general information about cybersecurity and UK data protection responsibilities. It is not legal advice. Liability for a cyber incident depends on the particular circumstances, applicable duties and evidence.
Sources
Scott Helme, Report URI — World's Largest Brands Infected With Malware Via Optimizely, 16 November 2026.
BleepingComputer — Optimizely hack infected CNN, Fox News, BBC, Salesforce sites with malware, 16 November 2026.
Information Commissioner's Office — Security outcomes and Contracts guidance.
UK GDPR — Articles 32 and 82.