Skip to navigation

Threat reportMalwareTL-2026-2169

WooCommerce Payment Skimmer 'sender.js' Uses Checkout Backdoor to Steal Card Data

highACTIVE

CloudSEK recovered an obfuscated client-side JavaScript skimmer, 'sender.js', from a compromised WooCommerce store running WooCommerce Payments (Stripe). After gaining web-shell access via a vulnerable plugin/theme, exposed admin credentials, or a known CMS flaw, the actor plants a checkout backdoor that loads the skimmer, which overlays a fake Stripe-lookalike payment form to harvest card number, expiry, CVV, and customer email in real time while letting the genuine transaction complete undetected.

Key facts

IdentifiersTL-2026-2169
SeverityHIGH
Affected productsAutomattic / WooCommerce WooCommerce Payments (WooPayments) — Stripe checkout integration for WooCommerce on WordPress
Malwaresender.js (WooCommerce/Stripe checkout skimmer)
Toolsobfuscator.io (or a compatible JavaScript obfuscation toolchain)
MITRE ATT&CK techniquesT1027 Obfuscated Files or Information, T1036 Masquerading, T1056.003 Web Portal Capture, T1059.007 JavaScript, T1078 Valid Accounts, T1132.001 Standard Encoding, T1190 Exploit Public-Facing Application, T1505.003 Web Shell
MotivationFINANCIAL
Target sectorsretail, ecommerce
Detection rules9 (1 shown free)
Sources5 cited sources

Detection coverage

As of 2026-06-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2169 across Splunk SPL, Microsoft KQL and Sigma, covering 14 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Checkout Backdoor / Web-Shell + sender.js Implant (SPL)

Detects PHP web-shell command primitives in request query strings, unauthorized theme/plugin/upload file writes referencing sender.js, wcpay-payment-element, or the _sb rogue-field naming convention, and synthetic-checkout baseline drift showing a newly injected <script> tag — the persistence + obfuscated-JS-execution stage CloudSEK documented between initial access and active skimming.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1505.003, T1059.007, T1027
  • Data sources: file_integrity_monitoring, web_access_logs, synthetic_checkout_monitoring
  • Severity: critical
  • Confidence: high

Splunk SPL

index=web sourcetype=access_combined uri_path="*.php"
| regex uri_query="(?i)(eval\(|base64_decode|passthru|system\(|shell_exec|str_rot13|assert\()"
| eval alert_reason="Possible PHP web-shell invocation via query-string payload (eval/base64_decode/system/shell_exec pattern) — precursor to checkout-backdoor + sender.js drop (T1505.003)"
| table _time src_ip uri_path uri_query status alert_reason
| append
    [ search index=fim sourcetype="fim:wordpress" (file_path="*/wp-content/themes/*" OR file_path="*/wp-content/plugins/*" OR file_path="*wp-content/uploads*")
      | search (file_content="*sender.js*" OR file_content="*wcpay-payment-element*" OR file_content="*_sb*" OR new_file=true)
      | eval alert_reason="Unauthorized theme/plugin/upload file change referencing sender.js / wcpay-payment-element / _sb checkout-backdoor artifacts (T1505.003/T1027)"
      | table _time host file_path action alert_reason ]
| append
    [ search index=web sourcetype="synthetic:checkout" baseline_diff=true (new_script_src="*sender.js*" OR dom_delta="*script*")
      | eval alert_reason="Synthetic checkout scan detected a new/obfuscated <script> tag (possible sender.js execution) not present in the known-good baseline (T1059.007)"
      | table _time host page_url new_script_src alert_reason ]

Microsoft KQL

let SuspiciousPhpParams = dynamic(["eval(", "base64_decode", "passthru", "system(", "shell_exec", "str_rot13", "assert("]);
CommonSecurityLog
| where TimeGenerated > ago(24h)
| where RequestURL has ".php"
| where SuspiciousPhpParams has_any (RequestURL)
| project TimeGenerated, SourceIP, RequestURL, DeviceAction
| union (
    DeviceFileEvents
    | where TimeGenerated > ago(24h)
    | where FolderPath has_any ("wp-content/themes", "wp-content/plugins", "wp-content/uploads")
    | where FileName endswith ".php" or FileName == "sender.js"
    | where ActionType in ("FileCreated", "FileModified")
    | project TimeGenerated, SourceIP=InitiatingProcessAccountName, RequestURL=FolderPath, DeviceAction=ActionType
)
| union (
    SyntheticCheckoutScan_CL
    | where TimeGenerated > ago(24h)
    | where BaselineDiff_b == true and (NewScriptSrc_s has "sender.js" or DomDelta_s has "script")
    | project TimeGenerated, SourceIP=PageUrl_s, RequestURL=NewScriptSrc_s, DeviceAction="synthetic_checkout_diff"
)

