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

> 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.

- **Published:** 2026-06-10T00:00:00Z
- **Last reviewed:** 2026-06-10T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-2169
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-woocommerce-sender-js-stripe-skimmer-tl-2026-2169.webp?v=f9f74e83 (Threadlinqs threat intel: WooCommerce sender.js Payment Skimmer: Detection & IOCs (TL-2026-2169) — High severity, 14 IOCs, 9 detection rules.)
- **ID:** TL-2026-2169
- **Severity:** HIGH
- **Category:** MALWARE
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 14

## Description

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

- T1190 Exploit Public-Facing Application
- T1078 Valid Accounts
- T1505.003 Web Shell
- T1059.007 JavaScript
- T1027 Obfuscated Files or Information
- T1132.001 Standard Encoding
- T1036 Masquerading
- T1056.003 Web Portal Capture

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Checkout Backdoor / Web-Shell + sender.js Implant (SPL)** (`TL-2026-2169-SPL-002`)

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

```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

```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

```yaml
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

- WordPress/WooCommerce Checkout Initial-Access Probing (KQL) (locked: unlock with TL Creds)
- Checkout Backdoor / Web-Shell + [indicator] Implant (KQL) (locked: unlock with TL Creds)
- [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (KQL) (locked: unlock with TL Creds)
- WordPress/WooCommerce Checkout Initial-Access Probing (Sigma) (locked: unlock with TL Creds)
- Checkout Backdoor / Web-Shell + [indicator] Implant (Sigma) (locked: unlock with TL Creds)
- [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (Sigma) (locked: unlock with TL Creds)
- WordPress/WooCommerce Checkout Initial-Access Probing (SPL) (locked: unlock with TL Creds)
- [indicator] Skimmer Active Exfiltration / DOM-Overlay Masquerade (SPL) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Inside a WooCommerce Payment Skimmer: How Carders Moved From Phishing Pages to Checkout Backdoors](https://www.cloudsek.com/blog/woocommerce-payment-skimmer-card-data-theft-checkout-backdoor)
- [ThreatsDay Bulletin: Worm Code Leaked, AI Agent Phished, Claude Code Patch + 28 New Stories](https://thehackernews.com/2026/06/threatsday-bulletin-worm-code-leaked-ai.html)
- [WooCommerce Payment Skimmer Mimics Stripe to Steal Cards at Real Checkouts](https://securityonline.info/woocommerce-payment-skimmer/)
- [Daily Cybersecurity Briefing (11 June 2026)](https://www.cybersecbrief.com/news/cybersec/cybersec-2026-06-11)
- [WooPayments: Integrated WooCommerce Payments — WordPress.org plugin listing](https://wordpress.org/plugins/woocommerce-payments/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-2169
