← Back to Blog

Optimizely Hijack Hit 178 Sites: Audit the Scripts Running on Yours

· 10 min read Optimizely Hijack Hit 178 Sites: Audit the Scripts Running on Yours

Last week, at least 178 widely visited websites served malware exploits to their visitors for about 24 hours. The delivery route wasn't a hole in those sites' own code. It was a script from a vendor they trusted, an A/B testing service called Optimizely, which has since confirmed the breach. The affected sites reportedly included the BBC, CNN, Equifax and Zoom, and the injected code was data-stealing malware.

If you run a small business site, you probably load scripts from other companies too. Analytics, a chat bubble, a review widget, an ad pixel, a booking tool. Each one runs with the same power as your own code, inside your customers' browsers. When one of those vendors has a bad day, you have a bad day, and you may not hear about it for hours.

This isn't a reason to panic or rip out every tool. It's a reason to spend an afternoon finding out what your site actually loads, deleting what you don't need, and writing down who you'd call if a vendor got hit. Most small sites have never done that. The rest of this post walks through how.

What happened

The analysis here comes from Apprised.news desk briefs, specifically the tech and cyber desk's 18 November brief. The original reporting is linked below, so you can check each claim yourself.

  • The incident. Krebs on Security reports that attackers used Optimizely, an A/B testing service, to deliver malware to top websites. Apprised.news's tech desk summarises it as at least 178 top web destinations serving malware exploits over about 24 hours, with the vendor confirming the breach.
  • The vendor's admission. CSO Online reports that Optimizely confirmed a large attack on customer websites that injected stealer malware. CSO Online also describes an authentication hole as part of the story.
  • A name for it. Palo Alto Networks' Unit 42 published a write-up calling it a supply-chain attack it dubs "optimjack".
  • The wider coverage. Cointelegraph also reported the 178-site figure, which matters if you take crypto payments or customer logins.
  • Why it isn't a one-off. Krebs's point, as the desk summarises it, is that few popular sites enforce strict rules about where scripts can load from. The desk's weighted read is that this is most likely a third-party-script weakness many large sites share, and that further vendor-script compromises are likely to surface within weeks. The confirmed facts (178 sites, about 24 hours, a vendor admission) already establish the delivery channel.
  • What's still unknown. Attribution is unresolved. CSO Online says the attack apparently came from China, while the desk's cyber analyst treats that as an unsupported lead. The open item that matters most is whether Optimizely publishes indicators and a root cause. If it was a narrow, one-time credential failure, that's one story. If it's a repeatable technique, it's another.

I'd hold off on any firm conclusion about who did it. For your purposes it doesn't matter. The delivery channel is the lesson.

What it means for a small business

You're exposed if your site loads code from any domain you don't control. That's nearly everyone. The risk isn't that a big vendor is careless. It's that you inherit their worst day with no warning and no control over timing. Three hypothetical examples show what that looks like in dollars and hours.

Maple Street Bakery: count first, then cut

Take a bakery with an online ordering site that loads 6 third-party scripts: Google Analytics, a chat widget, an A/B testing tool, a review widget, a Facebook pixel and a payment form. It takes 400 orders a month at a $38 average ticket, so roughly 13 orders a day on average. Suppose a compromised script steals customer data for 24 hours on a busy day of 60 orders. That's about 60 exposed customers and about $2,280 in transactions to review (60 x $38), before notification costs and chargeback work.

Now do the cheap thing. List the six scripts and ask what each one earns. The A/B testing tool hasn't run an experiment in a year. The review widget was a trial nobody cancelled. Drop those two and you've cut the number of outside parties that can touch your checkout page by a third. You didn't buy anything. You deleted something.

Ridgeline HVAC: get the inventory in writing

A 12-person HVAC company in Ohio has a lead-gen site with 4 scripts. A $300 per month marketing agency added most of them, and the owner can name two. If one of those vendors reported a breach tomorrow, who'd pull the script? Who'd even know?

The fix is an email. Ask the agency for a written list of every script, the vendor, the purpose, who owns each vendor account, and who gets notified if a vendor reports a breach. The result is a one-page inventory and a named contact, instead of "I think our agency handles that." That's worth more than it sounds. An agency that can't produce the list in a week has told you something important too.

Harbor Dental: report first, then enforce

A dental practice uses a hosted booking widget that loads from a vendor domain. A staff member turns on a Content Security Policy (CSP) in report-only mode for 2 weeks. A CSP is a rule your site sends to browsers saying which domains may load scripts. Report-only mode doesn't block anything. It just logs what would have been blocked.

The log shows 11 unexpected domains. Five turn out to be abandoned tags from old campaigns. They get removed. The practice then enforces a policy allowing only the 6 sources it actually approved. A compromised or forgotten tag from a seventh domain now simply won't run in patients' browsers. Two weeks of watching, then a rule that holds.

What to do this week

