
On November 16, 2026, hundreds of company websites exposed their visitors to malicious code, even though the companies’ own sites had not been hacked.
The code was hidden in a tool that companies use to test and improve their websites. The tool is called Optimizely Web.
The attack began on November 16. In total, 178 organizations were affected. The attackers tried to steal bank card details and cryptocurrency.
The main point is simple: even if your website is secure, its visitors can be put at risk by another company whose service you use.
How the attack worked
Optimizely Web is a tool that companies use to test different versions of their website. For example, it shows which button people like more. To make it work, the company places a small piece of code on its page. This snippet downloads the rest of the code from Optimizely servers every time, from the address cdn.optimizely.com.
The tool has a field called Project JavaScript. The customer can enter their code there, and it runs on every page. The attacker entered a small “loader” in this field. It downloaded a script called track.js from the site 1688360.cc, and this script was already doing harm.
The main reason the attack succeeded: the code came from a trusted address, cdn.optimizely.com. Browsers and many security systems trust it, so nothing raised suspicion.
Think of it this way: imagine a courier who brings you parcels every day from a familiar warehouse. If someone at the warehouse slips something dangerous into a parcel, you won’t question it, because the parcel comes from the usual source.
Optimizely confirmed that there was a vulnerability in its Experimentation product. The company stated that the route for the attack has been closed, the malicious code has been removed, and customers have been informed.
What the malicious code did to visitors
Once this code was loaded on a page, it quietly did several things:
- It changed cryptocurrency addresses. If a person wanted to pay with cryptocurrency and entered an address, the code swapped it for the attacker’s address. The money went into the wrong hands.
- It read bank card details. When a person entered their card number on a payment page, the code copied it and sent it to the attackers. This started around 13:43 UTC.
- It read cookies. Cookies are small files that allow a website to remember that you are logged in. Some cookies were not protected against scripts (the HttpOnly setting was missing), so the code could read them.
- It took screenshots. The code could capture what the person sees on the screen.
- It looked for weaknesses in iPhones. The code tried to exploit vulnerabilities on iOS devices, using tools called Coruna and DarkSword.
Important: the visitor saw nothing. The page looked and worked as usual.
How big the attack was
Report URI’s security monitoring company compiled 1,611 different Optimizely code snippets. Of these, 188 were infected. These snippets belonged to 178 organizations. The actual number may be higher, because only the snippets that could be found were checked.
The list included well-known brands such as Zoom, BBC, CNN, Salesforce, GitLab, IKEA and HSBC. It has not been confirmed for all of them that the malicious code actually ran there: Reuters could not verify it in every case. Salesforce investigated the changes and, as a precaution, disabled the Optimizely scripts.
By 19:25 UTC, the attackers had stolen approximately $7,040 USD worth of cryptocurrency.
Why some sites were protected and others were not
Security specialists checked 256 websites and looked at their CSP settings. CSP is a set of rules that tells a browser where it may load code from and where it may send data. The results were as follows:
- 68 websites had no CSP at all.
- 50 websites had a CSP, but it allowed both loading the malicious code and sending data to the attacker.
- 17 websites had a CSP that blocked the sending of data.
- 24 websites had a CSP that blocked the loading of the malicious code itself.
The settings called ‘strict-dynamic’ and ‘unsafe-eval’ allowed the attack to get through. The lesson: CSP only helps if it is set up correctly.
What this means for your WordPress website
If you don’t use Optimizely, that doesn’t mean you’re not at risk. The same problem can arise with any external script your page loads from somewhere else. Examples include analytics tools, chat windows, ad pixels, cookie consent tools and some plugins.
Every such script is like a key you have given to someone else. If someone steals that key, your website can become dangerous, even if you have not done anything wrong yourself.
E-shops are at the greatest risk, including WooCommerce websites. People enter their card details there, and that is exactly what attackers want to steal. A single malicious line on the payment page is enough for data to fall into the wrong hands while the shop looks and works as usual.
What to do today, for every website owner
- Make a list of all external scripts on your website: statistics, chat, ads, testing tools.
- Keep only those that are truly necessary. Every extra script is extra risk.
- Process payments on the service provider’s page or in their window, not on your own page where there are many external scripts.
- Check your CSP and do not leave it too loose. Use ‘unsafe-eval’ only if you cannot do without it.
- Set HttpOnly protection on cookies so that scripts cannot read them.
- Update WordPress, plugins and themes. WordPress 7.1.4 was released on 28 October and fixes 22 vulnerabilities.
- Monitor changes on your website. If someone adds a new script, you need to know about it immediately.
If you use Optimizely
- Open the Project JavaScript field and check whether there is any unfamiliar code there.
- Look for references to 1688360.cc. If such a reference is there, your snippet was infected.
- Change your access credentials and check who else has access to the account.
- Contact Optimizely and ask whether your account was affected.
For visitors
If a website looks strange or the payment page behaves unusually, do not enter your card details. Check your bank statement and update the iPhone system on your device.
How EvoEX helps
EvoEX CyberEX is our IT security centre for client websites. If you would like someone to check your WordPress or WooCommerce website and the external scripts used there, write to us: CONTACTS SECTION
Glossary: the hardest words in plain language
- Script (JavaScript): program code that runs in your browser and makes the web page “alive”.
- CDN: a network of servers that quickly delivers files to a page. Optimizely code was delivered from cdn.optimizely.com.
- Malware: a program created to harm people.
- Skimmer: malicious code that reads card details while a person is entering them.
- Cookie: a small file that allows a website to remember that you have logged in.
- CSP: rules that tell a browser where it may load code from.
- Supply chain attack: an attack carried out through a company you trust, rather than directly against your website.
