cards-forms-credit-clonenpm
cards-forms-credit-clone is a confirmed malicious npm package (MAL-2026-12527) that executes malicious code on install (malicious version 35.9.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cards-forms-credit-clone (npm)
What this malware does
On require('cards-forms-credit-clone'), index.js loads compat.js which downloads a platform-specific binary from obfuscated Cloudflare workers.dev hosts assembled at runtime via string-split concatenation (e.g. ['oo','b-worker.c','f101-adf.workers.dev'].join('')), with a DNS-TXT base64 fallback resolver at sdk.dl.wel1.ru. The fetched binary is written to /var/tmp or %TEMP% under disguised names (.cache<hex> / dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. No pinning, no hash or signature verification; comments frame the behavior as 'analytics'/'telemetry'. Hostname fragmentation and DNS-TXT covert-channel resolution are evasion patterns unrelated to the package's advertised 'cards forms' purpose. Any installer that requires this package is subjected to remote code execution under attacker control.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cards-forms-credit-clone (version 35.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cards-forms-credit-clone across your stack and pipelines.
If you installed it — respond
Remove cards-forms-credit-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-credit-clone was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks cards-forms-credit-clone before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cards-forms-credit-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.