None of this needs a developer for the first few steps. Do them in order.

  1. List every third-party script on your site. View page source or open your browser's network tab, reload the page, and note each external domain. Look for analytics, A/B testing, chat, ads, review and payment widgets. Check your checkout and booking pages too, not just the home page. The jwatte.com post on your site's invisible supply chain walks through this, and the tag-weight post shows how to see what each tag costs you in speed.
  2. Delete anything nobody uses or can explain. Old A/B tests, abandoned ad pixels and trial widgets are the usual leftovers. Every script you remove is one less vendor who can hurt you.
  3. Ask your agency or developer for a written inventory. Vendor, purpose, and account owner for each script. Use the email template in the kit below.
  4. Turn on a Content Security Policy in report-only mode. Review what it reports for 1 to 2 weeks, then enforce an allowlist of approved script sources. Expect surprises in the report. That's the point. The post on new security audit tools includes a note on a CSP that doesn't block Microsoft Clarity, which is the kind of snag you'll hit.
  5. Use Subresource Integrity where you can. For static scripts a vendor supports it for, SRI makes the browser refuse a file that has changed. Pin or self-host libraries you control instead of loading them live from a CDN. It won't help with scripts that change by design, like A/B testing code, which is part of why those are risky.
  6. Keep payment fields on the processor's hosted page or iframe. Then a rogue script on your own page can't read card numbers typed into a field it can't reach.
  7. Require multi-factor authentication everywhere. That means everyone with admin access to your site, your tag manager and your vendor dashboards. CSO Online describes an authentication hole in this incident, and a stolen vendor-dashboard login is exactly how a script gets swapped.
  8. Write a one-page vendor-compromise plan. Who can pull a script within minutes, how you'd notify customers, and who calls your insurer. The shape is the same as the one in the AI vendor lockout continuity plan.
  9. Check your cyber liability policy. Does it cover third-party vendor incidents and notification costs? Know the claims phone number before you need it.
  10. Watch for Optimizely's published root cause and indicators. If you've ever used Optimizely, ask your agency to confirm whether your account was in scope and to rotate credentials. Don't assume you weren't.

Copy-paste prompts

Each prompt works best if you paste in your real material and tell the AI to flag what it can't determine. Check any answer against your own site before acting.

Use this to triage your script list:

I run a small business website. Below is the page source or a list of external domains it loads. Work only from what I paste. For each domain, tell me what it probably is, whether it is likely a third-party script, and what risk it poses if that vendor were compromised. Format as a table with a keep / remove / ask-vendor column. If you do not recognise a domain, say so plainly instead of guessing.

[paste page source or domain list]

Use this when you're ready to start a CSP:

Write a plain-English Content Security Policy for a small business site that uses these vendors: [list them, e.g. Google Analytics, Stripe, Calendly]. Start in report-only mode, explain each directive, and tell me how to roll it out safely over 2 weeks without breaking checkout. If you are unsure which domains a vendor actually needs, say so and tell me how to find out from the report.

Use this to get your agency moving:

Draft a short, polite email to my web agency asking for a complete inventory of third-party scripts on our site, who owns each vendor account, whether each account uses multi-factor authentication, and how we would be told about a vendor breach. Our site is [URL] and the agency is [name]. Ask for a reply within 7 days.

Use this to build your response plan:

Create a one-page incident response checklist for the case where a vendor script on my website is reported as compromised: first hour, first day, customer notification, evidence to keep, and who to call. My business is [type] with about [number] customers a month. Base it on this list of our scripts and who owns each account: [paste inventory]. Mark any step where you are unsure of the right legal or insurance requirement so I can check it.

Use this if you want the concepts explained before you act:

Explain in simple terms what Subresource Integrity and a Content Security Policy each protect against, and which one gives a small business with no developer the most protection for the least effort. Our site is built on [platform]. If the answer depends on how our platform works, tell me what to check.

Download the kit

The Third-Party Script Audit Kit is a printable markdown file. It has a script inventory worksheet, a guide to finding scripts with your browser, a CSP rollout checklist, an agency email template, a one-page vendor-compromise plan, an insurance review checklist, a rough exposure calculator, and all the prompts above ready to paste.

Fact-check notes and sources

  • Apprised.news tech desk, 18 November 2026: the source of the 178-site, about-24-hours, vendor-confirmed summary, the weighted read, and the unresolved attribution and root-cause questions. Analysis page
  • Krebs on Security: reports that attackers used Optimizely to deliver malware to top websites, and the point that few popular sites enforce strict script-source rules. Article
  • CSO Online: reports Optimizely confirmed a large attack that injected stealer malware, describes an authentication hole, and states the attack apparently came from China (which the desk treats as unsupported). Article
  • Palo Alto Networks Unit 42: write-up of the incident as a supply-chain attack it calls "optimjack". Write-up
  • Cointelegraph: also reported the 178-site malware injection. Article
  • Hypothetical examples: the bakery, HVAC company and dental practice are invented for illustration. The arithmetic (60 orders x $38 = $2,280) is shown above; your own numbers will differ.

Related reading

This post is informational, not legal, financial or security-consulting advice. It draws on AI-written Apprised.news analysis of public reporting; check the linked sources before acting. Mentions of third parties are nominative fair use. No affiliation is implied.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility Statement • Privacy Policy

Last updated: April 2026