Sigma

title: Checkout-Page Backdoor File Drop (sender.js / wcpay-payment-element Skimmer)
id: f4b2d3e5-2a4b-4c8f-9d6e-3b6f0a2c4d22
status: experimental
description: Detects creation or modification of WordPress theme/plugin/upload files that plant a checkout backdoor referencing the sender.js skimmer or its wcpay-payment-element overlay target, or that contain common PHP web-shell primitives, consistent with the CloudSEK-reported WooCommerce Payments checkout-skimmer chain.
references:
  - https://www.cloudsek.com/blog/woocommerce-payment-skimmer-card-data-theft-checkout-backdoor
author: Threadlinqs Team
date: 2026-06-11
tags:
  - attack.persistence
  - attack.t1505.003
  - attack.execution
  - attack.t1059.007
  - attack.defense-evasion
  - attack.t1027
logsource:
  category: file_event
  product: wordpress
detection:
  selection_path:
    TargetFilename|contains:
      - 'wp-content/themes'
      - 'wp-content/plugins'
      - 'wp-content/uploads'
  selection_content:
    FileContent|contains:
      - 'sender.js'
      - 'wcpay-payment-element'
      - '_sb'
      - 'eval('
      - 'base64_decode'
  condition: selection_path and selection_content
falsepositives:
  - Legitimate plugin/theme developer deploying an update that happens to reference similarly-named fields
  - File Integrity Monitoring baseline re-scan flagging a known-good deployment immediately after a sanctioned release
level: high

Known false positives:

  • Legitimate plugin/theme developer deploying an update that references similarly-named fields or uses eval()/base64 for benign minification
  • FIM baseline re-scan flagging a known-good deployment immediately after a sanctioned release

