Skip to main content
Mallory
← Back to News
financial-sector-threatcybersecurity-regulationthird-party-vendor-breachdata-exfiltration-method

PCI DSS Compliance Gaps Exposed by Client-Side Payment Skimming and Third-Party Script Risk

Sector Threat Intelligence · 2 sources · Updated 5mo ago · First seen Mar 1, 2026

PCI DSS Compliance Gaps Exposed by Client-Side Payment Skimming and Third-Party Script Risk

Organizations pursuing PCI DSS compliance are being warned that compliance controls alone do not prevent client-side payment data theft, particularly when third-party scripts and outsourced payment flows are involved. Commentary highlights that changes to PCI DSS v4-related guidance (including updated SAQ A language for merchants using PCI-compliant payment service providers) can reduce mandated anti-skimming requirements, increasing the risk that merchants “trust but don’t verify” protections around browser-executed code and third-party dependencies.

Separately, tokenization guidance emphasizes that tokenization is distinct from encryption and is intended to reduce exposure by replacing sensitive values (e.g., PANs) with non-sensitive tokens, potentially reducing PCI scope when implemented correctly. The same guidance cautions that implementation pitfalls are common and that using encryption as a stand-in for tokenization can leave organizations at risk—reinforcing that data protection architecture (e.g., tokenization) and client-side/script visibility controls address different parts of the payment-data threat surface, and both may be necessary to mitigate modern skimming techniques such as MirrorMask targeting select Stripe merchants via script/API redirection and reverse-proxy interception.

Who's targeting your sector?See the actors and campaigns active against you right now.
See sector threats
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Jan 1, 2025 – Apr 1, 2025
  1. Apr 1, 20252y ago

    MirrorMask skimmer targets some Stripe merchants

    In April 2025, some merchants using Stripe were targeted by the MirrorMask digital skimmer. The campaign redirected Stripe scripts and API calls to a fake Stripe site and used a reverse proxy to harvest payment data while preserving a normal checkout experience.

  2. Jan 1, 20252y ago

    PCI DSS SAQ A removes requirements 6.4.3 and 11.6.1

    In 2025, PCI DSS SAQ A was changed to remove requirements 6.4.3 and 11.6.1 for merchants that outsource payment processing to PCI DSS-compliant payment service providers. The change reduced explicit anti-skimming and script-monitoring obligations for those merchants under SAQ A.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Malware

1 linked
Do you run this?See the adversaries and campaigns active against your sector right now, ranked by what they're exploiting.
See Your Sector's Threats
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.