cards-forms-clone-cards-core-clonenpm
cards-forms-clone-cards-core-clone is a confirmed malicious npm package (MAL-2026-12524) that executes malicious code on install (malicious version 35.4.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cards-forms-clone-cards-core-clone (npm)
What this malware does
On require(), index.js loads platform.js, which selects a platform-specific asset URL from obfuscated hostnames assembled via split-then-join string fragments (oob-worker.cf102-baf.workers.dev, cf103-070, cf99-9b3, cf100-416 workers.dev hosts, plus a DNS-TXT chunked fallback to *.dl.wel1.ru), downloads the payload, writes it to a hidden temp file, chmods it 0755 (or names it dotnet_diag*.exe on Windows), and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A stamp file named.analytics_state and env gates DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK provide a telemetry cover story; the package's advertised purpose is a base framework module unrelated to any such behavior. String-fragment obfuscation of the destination hosts and the masquerading filenames are deliberate evasion.
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-clone-cards-core-clone (version 35.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cards-forms-clone-cards-core-clone across your stack and pipelines.
If you installed it — respond
Remove cards-forms-clone-cards-core-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-clone-cards-core-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-clone-cards-core-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-clone-cards-core-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.