Optimizely Cyberattack: What It Means for Nonprofit Donation Pages

Illustration of a nonprofit donation form with a shield guarding the card field and outside scripts connecting to the page
TL;DR: The Optimizely cyberattack on November 16, 2026 ran malicious code on pages of at least 178 organizations, per Report URI, including four nonprofits in its list: Change.org, ASPCA, UNICEF USA and DonorsChoose. It targeted card details typed into the page itself and, per Report URI, could not reach hosted payment iframes. No source reports stolen donor data, so Scottship Solutions advises nonprofits to inventory every third-party script on their donation pages and confirm who can edit each one before Giving Tuesday on December 1.

Updated November 18, 2026. Whoever runs your website, whether in-house or through managed IT support for nonprofits, should be able to answer one question first: who can edit the scripts on your donation page? The Optimizely cyberattack is a different event from the Optimizely data breach reported in February 2026.

This post reflects what Report URI and Optimizely have published as of November 18, 2026. It says plainly where a detail is only reported or not yet public.

Not sure what runs on your donation page? Our nonprofit tech stack audit is the place to start, and we can talk through what to look for on your donation page. Tell us which donation platform you use.

What happened in the Optimizely cyberattack, and does it affect nonprofits?

What this means in plain English

Many big websites use a tool from a company called Optimizely to test different versions of their pages. Think of Optimizely as a contractor holding a key to the front door of many shops. The tool works by adding a small piece of code to the website that loads for every visitor.

On November 16, 2026, attackers got into Optimizely’s system and swapped in their own code. For part of a day, visitors to at least 178 organizations, per Report URI, were loading code that watched for credit card numbers and crypto payment details typed into the page. Optimizely says it fixed the problem and removed the code, and no source reports stolen donor data.

For a nonprofit, the risk comes from any outside tool that adds code to your donation page, whichever company runs it. If the card box on your donation form is run by your payment company, for example Stripe, that code could not see it, per Report URI. If donors type card details straight into your own page, outside tools on that page could.

Attackers wrote malicious JavaScript into the Project JavaScript field of Optimizely customer projects, per Report URI. The code reached visitors the normal way, because Optimizely’s CDN “served exactly what it was given,” in Report URI’s words. Some coverage calls it the Optimizely hack, and StepSecurity’s write-up uses the name OPTIMJACK, which it credits to researcher Amirul Cyber. The pattern is a supply chain attack: a trusted vendor’s delivery network carried the attacker’s code to many sites at once.

Report URI counted 188 infected snippets out of 1,611 it checked, tied to at least 178 organizations. Report URI says the real number is likely higher, because its sweep covered only snippets it already knew about. Nonprofits are affected if their site loaded one of those snippets, which is the question the third section helps you answer.

The timeline below uses Report URI’s sightings in UTC, plus Optimizely’s own status page for the last row. The 04:21 entry is the first observation, not necessarily the true start, so this post states no duration.

When (UTC) What happened Source
November 16, 04:21 First infected snippet seen (first observation, not necessarily the true start) Report URI
November 16, 13:43 Card skimmer added Report URI
November 16, 21:52 Last infected snippet seen Report URI
November 16, 23:11 All infected snippets confirmed clean Report URI
November 17, 01:02 Incident listed on Optimizely’s status page, which says the vulnerability was fixed and the injected code removed Optimizely status page

How the attacker got write access to so many customer projects is not public. Report URI says it does not know.

Is the Optimizely cyberattack the same as the Optimizely data breach in February 2026?

No. February 2026 was a vishing breach of Optimizely’s internal business systems, per SecurityWeek’s February 25, 2026 report. The November 16 cyberattack is malicious JavaScript served to website visitors, and no source we reviewed links the two. Searches for an Optimizely breach return both stories, so check the date before you act on any advice.

Was my nonprofit affected, and how do I check whether our site uses Optimizely?

Report URI’s list names four nonprofits: Change.org, ASPCA, UNICEF USA and DonorsChoose. Each is named as a site that loaded an infected snippet. No source says donor data was stolen from any of them, and no source says whether their donation forms were hosted or embedded.

You can check your own site in three steps, and none needs a security team.

  1. Ask your web vendor: ask whoever manages the site whether it loads Optimizely.
  2. Look at the page: search the page source, or your browser’s developer tools, for cdn.optimizely.com. StepSecurity notes that some sites serve the snippet from their own domain, so ask your web vendor as well.
  3. Do not stop at a clean result: Optimizely says it removed the injected code, so a page that looks clean today does not show what it loaded on November 16. StepSecurity advises asking Optimizely which projects were modified, when and through which accounts.

If your site did load it, Optimizely told BleepingComputer it notified all affected customers. The last section of this post covers what to do next. Our guide to protect nonprofit donor data covers the wider picture.

Why is a nonprofit that never used Optimizely still exposed to third-party script risk on donation pages?

Report URI found that hosted payment iframes, from providers such as Stripe and Adyen, were out of the skimmer’s reach. The skimmer targeted card and crypto details typed into the page itself. Exposure therefore comes from any third-party script running on a page where card data is typed into the page: a tag manager, analytics, A/B testing, chat or a donation widget.

A third-party script attack works the same way whatever the vendor. The tag manager risk is that one account with edit rights changes what every visitor’s browser runs. The question to ask is who controls the page where the card is typed.

Setup Who controls the card field What a compromised script on the page can reach Your main question for the vendor
Hosted payment page or iframe The payment provider Report URI found hosted iframes (Stripe, Adyen and similar) out of the skimmer’s reach Is the card field hosted by the payment provider on every donate button?
Embedded form on your own page Your page, so whoever can edit its scripts Card details typed into the page itself, which is what the Optimizely skimmer targeted, per Report URI Which scripts load on that page, and who can edit each one?

