DEV Community

Cover image for Apple Pay Down, Bank Transfers Delayed, Websites Hacked: Was It One Attack?
Detroon Shah
Detroon Shah

Posted on Originally published at Medium

Apple Pay Down, Bank Transfers Delayed, Websites Hacked: Was It One Attack?

The Apple Pay outage, Chase bank transfer delays and the Optimizely script hack all hit in November 2026. What caused each one, and what they teach web developers about third-party scripts.

Quick summary

  • Apple Pay & iCloud (Nov 17): caused by Apple's own internal update, not a hack.
  • Bank transfer delays (Nov 16): a software bug at JPMorgan Chase that slowed payments to other banks too.
  • Hacked websites: attackers abused Optimizely's signup flow and inserted malicious JavaScript into customer projects.
  • PHP: no evidence links it to any of the three.
  • Your takeaway: audit the third-party scripts on your checkout and login pages.

On Monday, Downdetector filled up with reports of delayed transfers at major U.S. banks. On Tuesday, Apple Pay and iCloud stopped working for a lot of people. The same week, Optimizely disclosed that malicious JavaScript had been injected into customer websites through its A/B testing product.

Three failures in two days. It's tempting to connect them, and some people online did.

Based on what's been published so far, they aren't connected. Each has a different root cause. The third one is the one I'd pay attention to if you build or run websites.

1. Why Apple Pay and iCloud went down

On November 17, Apple said an internal update had disrupted services including Apple Pay and iCloud. The company ruled out a cyberattack and later confirmed that everything was back to normal.

So this was a bad deploy, not a breach. (Reuters ยท CBS News)

2. Why bank transfers slowed at several U.S. banks

A day earlier, JPMorgan Chase said a software bug in its internal systems had slowed some transactions. Banks pass payments back and forth, so a delay at Chase can show up for customers at other banks too. U.S. Bank said its own systems were working normally, although some Zelle transfers involving other banks could take longer. (Reuters)

Transfers between banks run over shared rails like Zelle and ACH, so a processing backlog at one large bank shows up as delays at every bank it settles with.

3. How one compromised service hit many websites at once

This one is different, and it's the one that matters for web teams.

Optimizely, an A/B testing provider, confirmed that an attacker abused a flaw in its signup process and inserted malicious JavaScript into customer projects. (Optimizely's incident report ยท Salesforce's response)

What matters is where that code runs. When your site loads a third-party script, the script runs in your visitor's browser. If the vendor's copy changes, your visitors get the new version, even if your team didn't change anything.

Diagram of a third-party script supply chain attack: an attacker edits a vendor's hosted A/B testing script, the website loads it with a script tag, and the visitor's browser runs the code on checkout and login pages.
How a supply chain attack works: the website team deployed nothing, but visitors still got new code. Graphic by the author.

A common reaction is "just use Subresource Integrity." SRI doesn't really fit here. A/B testing scripts change every time someone edits an experiment, so you can't pin them to a fixed hash. More realistic controls are a strict Content Security Policy, loading the tool only on pages that need it, and keeping it off checkout and login entirely where you can.

For example, a CSP header that only allows scripts from your own origin and one named vendor:

Content-Security-Policy: script-src 'self' https://cdn.optimizely.com; connect-src 'self' https://logx.optimizely.com
Enter fullscreen mode Exit fullscreen mode

This won't stop a compromised vendor script from running, but it does limit where that script can send stolen data.

Was PHP involved?

Some posts tied these outages to a PHP vulnerability.

The Texas Department of Banking issued a PHP security alert on October 27 and told financial institutions to patch affected systems. That advisory is real. (Texas Department of Banking)

However, the public reports on Chase, Apple and Optimizely each name a different cause, and I found no evidence linking the PHP alert to any of these incidents. Timing alone isn't evidence.

The lesson for website owners

Whenever I audit a website, I ask one question first:

What runs on your checkout, login, or contact page that your team didn't write?

Most teams can't answer it right away. Here's where I'd start:

  1. Pick one important page: checkout, login, or contact.
  2. List every analytics tag, chat widget, and A/B testing script it loads.
  3. For each one, write down who owns it.
  4. Then write down who can switch it off, and how fast they can do it.

A quick way to get that list from the browser console:

[...document.scripts].map(s => s.src).filter(src => src && !src.startsWith(location.origin));
Enter fullscreen mode Exit fullscreen mode

Website security checklist: pick your checkout, login or contact page; list every third-party script; name who owns each one; name who can switch it off.
Build this list before you need it, not during an incident.

FAQ

Was the Apple Pay outage a cyberattack?
No. Apple said an internal update caused it and ruled out a cyberattack.

Why did my Zelle or bank transfer take longer?
JPMorgan Chase reported a software bug that slowed some transactions. Because banks send payments to each other, customers at other banks could see delays too.

What is a third-party script supply chain attack?
It's when attackers change code that a vendor hosts and many websites load, such as analytics, chat, or A/B testing tools. Every site using that script then serves the attacker's code to its visitors.

How do I protect my website from this?
List every third-party script on your sensitive pages, remove the ones you don't need, assign an owner to each, and consider a Content Security Policy (CSP) to limit what scripts can do.

Need a second pair of eyes?

I'm Syed Zubair Hussain Shah, a full-stack developer. I build websites and audit existing ones for performance, technical SEO, and third-party script risk, including the kind of third-party exposure described above.

See my work and get in touch: zubairhussain.xyz

Originally published on Medium.

Top comments (0)