Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Web skimming steals card data through a trap planted in a checkout page. The attacker rewrites an e-commerce site (an online shop) so that the card number and other details a buyer enters are quietly sent outside. Skimming originally meant reading card data off a card to steal it.
How does web skimming work?
Imagine an inconspicuous reader placed beside the cash register. The customer thinks they are using a card at the usual shop's register, yet the data is also copied by the reader.
The method divides roughly into three stages: getting into the site, placing a malicious program, and stealing the input at checkout. In a case JPCERT/CC described in 2021, an administrator's credentials were stolen through a weakness in the admin screen, and JavaScript that watched operations at login and checkout was placed. The stolen data was kept in a file on the server.
JPCERT/CC explains that the attack did not target a weakness unique to EC-CUBE, and that other e-commerce sites could be affected if their admin screens had the same kind of weakness. The specific form that swaps the checkout page for a fake is explained under formjacking. The routes in can also be read on the card skimming vulnerability page.
Why does web skimming matter?
In December 2019 IPA warned that many cases had been confirmed in which the checkout page of sites built with EC-CUBE was tampered with and credit card numbers and other data were stolen. According to the Ministry of Economy, Trade and Industry, about 140,000 leaked card numbers and similar items were involved.
The buyers are harmed, but the shop loses trust. Buyers feel no difference on the screen, so they notice late. For operators too there are few clues, and discovery can be late.
The measure IPA gave to operators is to check the EC-CUBE version in use and, if it is not the latest, update promptly. JPCERT/CC Eyes advises updating plugins as well as the core, and regularly checking vulnerability information for the parts in use. The free URL check shows what is visible from outside your shop.
Related terms
- Formjacking: swapping the checkout page for a fake to steal card numbers
- Tampering: a site's content being rewritten without permission
- XSS: a weakness that lets someone insert unauthorized commands through input fields and the like
- WAF: a wall that stops suspicious traffic at the entrance
Frequently asked questions
If we do not store card data ourselves, do we still need to worry about web skimming?
Yes. This method targets not stored data but the information a buyer types into the checkout page at that moment. Whether or not you store it, you need updates that prevent rewriting, and checks that nothing has been rewritten.
What can alert you to web skimming damage?
The page looks unchanged, so operators find it hard to notice, and with few clues the discovery can be late. Check regularly that the files of the checkout page contain no change you do not recognize.
Next step
The whole order for preventing rewriting is in tampering measures. The free URL check shows only what is visible from outside your shop, so to plan a check of the checkout page, contact us.
Frequently asked questions
If we do not store card data ourselves, do we still need to worry about web skimming?
Yes. This method targets not stored data but the information a buyer types into the checkout page at that moment. Whether or not you store it, you need updates that prevent rewriting, and checks that nothing has been rewritten.
What can alert you to web skimming damage?
The page looks unchanged, so operators find it hard to notice, and with few clues the discovery can be late. Check regularly that the files of the checkout page contain no change you do not recognize.