One Vendor Script Hit 178 Websites. What Runs on Yours?

Published On
November 17, 2026
Share this post
Emry Networks website script brief: on November 16th, 2026, hijacked Optimizely code ran on the websites of 178 organizations, with 188 of 1,611 checked snippets infected, according to Report URI, and a reminder that PCI DSS 4.0.1 requirements 6.4.3 and 11.6.1 cover payment page scripts

On Monday, November 16th, 2026, visitors to the websites of 178 organizations were served malicious code. None of those websites had to be hacked directly. The code arrived through Optimizely, a website testing and personalization tool the sites already trusted. Researchers at Report URI fetched 1,611 Optimizely snippets and found the code in 188 of them, belonging to 178 organizations, including Zoom, CNN, the BBC and Salesforce. (Report URI, November 16th, 2026)

Optimizely confirmed the incident on its status page: an unauthorized party exploited a vulnerability in its Experimentation product and used it to add malicious JavaScript to some customer projects. The company says it fixed the vulnerability, removed the injected code and secured affected user accounts. (Optimizely status page)

This brief is for owners, practice managers, and office and compliance leads at regulated small businesses: medical and dental practices, law firms, financial advisors, accounting firms and others whose website takes payments, appointment requests or intake forms. You do not need to know JavaScript to act on it. You need to know what your own pages load, and who can change it.

Watch the 60-Second Briefing: Watch our narrated YouTube Short on the Optimizely website script attack, on YouTube (@emrynetworks).

What happened in the Optimizely attack?

Optimizely Web works by having each customer's site load a small file, called a snippet, from Optimizely's delivery network. Each snippet can carry an optional field called Project JavaScript: custom code the customer writes in the Optimizely dashboard, which runs on every page. Report URI found that the attacker wrote its own code into that field in customer projects. The rest of each file was untouched, and it was still served from Optimizely's own domain, which every affected site already trusted.

  • When: Report URI's timeline shows the first Optimizely injection early on November 16th, 2026, and a mass clean-up that evening. By the end of its timeline, only 1 of the 188 infected snippets still carried the code.
  • How many: 188 infected snippets out of the 1,611 Report URI could check, belonging to 178 organizations. Report URI says the real number is likely higher, because it could only check the snippets it found in time.
  • Who: the largest group was banking and finance, with 32 organizations. Report URI also listed 8 healthcare and pharma organizations.
  • What is not known yet: how the attacker got write access to so many unrelated customer projects. Report URI says that is for Optimizely to explain. BleepingComputer reported that Optimizely pointed to a flaw in its Experimentation account signup flow. (BleepingComputer)

What did the malicious code do?

Every visitor received the same added script. What it did depended on the device and what the visitor did on the page. Report URI documented four behaviors:

  1. Card skimming. It watched the page's own forms for a card number, expiry date and security code, and tried to send them to the attacker. Report URI says this part was added during the day.
  2. Crypto address swapping. It replaced cryptocurrency wallet addresses on the page and in the clipboard with the attacker's. Report URI traced roughly $7,000 in crypto to the attacker's wallets, and BleepingComputer notes some of those wallets were active before this campaign.
  3. Cookies and screenshots. It could collect cookies, page addresses and screenshots and send them out.
  4. iPhone attack code. On iPhones and iPads it loaded known exploit kits aimed at older iOS versions. SecurityWeek reports that Hudson Rock found links to that infrastructure but no demonstrated successful exploitation. (SecurityWeek)

No one has reported that any named company's customers lost card data, and this brief does not claim that. Report URI says it cannot see how many cards or cookies reached the attacker. Its advice to affected sites is aimed at card fields in a site's own forms: treat cards entered on November 16th, 2026 as potentially exposed. That is the detail that matters for a small business: where does your website collect card numbers, and whose code runs on that page?

Why didn't the companies' own security stop it?

Because the code came from a source they had approved. Report URI's lesson is blunt: "trusted JavaScript doesn't always remain trustworthy."

Report URI also checked the Content Security Policy (CSP) of the affected organizations it could reach. A CSP is a browser setting that tells the browser which sites a page may load code from and send data to. Of the organizations it evaluated, 68 had no CSP at all. Only 24, about 15%, had a policy strict enough to block the payload. Allowing Optimizely's domain did not help, because the bad code came from Optimizely's domain.

Does this matter for a small regulated business website?

Yes, even if you have never heard of Optimizely. Most small business websites load several outside tools: a chat box, an appointment or booking widget, a tag manager, analytics, a review widget, a payment or intake form. Each one is a vendor that can change what runs on your pages. If one of those vendors, or one of the logins that can edit them, is compromised, the change shows up on your site without anyone touching your web server.

For a regulated business, that is a vendor risk question, not only a web design question. We covered the same pattern from the dashboard side in our brief on vendor dashboards that hold patient data.

What does PCI DSS 4.0.1 ask for on payment pages?

If you take card payments on your own website, the PCI Data Security Standard already covers this risk. PCI DSS v4.0.1 has two requirements aimed at scripts in the customer's browser on payment pages:

  • Requirement 6.4.3: every payment page script that loads and runs in the customer's browser must be managed: a method to confirm each script is authorized, a method to assure the integrity of each script, and an inventory of all scripts with a written business or technical reason for each one.
  • Requirement 11.6.1: a change- and tamper-detection mechanism must alert your staff to unauthorized changes to the scripts and security-impacting HTTP headers on payment pages, as received by the customer's browser, at least weekly or at the frequency set in your targeted risk analysis.

The PCI Security Standards Council published a guidance supplement on these two requirements in March 2025, "Payment Page Security and Preventing E-Skimming." It names Content Security Policy and Subresource Integrity among the possible ways to meet them. (PCI SSC blog)

