Formjacking meaning, in plain words

Formjacking swaps in a fake payment screen to steal card numbers. How data leaks while the screen looks normal, the EC-CUBE losses, and what to check.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Formjacking is a method of replacing a payment screen with a fake to steal card numbers. The buyer thinks the usual screen is taking their number, but what they type is also sent to a destination the attacker prepared. It can happen with no change in how the screen looks, which makes it hard to notice.

How does formjacking work?

Compare it with a small reader placed beside a shop's register. The customer uses a card at the genuine register, but the card details are copied by the reader too. On the internet, the same happens when a malicious command is slipped into the page that shows the payment screen.

The PCI Security Standards Council says that scripts running in the buyer's browser are a major target for attackers trying to steal payment card data. This kind of attack is also called e-skimming.

It is easiest to understand if you think of two routes by which the malicious command gets in. In one, your own site's files are tampered with. In the other, another company's program that you load from outside for advertising or analytics is rewritten, and damage occurs even though your own files are intact. The flow by which card data is stolen is explained in card skimming.

Why does formjacking matter?

Because the damage goes straight to customers' card data. IPA warned that many cases were confirmed in which the payment screens of sites built with EC-CUBE were tampered with and card numbers and other data were stolen. According to the Ministry of Economy, Trade and Industry, the leaked card numbers and other data came to about 140,000 as of December 2019.

This is not only an old story. For the vulnerability in the Amazon Pay plugin for EC-CUBE published on 14 October 2026, JVN records that the developer has already confirmed attacks that use it. For parts that touch payment, a late update goes straight into how easily you are targeted.

What an operator can do starts with bringing parts up to date. Next, list the scripts the payment screen loads and look for any you do not recognize. PCI SSC has published guidance on requirements 6.4.3 and 11.6.1, which cover managing the scripts on payment pages and detecting changes. Our Cyber Shield Guard supports detection of file changes.

What should you check on your payment screen?

  1. From which screen of your own site does a customer go on to pay?
  2. Which outside scripts does that screen load, and who added each?
  3. Who would notice if a file on the payment screen changed?

To check your own payment screen with us, contact us.

Related terms

  • Tampering: rewriting a site's contents without permission
  • Dependencies: parts, written by others, that your program uses

Frequently asked questions

If I take payment on an outside payment company's screen, can formjacking not happen?

It becomes less likely, but not impossible. PCI SSC includes cases where a payment screen is embedded, because the pages around it can affect payment security. Check once from which screen of your own site a customer proceeds to payment.

Can I be a victim and not notice?

Yes. The typed data is sent out while the screen looks unchanged, so some operators learn of it only through a call from a card company or payment provider. A mechanism that watches payment screen files for changes shortens the time before you notice.

What should I do first if I suspect damage?

Save the payment screen files and logs without deleting them, and change the passwords for the admin screen and the server. Then contact your payment provider and the emergency guide desk. Restoring before the cause is investigated erases the clues.

Next step

The free URL check shows only what is visible from outside. If you suspect damage, go to the emergency guide first. A detailed account is in card skimming, and for your own case, contact us.

Frequently asked questions

If I take payment on an outside payment company's screen, can formjacking not happen?

It becomes less likely, but not impossible. PCI SSC includes cases where a payment screen is embedded, because the pages around it can affect payment security. Check once from which screen of your own site a customer proceeds to payment.

Can I be a victim and not notice?

Yes. The typed data is sent out while the screen looks unchanged, so some operators learn of it only through a call from a card company or payment provider. A mechanism that watches payment screen files for changes shortens the time before you notice.

What should I do first if I suspect damage?

Save the payment screen files and logs without deleting them, and change the passwords for the admin screen and the server. Then contact your payment provider and the emergency guide desk. Restoring before the cause is investigated erases the clues.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.