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

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

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

cards-forms-cards-core-clone establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Yes — cards-forms-cards-core-clone is associated with the IN-MAL-2026-015245 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-cards-core-clone across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cards-forms-cards-core-clone (version 35.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cards-forms-cards-core-clone across your stack and pipelines.

Malicious package

cards-forms-cards-core-clonenpm

cards-forms-cards-core-clone is a confirmed malicious npm package (MAL-2026-12523) that opens a backdoor for remote access (malicious version 35.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cards-forms-cards-core-clone (npm)

MAL-2026-12523

Immediate action

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

npm uninstall cards-forms-cards-core-clone

What this malware does

On require(), index.js loads runtime.js which detects OS and CPU architecture, reconstructs C2 hostnames from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), and downloads a platform-specific executable over HTTPS. If those origins are unreachable, it falls back to a DNS-TXT-based delivery channel that reassembles a base64-encoded payload from numbered subdomains under *.dl.wel1.ru. The fetched binary is written to /tmp or %TEMP% under a disguised name (e.g. dotnet_diag<rand>.exe or.cache_<rand>), chmodded 0755, and spawned detached via /bin/sh -c or cmd /c start. A TTL cache file (/tmp/.analytics_state) suppresses re-detonation on subsequent installs. The package name resembles a legitimate forms/cards library but ships no matching functionality; its only import-time effect is dropper execution.

Malicious versions

1 flagged

35.3.2

Indicators of compromise (SHA-256)

9d987094f38a49c0bb9ae5329e3ff47d97489ee5af348ebc7e056e752cffc1fb

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cards-forms-cards-core-clone (version 35.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cards-forms-cards-core-clone across your stack and pipelines.
If you installed it — respond
cards-forms-cards-core-clone establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If cards-forms-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-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

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

Campaign

IN-MAL-2026-015245

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cards-forms-cards-core-clone-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database