Tuning notes: Maintain a hash-based known-good baseline of theme/plugin/core files and synthetic-checkout DOM snapshots so this fires only on drift; whitelist the CI/CD deploy account and expected release-window file churn.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • WordPress/WooCommerce Checkout Initial-Access Probing (KQL) · unlock with TL Creds
  • Checkout Backdoor / Web-Shell + [indicator] Implant (KQL) · unlock with TL Creds
  • [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (KQL) · unlock with TL Creds
  • WordPress/WooCommerce Checkout Initial-Access Probing (Sigma) · unlock with TL Creds
  • Checkout Backdoor / Web-Shell + [indicator] Implant (Sigma) · unlock with TL Creds
  • [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (Sigma) · unlock with TL Creds
  • WordPress/WooCommerce Checkout Initial-Access Probing (SPL) · unlock with TL Creds
  • [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-06-10, Threadlinqs Intelligence tracks 14 indicators of compromise for TL-2026-2169.

14 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CloudSEK's HUMINT engagements with operators active on carding marketplaces (Savastan0, Cvvhub, Jerrys, Zillion, Proton, VClub, Pepe, and unspecified invite-only forums) surfaced a shift in carder tradecraft: rather than standing up phishing pages that imitate a store, technically capable actors are compromising the legitimate e-commerce site itself and skimming real transactions.

The documented attack chain begins with generic web-application initial access — a vulnerable or outdated plugin/theme, a known CMS vulnerability, or exposed administrator credentials (no specific CVE or product/version was identified by the source). Once inside, the actor plants a web shell, then uses it to place a checkout backdoor: code positioned to execute on the payment page, whether injected into a theme file, a plugin, the database, or loaded from an attacker-controlled host.

That backdoor loads 'sender.js', a heavily obfuscated payload combining obfuscator.io-style string-array rotation with a custom encoding layer (base64, URL escape/unescape, and a per-character string-reversal helper) across two large encoded string-table blobs. On the checkout page, the script waits for the WooCommerce Payments (Stripe) element to render, then injects a DOM overlay that impersonates it — specifically targeting the 'wcpay-payment-element' / 'StripeElement' node — rather than attempting to read the real, cross-origin-protected Stripe iframe. The counterfeit form uses rogue input fields suffixed '_sb' (card-number_sb, expiry_sb, security-code_sb) to capture card number, expiry, CVV, and the customer's email in parallel with the legitimate checkout flow; because the real order still completes normally, the compromise produces no visible failure for the customer or the merchant, and CloudSEK notes dwell time is often measured in months.

Before exfiltration, the skimmer performs the same client-side checks a real checkout would run — Luhn checksum, card-brand/BIN detection, and expiry validation — so that only cards likely to be usable are captured and sent onward, reducing noise for the operator. Captured data is encoded and sent to an attacker-controlled collection endpoint, deduplicated per victim. To blend in, the skimmer stores tracking state under localStorage keys crafted to resemble marketing/analytics artifacts and sets a client-side Google Analytics opt-out flag ('ga-disable-*') to suppress anomalous behavioral-tracking signals around the injected form. CloudSEK's own defensive guidance for merchants centers on checkout-page change detection: CSP with reporting, Subresource Integrity on third-party scripts, file-integrity monitoring of theme/plugin/core files, review of WordPress options/widgets/post content for injected blobs, auditing unexplained 'ga-disable-*' flags, and synthetic checkout testing against a known-good baseline.

According to CloudSEK, freshly validated cards captured this way, along with billing context, are sold on carding marketplaces and forums (Savastan0, Cvvhub, Jerrys, Zillion, Proton, VClub, Pepe), reflecting active, ongoing monetization rather than a one-off proof of concept. No CVE, CVSS score, or specific vulnerable product/version was published by the source; the compromise vector is generic web-application initial access, not a single named vulnerability.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1027 Obfuscated Files or Information; T1036 Masquerading

Collection

T1056.003 Web Portal Capture

Execution

T1059.007 JavaScript

Initial Access

T1078 Valid Accounts; T1190 Exploit Public-Facing Application

Command and Control

T1132.001 Standard Encoding

Persistence

T1505.003 Web Shell

Remediation

Immediate actions

  • Deploy a Content Security Policy (with reporting) that alerts on any new or changed script loading on the checkout page
  • Audit WordPress options, widgets, and post content for injected scripts or encoded blobs
  • Investigate any unexplained 'ga-disable-*' flags and reconcile Google Analytics property IDs against known-good baselines
  • Run synthetic/automated checkout transactions and diff behavior against a known-good baseline to catch a live overlay

Workarounds

  • Prefer wallet/tokenized payment methods (Apple Pay, Google Pay, PayPal) where offered, which are not exposed to a DOM-overlay card-form skimmer
  • Use virtual or single-use card numbers and enable transaction alerts to limit fraud exposure from any single compromised checkout

Longer-term hardening

  • Deploy File Integrity Monitoring (FIM) on theme files, plugins, and WordPress core to catch unauthorized modification
  • Enforce Subresource Integrity (SRI) hashes on third-party checkout scripts to prevent silent tampering
  • Restrict script and outbound-connection sources on the checkout page via CSP to an approved allowlist
  • Harden WordPress admin authentication (MFA, unique strong credentials) to close the exposed-credentials initial-access path
  • Keep all WooCommerce/WordPress plugins and themes patched and remove unused ones to close the vulnerable-plugin/theme initial-access path

Affected and fixed versions

  • Automattic / WooCommerce — WooCommerce Payments (WooPayments) — Stripe checkout integration for WooCommerce on WordPress
    Vulnerable versions: Not version-specific: CloudSEK identified no flaw in WooCommerce Payments itself. Compromise is via generic web-application initial access (vulnerable/outdated plugin or theme, exposed admin credentials, or a known CMS vulnerability) on the surrounding WordPress/WooCommerce store.

Timeline

  • CloudSEK publishes 'Inside a WooCommerce Payment Skimmer: How Carders Moved From Phishing Pages to Checkout Backdoors,' documenting the locked-ioc-1 sample and defensive guidance for merchants.
  • The skimmer captures card number, expiry, CVV, and customer email in parallel with the genuine transaction, validates the card client-side (Luhn checksum, BIN detection, expiry check), and exfiltrates the encoded, deduplicated record to an attacker-controlled endpoint while the real order still completes.
  • The obfuscated 'locked-ioc-1' skimmer loads on the checkout page and injects a DOM overlay impersonating the WooCommerce Payments Stripe element ('wcpay-payment-element' / 'StripeElement'), presenting a look-alike payment form with '_sb'-suffixed rogue input fields.
  • Using the web shell, the actor plants a checkout backdoor, positioning code to execute on the payment page (injected into a theme file, a plugin, the database, or loaded from an attacker-controlled host).
  • Per CloudSEK's analysis, the actor gains initial web-shell access to a WooCommerce store running WooCommerce Payments (Stripe) via a vulnerable/outdated plugin or theme, a known CMS vulnerability, or exposed admin credentials.
  • CloudSEK's HUMINT engagements with operators on carding marketplaces (Savastan0, Cvvhub, Jerrys, Zillion, Proton, VClub, Pepe) surface a shift from standalone phishing pages to direct compromise of legitimate e-commerce checkouts.
  • The Hacker News' ThreatsDay Bulletin, securityonline.info, and Daily Cybersecurity Briefing amplify CloudSEK's findings on the checkout-backdoor skimmer technique.

Sources cited

Previous and next in malware

Drafted by the Threadlinqs research pipeline from 5 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats