Which versions of cards-forms-credit-clone are malicious?

The following npm versions of cards-forms-credit-clone are flagged malicious: 35.9.5. Treat any of these as compromised.

How do I remediate cards-forms-credit-clone if I installed it?

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.

I already installed cards-forms-credit-clone — how do I know if it already compromised me?

If cards-forms-credit-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.

Is cards-forms-credit-clone part of a known attack campaign?

Yes — cards-forms-credit-clone is associated with the IN-MAL-2026-015254 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find cards-forms-credit-clone across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cards-forms-credit-clone (version 35.9.5).

Malicious package

cards-forms-credit-clonenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-12527

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall cards-forms-credit-clone

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

1 flagged

35.9.5

Indicators of compromise (SHA-256)

2cf698916c071bb43228f0e40bbb5fc10c2c35c495e091c0b3d1cf1c10e8eb26

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cards-forms-credit-clone (version 35.9.5).
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 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

No. cards-forms-credit-clone on npm has been identified as a malicious package (version 35.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015254

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database