Donation page skimming is not new. In January 2020, an Australian bushfire donation site was compromised, per Dark Reading’s coverage. That case involved a compromised Magento site, not a vendor script, so Optimizely is a different route to the same outcome.

No coverage we reviewed named a donation platform as affected, and we make no claim about how any platform’s form is built. Check that platform’s own documentation.

What is a Magecart attack, and how is it different from card testing?

Magecart is browser-based web skimming: attackers inject malicious JavaScript into a checkout or payment page to capture card data as the visitor types it, also called formjacking. The card skimmer Report URI saw added at 13:43 UTC on November 16 does the same job.

Skimming steals real cards from real donors. Card testing is a different problem, where fraudsters make small fake donations to check whether stolen cards work. The Giving Tuesday tech checklist from Scottship covers card testing, so this post does not repeat its steps.

How do you reduce third-party script risk on your donation pages?

A script inventory is a job a non-technical director can own. List every tag and script on the donation page, who added it, why, and who can edit it. Remove what has no owner. Treat every tool that can edit page scripts, such as a tag manager, A/B testing tool, chat widget or analytics account, as an account that needs multi-factor authentication and a named owner.

Then put four questions to your donation platform and web vendor.

  • Is the card field hosted by the payment provider?
  • Which scripts load on that page?
  • How are script changes detected?
  • Who gets alerted?

Two terms are worth asking your vendor about by name. A content security policy limits which sources a page is allowed to load scripts from, and script integrity checks confirm a script has not changed since it was approved.

Monitoring tools exist for this job. cside, Feroot, Reflectiz and Jscrambler sell script monitoring, and each sets its own pricing. We do not recommend one here.

Does PCI DSS 6.4.3 and 11.6.1 apply to a nonprofit donation page?

PCI DSS has two requirements written for payment page scripts. Requirement 6.4.3 covers an inventory of every script on the payment page, with a written reason and an authorization for each. Requirement 11.6.1 requires a way to alert on unauthorized changes to the payment page’s contents and HTTP headers.

Both have been required since March 31, 2025, per the PCI Security Standards Council. Both are payment page script requirements aimed at the gap Report URI describes: scripts changing on a page where cards are typed.

Whether those requirements reach your form depends on how the form is built. The PCI Security Standards Council says its SAQ A script criterion does not apply to a merchant that redirects customers to a payment provider. A merchant whose page embeds the provider’s payment form, for example in an iframe, must confirm the page is not susceptible to script attacks.

It can do that with techniques such as 6.4.3 and 11.6.1, or by getting confirmation from its compliant payment provider. Ask your processor which questionnaire and requirements apply to your form.

Our overview of nonprofit PCI DSS and donor data frameworks covers the general framework, so this post does not restate it.

Frequently Asked Questions

What happened in the Optimizely cyberattack?

On November 16, 2026, attackers used Optimizely’s experimentation platform to serve malicious JavaScript on sites of at least 178 organizations, per Report URI. Optimizely’s status page says it fixed the vulnerability and removed the injected code. How the attacker got access is not public.

Is the Optimizely cyberattack the same as the Optimizely data breach in February 2026?

No. The February 2026 Optimizely data breach was a vishing attack on the company’s internal business systems, per SecurityWeek. The November 16 cyberattack served malicious JavaScript to website visitors, and no source links the two.

Who is responsible for script security when I use a donation platform?

Responsibility is shared, and the split depends on who hosts the card field. Ask your donation platform in writing which parts of the donation page it controls and which scripts your team can add or edit. Your own page, tag manager and analytics accounts stay yours to inventory, whichever platform you use. For Optimizely, ask your web vendor whether your site loads it and check the page source for cdn.optimizely.com, because a clean page today does not show what it loaded on November 16.

Is my nonprofit donation page safe from skimming?

Not automatically. The deciding factor is who controls the card field. Report URI found hosted payment iframes out of the Optimizely skimmer’s reach, while card details typed into the page itself were the target. Scottship’s advice is to list every script on the donation page and name an owner for each before Giving Tuesday.

How much does third-party script monitoring cost?

Cost depends on the tool and the number of pages monitored, and vendors change their prices, so check each vendor’s own pricing page for the current figure. A script inventory needs no tool and costs staff time only, so start there.

Sources and further reading

What should a nonprofit do if it already loaded a compromised script?

A nonprofit whose site loaded a compromised script has three jobs. Ask your web vendor which scripts loaded and when. Ask your payment processor whether card activity on that page needs review. If you carry cyber insurance, tell your insurer.

Optimizely told BleepingComputer it notified all affected customers, so check the inbox of the person who owns your Optimizely account. For the longer path, read how long cyberattack recovery takes, which this post does not retell.

Giving Tuesday falls on December 1, 2026. Finish the script inventory on your donation page first.

The Scottship Tech Stack Audit reviews the tools your nonprofit runs, and we can talk through what to look for on your donation page before Giving Tuesday. Send us your donation platform and website vendor names.

Will Facques

Written by

Will Facques

Senior IT Consultant at Scottship Solutions

Will works directly with nonprofit and small business clients on infrastructure, managed services, and technology implementations. He translates complex technical requirements into practical solutions that actually get done.

Certifications

PMP (Project Management Professional) • Lean Six Sigma Yellow Belt • CompTIA Network+

Industries Served

Human Services, Healthcare & Community Health, Education & Youth Development, Faith-Based, Child Advocacy, Arts & Culture

Archives

Get Scottship’s research in your Google results