1. Red
  2. Learn
  3. Ecommerce

Magento malware: find checkout skimmer scripts and respond

Magento malware: where checkout skimmer scripts hide (config rows, CMS blocks, layout XML, files), how to find them, and how to respond. Checked 4 Nov 2026.

By Timothy Lindblom, FounderPublished 4 November 20268 min readHow we check facts
On this page
  1. Who is this for, and what does a skimmer actually do?
  2. Why do file scans find nothing?
  3. Where do injected scripts hide in Magento 2?
  4. What do I do first?
  5. Which credentials do I rotate, and in what order?
  6. Should I add a Content Security Policy?
  7. Am I affected? A three-state self-test
  8. What exact questions should I send my host or agency?
  9. What can the free scan tell me?

A Magento 2 checkout skimmer is usually a small script that lives in the database or in layout configuration, not in a file, which is why file scans miss it. To find it, search CMS blocks, CMS pages and the design configuration rows for script tags, check layout XML for external script sources, and look for PHP files in directories that should hold none. Then rotate credentials.

FactDetailSource
Typical hiding placesDatabase records for headers and footers, CMS blocks, layout templates, XML configuration, and self-restoring copiesSansec research index
A documented caseObfuscated script in the design/footer/absolute_footer row of core_config_data on Magento 2.4.6, plus an unauthorized payment method at checkoutmagento2 #40466
Why file scans miss itThe code is stored in the database, so it survives file-integrity checksmagento2 #40466
A current exploited bugCVE-2026-75650, exploited in the wild per Adobe; first confirmed attack 4 September 2026 per SansecAdobe, Sansec
CISA KEVAdded 8 September 2026CISA
Other Magento entries in KEVCVE-2026-71362, added 24 September 2026, and CVE-2026-48356, added 27 October 2026. See the Adobe Commerce KEV patch checkCISA KEV
Checked4 November 2026this page

Who is this for, and what does a skimmer actually do?

Anyone running Magento Open Source or Adobe Commerce who has had a card-fraud report from a processor, a customer complaint, a warning from a scanner, or an odd payment option at checkout. A skimmer reads what a shopper types into the payment form and sends it to a server the attacker controls. The order still goes through, so nothing looks broken.

This page covers finding it and responding. It does not describe how attackers build one. If you are still deciding whether your store is exposed to the current exploited bug, read StyleSmuggler, CVE-2026-75650 first, because patching and compromise are separate questions.

Why do file scans find nothing?

Because the skimmer is often not a file. In magento2 issue #40466, a reporter on Magento 2.4.6 found an obfuscated script in the core_config_data table at the path design/footer/absolute_footer, and an unauthorized payment method appeared at checkout. The issue noted that code stored in the database persists across page loads and slips past file-integrity checks. The issue was opened on 27 January 2026 and closed on 9 April 2026 without a confirmed root cause, so treat it as an example of where, not of how.

Sansec's research index lists the same families of hiding place across years of write-ups: database records for headers and footers, CMS blocks and layout templates, XML configuration, and mechanisms that put the code back after you delete it. The pattern is old and stable. Where the script sits matters more than which group wrote it.

Where do injected scripts hide in Magento 2?

Work through these in order. Each row is a read-only check.

PlaceWhat to look forHow to lookSource
core_config_data, design rowsA script tag or encoded blob in header or footer fields, such as design/footer/absolute_footerRead-only query on the table, filter on paths starting with design/magento2 #40466
cms_block and cms_pageScript tags or external sources in content; a recent update_time on a block nobody editedQuery both tables for script tags and sort by update_timeIroncart guide
Layout XMLExternal HTTPS script sources added to app/code/*/view/frontend/layout/ or app/design/*/layout/Search those paths for script includes you do not recogniseIroncart guide
pub/static/Obfuscated JavaScript that reads form fields or makes outbound requestsCompare against a fresh deploy of your own buildIroncart guide
pub/ and var/PHP files in directories that should hold none (media, cache, sessions aside)List PHP files under non-code directoriesIroncart guide, Sansec
admin_userAccounts nobody createdCompare the list with your staffIroncart guide
Checkout in a browserScript sources and network requests that are not yours or your processor'sOpen developer tools on the payment step, read the Network tabthis page

The last row catches what the others miss, because the browser shows what shoppers actually receive. Do it on the payment step with your cache cleared, and again from a phone on mobile data. Some skimmers behave differently depending on the visitor.

Take a copy of anything you find, with timestamps, before you remove it. You may need it for your processor, your insurer or a forensic review.

What do I do first?

