cards-forms-debit-clonenpm
Advisory published Updated
cards-forms-debit-clone is a confirmed malicious npm package (MAL-2026-12528) that executes malicious code on install (malicious version 35.2.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cards-forms-debit-clone (npm)
What this malware does
On require(), index.js loads shim.js which downloads a platform-specific binary from anonymous *.workers.dev subdomains (hostnames assembled at runtime by joining split string fragments to evade static matching), writes the bytes to /tmp or %TEMP% under disguised names (".cache<hex>" on Unix, "dotnet_diag_<hex>.exe" on Windows), chmods 0755, and spawns the binary detached via child_process.spawn("/bin/sh") or spawn("cmd"). If HTTPS retrieval fails, a DNS TXT fallback channel against *.dl.wel1.ru reads a chunk count from c.<domain>, iterates N subdomains to reassemble a base64-encoded payload, and executes the decoded bytes. No signature or hash verification is performed, the fetched content is opaque, and the routine is labeled "telemetry" as a cover story with a nominal opt-out. The behavior fires on any import of the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for cards-forms-debit-clone (version 35.2.3).
If you installed it — respond
Remove cards-forms-debit-clone from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cards-forms-debit-clone was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cards-forms-debit-clone-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.