SecurCheckCyber Center
Need help
Back to analysis tools
All cyber threats
Malware

Magecart / web skimmer

Magecart / web skimmer

A web skimmer captures checkout information on a compromised payment form and sends it to an outside endpoint.

Fiche de sensibilisationPrête à diffuser à vos équipes ou clients

MIGHT YOU BE AFFECTED?

Turn knowledge into action.

How does this work?

A web skimmer captures checkout information on a compromised payment form and sends it to an outside endpoint. Investigators should assess actual behaviour, infection context and permissions obtained. Preserve evidence rather than relying on a malware label alone.

REAL-WORLD EXAMPLE

« A modified third-party script reads checkout fields and sends data to an unfamiliar domain. »

Typical sequence

  1. 1Compromise a merchant site or JavaScript dependency.
  2. 2Inject code into its checkout page.
  3. 3Observe fields completed by customers.
  4. 4Copy payment card details as they are entered.
  5. 5Send collected values to an external domain.

Warning signs

  • New third-party checkout script or unexpected change in its integrity.
  • Unknown domain contacted while card fields are entered; customer complaints after purchases.
  • Unusual activity in security logs.
  • Unknown devices, processes or network origins.
  • Unexplained setting or permission changes.
  • Correlated security alerts.
  • Unauthorised access or data modifications.

How to protect yourself

  • Minimise checkout dependencies; enforce an appropriate Content Security Policy and script integrity.
  • Monitor changes to payment pages and their outbound requests.
  • Limit privileges and protect accounts.
  • Patch software and review configurations.
  • Use context-appropriate strong authentication.
  • Monitor and investigate suspicious logs.
  • Train staff to recognise deceptive requests.
  • Keep protected and tested backups.

If you think you are affected

Isolate the affected system if needed, preserve logs and suspicious files, and investigate initial access and exposed accounts. Audit payment scripts; minimise dependencies; use CSP and change monitoring. Check related devices before returning to normal operations. Suspend affected payment flows, preserve evidence, contact the payment provider and evaluate applicable notification obligations.

Get help

Last updated: 8 October 2026