Order matters. A short version, then the detail.

Response order for a Magento checkout skimmer: preserve evidence, find and remove, close the way in, rotate credentials, tell the processor, monitor 1 Preserveevidence 2 Find andremove 3 Close theway in 4 Rotatecredentials 5 Tell theprocessor 6 Watch thecheckout page Closing the way in comes before rotating, otherwise the new secrets can be read too.
Response order for a suspected Magento checkout skimmer. The order is this page's recommendation; Adobe's own rotation list is in the section below.
  1. Preserve. Snapshot the database and the files before changing anything. Note the time you found each item.
  2. Find and remove. Use the table above. Remove the script and the thing that restores it. Sansec's research describes skimmers that return after deletion, so removal is not the end.
  3. Close the way in. Work out how it got there. Check patch status for the exploited bug, review admin accounts, remove extensions you do not use, and ask who had admin access. The wider Magento hardening checklist covers what to keep in place afterwards.
  4. Rotate. Change what the server could read, in the order below.
  5. Tell the processor. Ask what evidence they need and by when.
  6. Watch. Re-check the checkout page in a browser after a day and after a week.

If you do not have the skills in-house, this step-by-step plan for a hacked site covers who to call and what to keep.

Which credentials do I rotate, and in what order?

Adobe published an ordered list for the StyleSmuggler incident. Its opening words apply to any store you believe was entered. According to Adobe's knowledge base (checked 24 October 2026), rotating the encryption key alone does not invalidate credentials that may already have been exposed.

  • Enable maintenance mode and disable cron
  • Rotate the encryption key
  • Rotate all admin user passwords
  • Deactivate and regenerate REST, SOAP and GraphQL integration tokens
  • Rotate OAuth client secrets for connected applications
  • Rotate payment gateway API credentials at each provider
  • Rotate database credentials, and Fastly credentials if you use it
  • Rotate SSH and deploy keys and service account credentials
  • Rotate API keys for shipping, tax and other extensions
  • Flush the cache, re-enable cron, disable maintenance mode

Rotate each secret at the place it was issued, not only inside Magento. Sansec makes the same point. The general method is in a full credential rotation walkthrough.

Should I add a Content Security Policy?

After cleanup, yes, in a way that lets you see what loads before you block anything. Adobe's developer documentation describes two modes: report-only, which logs violations, and restrict, which blocks them. On payment and checkout pages, restrict mode is the default from 2.4.7 and only allowlisted inline scripts run. You declare allowed hosts in a csp_whitelist.xml file and can set a report endpoint in the admin.

MDN recommends trying a policy with the Content-Security-Policy-Report-Only header before enforcing it, and describes reporting with report-to. Reports are useful here for a second reason: a new script source on the payment page shows up in them.

A policy limits where scripts may load from and send data to. It does not remove a script on a host you already allowed, and an attacker with admin access can change the policy.

If you take cards on your own page, PCI DSS requirements 6.4.3 and 11.6.1 deal with payment-page scripts and change detection, and what they mean for a small store is written out separately. The PCI Council's FAQ of 28 February 2025 covers payment-page script protection for merchants answering SAQ A (iframe versus redirect checkouts are treated differently), and refers to those two requirements. The standard itself is in the PCI document library; check with your acquirer which questionnaire applies.

Am I affected? A three-state self-test

Where you stand right now

A scan from outside can see what a shopper's browser is given and which version your store reports. It cannot read your database, your layout files or your server.

  1. Detected You or a tool saw an unfamiliar script source, an extra payment option, or a Magento version below the fix for an exploited bug. Treat the store as possibly compromised. Preserve evidence, then follow the order above.
  2. Unknown You have no report and no sign, but nobody has searched the database, CMS content and layout. This is the common case. Run the table above and read the checkout in a browser. Ask your host or agency for patch status with a date.
  3. Confirmed by owner evidence You have a dated search of the database, CMS content, layout and non-code directories, a patch record, and the rotation completed at each source. What you found is documented. Keep watching the checkout page, since a skimmer can return.

No scan, ours included, moves you from "unknown" to "confirmed".

What exact questions should I send my host or agency?

For [your store]: has anyone searched core_config_data design rows, cms_block, cms_page and layout XML for script tags or external script sources, and on what date? Which PHP files exist under pub/ and var/ that are not part of our build? Which Adobe security patches are applied, with their dates? Which admin accounts exist and who created them? Has a server-side malware scan been run, and can we have its output?

Our payment processor or acquirer has asked for evidence about script protection on our payment page. Which Content Security Policy is deployed on checkout, is it in report-only or restrict mode, and where do reports go?

