Which versions of nchain-clone are malicious?

The following npm versions of nchain-clone are flagged malicious: 3.3.5. Treat any of these as compromised.

How do I remediate nchain-clone if I installed it?

Remove nchain-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 nchain-clone — how do I know if it already compromised me?

If nchain-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 nchain-clone part of a known attack campaign?

Yes — nchain-clone is associated with the RLMA-2026-01443 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 nchain-clone across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nchain-clone (version 3.3.5).

Malicious package

nchain-clonenpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

nchain-clone is a confirmed malicious npm package (MAL-2026-1795) that executes malicious code on install (malicious version 3.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nchain-clone (npm)

MAL-2026-1795

Immediate action

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

npm uninstall nchain-clone

What this malware does

The package nchain-clone was found to contain malicious code.

Malicious versions

1 flagged

3.3.5

Indicators of compromise (SHA-256)

5d8348156b4d40ff033d09046ce5115e49eb3c73e3899e92e861cba0495205f0

eac539849e0053adcf6d0d4967489d0b945897e27f64928ad5ed80b097fff8ee

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nchain-clone (version 3.3.5).
If you installed it — respond
Remove nchain-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 nchain-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. nchain-clone on npm has been identified as a malicious package (version 3.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01443

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nchain-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