Who Can Read Your Checkout? A 45-Minute Script Audit
On Monday 16 November 2026, visitors to some of the world's best-known websites loaded code that tried to swap copied crypto wallet addresses and copy card details from payment forms. The sites themselves hadn't changed a line. The code arrived through Optimizely, a testing tool many large brands load across their sites.
Small online stores use the same pattern every day: a chat widget, a review app, an analytics tag, an upsell app. Each one is another company's code running in your customer's browser, and you've probably added a few yourself. This guide gives you a 45-minute audit for the pages where customers type card details.
What happened with Optimizely
Optimizely Web Experimentation lets each customer add their own JavaScript to a project, and Optimizely's network serves it to the site's visitors. Security researcher Scott Helme of Report URI found that an attacker had written malicious code into that project JavaScript for at least 178 organisations. He found it in 188 of the 1,611 Optimizely snippets he checked, and expects the real number is higher.
Through the day the code gained a crypto address swapper and a card skimmer that read card numbers, expiry dates and security codes from a site's own form fields. StepSecurity's analysis notes the skimmer could only read fields on the page itself, so card fields inside a payment provider's hosted iframe were out of its reach. Optimizely told The Register it had fixed the vulnerability and removed the injected code from affected projects, and Report URI found the infected files clean by late that day (UTC).
What you should take away
Every script on a checkout or payment page can read what customers type there. Keep a short list of those scripts, give each one an owner and a reason, remove the rest, and set up a way to spot when something changes. The safest card fields sit with your payment provider, in their hosted page or iframe.
Why this is also a PCI DSS question
The card industry standard, PCI DSS v4, has two rules aimed at this exact risk. Both have applied since 31 March 2025.
- Requirement 6.4.3: every script on a payment page is approved, has a way to check it hasn't been tampered with, and sits on a list with a written reason it's needed. That includes your own scripts and those from other companies.
- Requirement 11.6.1: you need a way to spot unauthorised changes to the payment page as customers' browsers receive it, and to alert staff. Checks run at least weekly, or as often as your own risk review sets.
Many small stores fill in the shorter SAQ A questionnaire. Since 31 March 2025, it asks you to confirm your site is protected from script attacks. The PCI Security Standards Council says you can do that in two ways: use techniques like those in 6.4.3 and 11.6.1 yourself, or get written confirmation from your PCI DSS compliant payment provider that its embedded payment form includes that protection when set up to its instructions. Your payment provider or bank can tell you which questionnaire applies to you.
Run the 45-minute checkout script audit
- Map your payment pages (5 minutes). List every page where a customer enters card or wallet details, plus the page that loads your payment form. Note whether card fields sit on your page or inside your provider's hosted page or iframe.
- List the scripts (15 minutes). Open each page in Chrome, open Developer Tools, and filter the Network tab by JS. Write down each script's web address and the company behind it. Check your tag manager for anything it fires on checkout too.
- Give each script an owner and a reason (10 minutes). For every line, write who added it, which tool or app it belongs to, and why it needs to run on this page.
- Remove what nobody can justify (10 minutes). Uninstalled apps often leave code behind. Remove ownerless scripts, move marketing tags off payment pages where you can, and keep a copy of what you removed.
- Lock down the accounts (5 minutes). For each tool that can publish code to your site, turn on multi-factor authentication, remove access people have outgrown, and keep admin rights to those who need them.
Copy this script register
- Page: checkout, payment or order confirmation.
- Script source: the full web address.
- Vendor and tool: for example a review app, analytics tag or chat widget.
- Reason it's on this page: one sentence.
- Owner: the person who answers for it.
- Who can change it: the accounts that can publish code through this tool.
- Protection: platform sandbox, Content Security Policy, Subresource Integrity or change monitoring.
- Last reviewed: date and initials.
Use the controls your platform gives you
On Shopify
Shopify runs app pixels and custom pixels in a sandbox, an isolated environment separate from the rest of the store. Pixels load on the storefront, checkout, thank you and order status pages, and you can review them in the Customer events section of your admin settings. The old Additional scripts box in checkout settings has been view-only since 28 August 2025, and non-Plus stores had until 26 August 2026 to upgrade their thank you and order status pages. On Shopify, your audit is mostly a review of installed apps, pixels and who can change them. That's a quick job.
On a custom site, WooCommerce or similar
Where you control the code, two browser features help:
- Content Security Policy (CSP): a response header that sets which sources the page may load scripts from and where it may send data. Start in report-only mode to see what would be blocked, then enforce it. Of the 256 sites Report URI checked during the incident, 24 had a policy that blocked the payload.
- Subresource Integrity (SRI): a hash on a script tag so the browser refuses a file that has changed. It suits fixed files with version numbers. Tools that update their scripts constantly, like testing and tag platforms, need CSP and monitoring instead.
Set up change monitoring
The Optimizely code changed many times in a single day. A weekly review catches what a yearly one misses. Options range from a script monitoring service to your payment provider's own protection, and your developer can set up alerts on CSP reports. Whatever you pick, make sure someone gets the alert and knows what to do next. We'd start with whoever already looks after your site.
Limits to keep in mind
An audit lowers risk; it can't promise a breach will be stopped. Hosted payment fields protect card numbers, but a script on the page can still read other details customers type, such as names, emails and addresses. Compliance obligations depend on your setup and your acquirer, so treat this as general information and check the details with your payment provider or a qualified assessor.
Takeaway
Your checkout is only as trusted as the least-watched script on it. Book 45 minutes this week: list the scripts, name an owner for each, remove the extras and switch on alerts. Then repeat the review whenever you add or remove an app.
Want a second pair of eyes on your checkout scripts? Contact Maud Digital to review your payment pages and app list together.
Source note: This original Maud Digital guide uses The Register's report (including Optimizely's statement), Report URI's investigation and StepSecurity's analysis; PCI DSS v4 requirement text from the PCI SSC SAQ A-EP, and the PCI Security Standards Council's posts on SAQ A updates and FAQ 1588; the Australian Cyber Security Centre's Secure your website guidance; Shopify's pixels overview and Thank you and Order status upgrade pages; and MDN's Content Security Policy and Subresource Integrity guides. Checked on 19 November 2026. General information only, not professional advice.
General information to help you decide, based on public sources at the date shown. For legal, tax or compliance questions about your business, speak with a qualified adviser.