Ask for dates in writing. "We checked" without a date does not tell you whether the check came before or after the code appeared.

What can the free scan tell me?

The free scan identifies the technologies your site serves and matches each version to known vulnerabilities. It also reads security headers, including the CSP. It is a lookup: it can say a version is affected, not whether your setup is exposed. It does not read your database or your server, so it cannot find a skimmer stored there.

The full scan is $100 per scan. An AI red team lists what it can reach from outside, ranks paths, proves access once with evidence, stops, and writes up the path and the fix. For what a scan from outside cannot prove, see the limits of an outside-in scan. For the wider October picture for shops and the other ecommerce guides, see October 2026 incidents for ecommerce stores.

Questions people ask

Magento malware: how do I find the offending files?

Often there is no file. Skimmers are regularly stored as database rows, in CMS blocks or in layout and design configuration, so a file-integrity check finds nothing. Search the database and the layout for script tags and external script sources first, then look for PHP files in directories that should hold none.

My file scan says nothing is wrong but customers report card fraud. Why?

A file scan only reads files. One reporter on Magento 2.4.6 found the script in a design configuration row in the database, with an extra payment method showing at checkout. Check the database, the CMS content and what the checkout page loads in a real browser.

Can I just delete the script and carry on?

Deleting the script is one step. Sansec's research describes skimmers that restore themselves after deletion, so find what put it there, change every credential an attacker could have read, and watch the page afterwards. Take a copy of the evidence before you change anything.

Do I have to tell my payment processor and customers?

Probably, and your processor or acquirer contract will say how fast. Tell them early and ask what evidence they want. Customer notification duties depend on where you and your customers are based, so check the breach rules for each market you sell to.

Will a Content Security Policy stop a skimmer?

It can stop a skimmer loading from, or sending data to, a domain you have not allowed. It does not remove a script that is already allowed, and a store that has been entered can change its own policy. Treat it as a second layer after cleanup, tested in report-only mode first.

How do I know whether my store was breached through a Magento bug?

From outside you cannot tell. Check whether the store ran an affected version unpatched, for example during the StyleSmuggler window from 4 September 2026, and ask your host or agency for the patch status with dates. Weak admin passwords and malicious extensions are other common routes.

Sources

  1. magento/magento2 issue #40466: injected script in core_config_data and an unauthorized payment method (GitHub)A reporter on Magento 2.4.6 found an obfuscated script in the design/footer/absolute_footer row. Opened 27 January 2026, closed 9 April 2026.
  2. Sansec research index: Magento payment skimmer write-upsLists database records (headers and footers), CMS blocks, layout templates and XML configuration as recurring hiding places, plus skimmers that restore themselves.
  3. Sansec: StyleSmuggler, Magento and Adobe Commerce zero-day (CVE-2026-75650)Timeline, indicators of compromise, the advice to scan with eComscan and to rotate credentials at their source.
  4. Adobe security bulletin APSB26-146 (7 September 2026)Adobe states CVE-2026-75650 is exploited in the wild.
  5. Adobe Experience League: urgent action required for APSB26-146Adobe's ordered rotation list and the statement that rotating the encryption key alone does not invalidate credentials already exposed.
  6. CISA Known Exploited Vulnerabilities catalog entry for CVE-2026-75650Added 8 September 2026, due date 11 September 2026.
  7. CISA alert: CISA Adds Four Known Exploited Vulnerabilities to Catalog (8 September 2026)
  8. Adobe developer docs: Content Security Policies in Adobe CommerceReport-only and restrict modes, csp_whitelist.xml, the report URI setting, and restrict mode by default on payment pages from 2.4.7.
  9. Adobe developer docs: Commerce security topicsIndex of Adobe's own guidance on cross-site scripting, file uploads and sensitive information.
  10. PCI SSC blog: FAQ clarifies new SAQ A eligibility criteria for e-commerce merchants (28 February 2025)Payment-page script protection, referencing PCI DSS requirements 6.4.3 and 11.6.1.
  11. PCI Security Standards Council document library (PCI DSS v4.0.1)Where the current standard is published.
  12. MDN: Content Security Policy (CSP)Content-Security-Policy-Report-Only and the report-to directive.
  13. MDN: Content Security Policy implementation guideRecommends testing a policy in report-only mode before enforcing it.
  14. Ironcart: Magento incident response guide (practitioner guide, not a vendor advisory)Names cms_block, cms_page, admin_user, layout XML and non-code directories as places to audit. Used for the checklist, not for any incident fact.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.