Skip to main content
Technology

Web Skimming: How a Trusted Site Can Steal Your Card

Web skimming code hit 178 big websites in one day. Learn how a trusted checkout can steal your card, how to check exposure, and what you owe if it's used.

Nora Whitfield
November 22, 20268 min read
Share
Web Skimming: How a Trusted Site Can Steal Your Card
Table of contents

You bought something from a big, well-known website on a Sunday in November. The padlock showed in the address bar, the checkout page looked normal and the order went through. Two weeks later, a charge you do not recognise appears on your card.

That is the risk behind web skimming, and a single attack on November 16 showed how far it can reach. Malicious code ran on the websites of 178 organisations, including household names, without any of those companies being hacked directly. Here is how a trusted site can steal your card, how to tell if you were exposed, and what the law says you owe if a thief uses your number.

What Is Web Skimming?

A physical card skimmer is a fake reader glued over a gas pump slot. Web skimming is the same trick in code. A small script hides inside a real checkout page and copies what you type before you press "Pay".

You never see it. The page looks identical, the address is correct and the padlock is real, because the padlock only proves your connection to the site is encrypted. It says nothing about what code the site is running.

Most large websites do not run only their own code. They load dozens of scripts from outside companies for analytics, ads, chat widgets and testing tools. Each of those is a door. If an attacker gets into one supplier, every site that loads that supplier's script starts serving the attacker's code.

How One Supplier Put Skimming Code on 178 Sites

Optimizely sells a tool that lets companies test different versions of their web pages. Customer sites load a snippet of code from Optimizely so those tests can run on every page.

In an update posted to its status page on November 18, Optimizely said an unauthorised party had "exploited a flaw in the Optimizely Web Experimentation account signup flow." The attacker used it to impersonate users and insert malicious JavaScript into customer projects. Optimizely said fewer than 5% of its customers were affected, the code was removed and no credentials were breached.

Security researcher Scott Helme of Report URI, a company that monitors website scripts, mapped the damage. His team checked 1,611 Optimizely snippets and found 188 infected, belonging to 178 organisations. He named Zoom, the BBC and CNN among them.

The timeline, in UTC

  • 04:21: first injected code seen, according to Report URI.
  • 08:10: first version of a script that swapped cryptocurrency addresses.
  • 13:43: the card skimmer was added.
  • Evening: mass clean-up began, with one infected snippet still found at 21:52.

Report URI counted about 17.5 hours between the first injection and the last infected snippet it found. The attacker rebuilt the code 26 times that day, adding features as it went. Banking and finance was the largest group, with 32 affected organisations.

What the Code Stole, and What It Could Not Reach

According to Report URI's analysis, the injected code did four things.

  1. Card skimming. From 13:43 UTC, it captured card numbers, expiry dates and CVV codes typed into checkout forms and sent them to the attacker.
  2. Crypto address swapping. It replaced wallet addresses on the page and in your clipboard, so a payment you meant to send to a friend or exchange went to the attacker instead.
  3. Cookie and screenshot theft. Near payment wording, it sent the page address, some cookies and a screenshot back to the attacker.
  4. iPhone exploits. On iPhones and iPads it loaded exploit kits, including DarkSword for iOS 18. Report URI says iOS 18.7.3 and 26.3 or later are patched.

One design choice blocked the skimmer. Report URI says cards entered in a payment provider's hosted frame were out of reach. That frame is a box inside the checkout page that actually loads from the payment company, such as Stripe or Adyen. Code running on the shop's page cannot read inside it.

You cannot easily tell which kind of form you are using. But it explains why some sites on the list exposed cards and others probably did not.

Were You Exposed? A Quick Check

Ask yourself three questions about November 16.

  • Did you type a card into a checkout on a large brand's website that day? Report URI advises treating any card entered on an affected site that day as possibly exposed.
  • Did you copy and paste a crypto wallet address after visiting one of those sites? Check the address you sent to against the one you meant to use.
  • Is your iPhone or iPad running an older iOS version? Update to iOS 18.7.3 or later on the 18 branch, or 26.3 or later.

If the answer to the first question is yes, you do not need to cancel your card in a panic. You need to watch your statements, and know the rules.

Your Liability If Someone Uses Your Card: A Worked Example

US federal rules treat a stolen card number differently from a lost card. According to the Federal Trade Commission, if your account number is used but the physical card is not lost or stolen, you are not responsible for unauthorised credit card charges. For debit cards, you are not responsible either, if you report within 60 calendar days after your statement is sent.

Here is how that plays out with real numbers. Say a skimmer captured both cards below, and a thief spent $1,200 on each.

  • Credit card: the $1,200 is the bank's money while you dispute it. Your legal liability is $0.
  • Debit card, reported in time: your liability is also $0, but the $1,200 left your checking account. Your rent or bill payment can bounce while the bank investigates.
  • Debit card, reported late: the FTC warns that if you report more than 60 calendar days after the statement is sent, you could lose all the money taken, and possibly more.

The legal answer is similar for both cards. The practical answer is not. A credit card puts the bank's money at risk first, and a debit card puts yours at risk first. That is a strong reason to use a credit card for online shopping on sites that load lots of third-party scripts.

How to Shop Online With Less Exposure

You cannot audit every script on every site. You can cut what a skimmer gets if it is there.

  1. Use a credit card or a wallet payment. Wallet buttons and virtual card numbers mean the real card number is not typed into the page. Some card issuers also offer virtual card numbers for online use.
  2. Turn on transaction alerts. A push alert for every charge turns a two-week discovery into a two-minute one.
  3. Check statements monthly, not yearly. The debit card clock starts when the statement is sent, not when you read it.
  4. Double-check pasted crypto addresses. Compare the first and last several characters before sending anything. A swapped address looks just as valid.
  5. Keep your phone and browser updated. The iPhone exploits in this attack only worked on unpatched versions.

For the iPhone side of this attack, our guide on staying safe from the DarkSword iPhone hack covers the exploit kit in more detail. A supplier quietly exposing customers is also the story behind our piece on how a newsletter vendor can leak your email. If you hold coins, our explainer on cryptocurrency covers why a sent transfer usually cannot be reversed.

Frequently Asked Questions

What is web skimming and how does it work?

Web skimming is malicious code hidden in a website's checkout page that copies card details as you type them. It often arrives through a third-party script the site loads, so the website itself may not have been hacked directly.

Which websites were affected by the Optimizely hack?

Report URI found 178 organisations whose Optimizely code was infected on November 16, naming Zoom, the BBC and CNN among them. Optimizely said fewer than 5% of its customers were affected.

Am I liable if my credit card number is stolen online?

Under US rules described by the FTC, you are not responsible for unauthorised charges when your card number is used but the card itself is not lost. Debit card users must report within 60 calendar days after the statement is sent.

Is the padlock in my browser a sign a site is safe?

No. The padlock only means your connection to the site is encrypted. A site with a valid padlock can still run a skimming script loaded from a compromised supplier.

Trust the Payment Method, Not the Brand

The November 16 attack hit sites run by banks, broadcasters and software companies, which is exactly why brand trust is a poor defence. What protected shoppers was structure: hosted payment frames, credit cards that keep your cash out of reach, and alerts that catch a bad charge fast. Set those up once, and the next supplier hack becomes an annoying dispute instead of an emptied account.

Share

Written by

Nora Whitfield

Technology & Science

Covers technology and science for Quick Trend Insights, with a focus on what new AI tools, consumer hardware and space missions actually change for the people following them.

More articles

Related Articles

View all