Your payment provider and acquirer decide how you validate compliance. If your card fields are hosted by the provider, ask them in writing what that means for these two requirements on your site.

What about HIPAA and patient-facing pages?

HHS has a bulletin on online tracking technologies used by HIPAA covered entities and business associates. Its status needs care. On June 20th, 2024, a federal court in Texas vacated the part of the bulletin that said HIPAA applies when a tracking tool connects a visitor's IP address with a visit to a public page about a health condition or provider, where no login is required (American Hospital Association v. Becerra). HHS says it is evaluating its next steps. The rest of the bulletin still stands. (HHS, Use of Online Tracking Technologies)

The steady part is the vendor rule. If a website tool receives protected health information, for example from a patient portal or an intake form, the vendor needs a business associate agreement, and the practice needs to treat that tool as part of its HIPAA risk analysis. A script that can read every form on the page is exactly the kind of vendor to list.

Emry Networks 4-layer Defensible IT website script blueprint: a script inventory with a reason for each tool, limited edit access to tag and testing tools, a Content Security Policy, and change alerts on payment and intake pages

How does Standard IT differ from Defensible IT on website scripts?

Standard IT treats a website tag as a one-time install. Defensible IT treats every script as a vendor with an owner, a reason, and an alert.

Standard IT says "the marketing agency added that tag a while ago." Defensible IT can show the script list, who can edit each tool, the browser policy, and the alert history.

Standard IT looks like this:

  • Tags and testing tools added by whoever had the login, with no list of what loads where.
  • One shared login to the tag manager or chat tool, with no MFA.
  • No Content Security Policy, or one so loose it allows anything.
  • No one is told when the code on the payment or intake page changes.

Defensible IT looks like this:

  • A script inventory for each important page, with an owner and a written reason for each tool, managed through compliance-first managed IT services.
  • Named accounts with MFA on tag, testing and chat tools, and a short list of who can publish changes.
  • A Content Security Policy that limits where the browser may load code from and send data to, tested in report-only mode first.
  • 24x7 managed detection and response, plus change alerts on payment and intake pages that reach a person, with a log kept as evidence.

Your website script map

Here is a simple way to start, in about an hour with your web person or agency. For each of your most important pages, write down four things:

  • The page: home, contact or intake form, appointment booking, client portal login, online bill pay.
  • What it loads: every outside script or widget on that page, by vendor name.
  • Who can change it: the people and accounts that can edit each tool, and whether they use MFA.
  • Who gets told: the person or service that gets an alert if the code on that page changes.

If a box stays empty, that is your first finding. Pages that take card numbers, health details or client documents come first.

How does Emry Networks help regulated businesses in Jacksonville FL, Manchester NH, and nationwide?

Emry Networks provides managed IT, cybersecurity, and IT compliance program support for medical and dental groups, law firms, financial advisors, defense contractors, logistics firms, and other regulated industries. We serve regulated SMBs nationwide from hubs in the Jacksonville, FL and Manchester, NH areas. Pricing is all-inclusive and flat monthly, so overnight incident response does not bring a surprise invoice. Every engagement follows the 3-phase Emry Assurance Roadmap (often delivered as a 90-day blueprint):

  • Phase 1 - Red Zone (Regulatory Discovery): Map the scripts and vendors on your key pages, who can change them, and which ones touch card, patient or client data.
  • Phase 2 - Transition (Security Hardening Sprint): Remove tools you no longer need, move to named logins with MFA, add a Content Security Policy, and confirm business associate agreements where they apply.
  • Phase 3 - Green Zone (Continuous Management & Drift Control): Watch for script changes, review the inventory on a set schedule, and hand you dated evidence for assessments and questionnaires.

Not sure what your website loads? Book a 30-Minute Risk Assessment. In thirty minutes we review your key pages, the tools on them, and who can change them, then tell you plainly what we find. Prefer the phone? Call (603) 202-3200.

What are the next steps for your team?

Start the script map above this week, then book a 30-Minute Risk Assessment to go through it with us.

Frequently asked questions

What happened in the Optimizely supply-chain attack?

On November 16th, 2026, an attacker added malicious code to customer projects in Optimizely Web, a website testing tool. Report URI checked 1,611 Optimizely snippets and found 188 infected, belonging to 178 organizations. Optimizely confirmed an unauthorized party exploited a vulnerability in its Experimentation product, and says it fixed the vulnerability and removed the code.

Were the affected companies hacked?

Not directly, according to Report URI. Their own servers and code were not the entry point. The malicious code was added to a vendor tool their websites already loaded, and it was served from the vendor's trusted domain.

What could the malicious code do?

Report URI says it looked for card numbers typed into a page's own forms, swapped crypto wallet addresses, collected cookies and screenshots, and served attack code aimed at older iPhones and iPads. Roughly $7,000 in crypto reached the attacker's wallets. No named company has reported that its customers lost card data.

What do PCI DSS 6.4.3 and 11.6.1 require?

Under PCI DSS v4.0.1, requirement 6.4.3 says each script on a payment page must be authorized, checked for integrity, and listed with a written reason. Requirement 11.6.1 says a change- and tamper-detection mechanism must alert staff to unauthorized changes to payment page scripts and security-impacting headers, at least weekly or as set by a targeted risk analysis.

Does HIPAA cover website tracking tools?

It can. HHS has a bulletin on online tracking technologies. On June 20th, 2024, a federal court vacated the part covering public pages that need no login, and HHS says it is evaluating next steps. The rest stands: a website vendor that receives protected health information needs a business associate agreement.

Next steps

See how we help businesses in your industry, or book a short call to talk through where you stand today.

Share this post

Read more from our team

Explore insights on compliance and security.

Ready to strengthen your compliance?

Get hands-on assessment and guidance from our compliance experts.