Hive Manila

One script, 178 websites: what the Optimizely attack means for your website

Malware reached 178 organizations' websites through one trusted tool. What happened, what it means for your website, and a free check for your own.

Online store owner looking closely at her laptop with concern

On November 16, visitors to the websites of 178 organizations, including the BBC, CNN, Zoom, IKEA and HSBC, were served malicious code. None of those websites were broken into. The code came in through Optimizely, a testing tool they all load on their pages.

Most business websites in the Philippines don’t use Optimizely. But many of them load outside code the same way, through chat windows, plugins, store apps and ad pixels. That is the part worth understanding.

The short version, in 35 seconds.

What happened

Optimizely helps companies test different versions of their web pages. To use it, a site adds a small script from Optimizely’s servers to every page.

Attackers found a flaw in the way new Optimizely accounts were created and used it to add their own code to some customers’ projects (BleepingComputer). From there, every visitor to those sites downloaded it automatically. Nobody had to click anything.

The code could:

  • capture card numbers, expiry dates and security codes typed into forms
  • swap cryptocurrency wallet addresses on the page for the attackers’ own
  • collect cookies, page addresses and screenshots
  • try to break into older iPhones and iPads

Security researcher Scott Helme of Report URI spotted it the same day. His team checked 1,611 Optimizely scripts and found the malicious code in 188 of them, belonging to 178 organizations. Optimizely closed the flaw, removed the code and reset the affected accounts. Within the day, all but one of the infected files had been cleaned.

Why big companies didn’t catch it

These are companies with security teams. So why did it work?

Because the code arrived from a place they had already approved. Many large sites use a Content Security Policy, a rule set that tells the browser which outside code is allowed to run. The sites with a policy had already approved Optimizely, so the browser treated the bad code as normal.

Report URI checked 256 of the affected sites. 68 had no policy at all, and only 24 had one strict enough to block the attack (cside). A policy helps, but only when it limits what trusted tools can do, not just where they come from.

Your website works the same way

This isn’t only an online store problem. Plenty of regular business websites run a chat window in the corner, and we had one on our old site too. Add a booking widget, a Facebook or TikTok pixel, Google Analytics, and on a store, review apps and discount pop-ups, plus a few plugins someone installed once and forgot about.

Every one of those loads code from someone else’s server onto your pages, including your contact forms and checkout. If any one of them is compromised, your customers see the result on your site, under your name.

We run outside scripts too. Our own site loads Google Analytics and the Meta Pixel, and we wrote about how those two slowed our launch. Nobody can avoid outside code completely. The goal is to know what is there and keep it to what you actually use.

Check your site now

We built a quick checker for this. It loads your homepage the way a visitor’s browser does and tells you what outside code it runs, whether the basic security settings are on, and what to fix first. It only looks at what any visitor can see. Nothing is tested or changed on your site.

What to check this week

  1. List what your site loads. Use the checker above, or run your homepage through PageSpeed Insights and look at the third-party section.
  2. Remove what you don’t use. Old pop-ups, trial apps, a second analytics tool. Each one you remove is one less thing that can go wrong.
  3. Check who can add code. This attack started with account access. Look at who has admin access to your website, your tag manager and each app. Remove people who left.
  4. Keep apps and plugins updated. Most fixes reach you through updates. A plugin that hasn’t been updated in a year is worth replacing.
  5. Ask about a Content Security Policy. If you have a developer, ask whether your site has one. They can start in “report-only” mode, which only watches and reports, so nothing breaks while you learn what your site really loads.

If you visited one of the affected sites

If you bought something or logged in on a big brand’s website on November 16, check your card statements and tell your bank about anything you don’t recognize. If you use an iPhone or iPad, install the latest update.

Where this leaves smaller businesses

You don’t need a security team to lower your risk. Most of it is housekeeping: fewer apps, fewer people with admin access, regular updates. It is not glamorous, and it is easy to put off when sales are the priority.

If you’d rather not keep track of it yourself, our care plans cover updates, speed, security and backups every month. If your site already feels slow or messy and you’re not sure what’s running on it, a Project Rescue diagnosis starts by listing exactly that. Or send us your brief and we’ll tell you what we’d look at first.

Common questions

How do I check if my website has been hacked?

Look for pages, links or redirects you did not add, new admin users, and warnings in Google Search Console. A free scan can catch known problems, but a person checking the scripts and logins is more reliable.

Can a third-party script hack my website?

Yes. Any script your site loads from another company runs with the same access as your own code. If that company is breached, your visitors can be affected even if your own site was never touched.

How often should I update my website?

Check for updates at least monthly, and apply security updates as soon as they come out. Remove plugins and scripts you no longer use, since each one is something that can break or be attacked.

Get the Sunday read

One short email a week with our newest insights and case studies. Sunday, 8 AM Manila time.

Want someone watching your site every month?

A short brief, then a written proposal within 1 working day. We talk once the work needs it.