Malicious Code Vulnerability in nchain-clone Package

nchain-clone Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1795: Malicious code in nchain-clone (npm). Affects nchain-clone versions 3.3.5. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The nchain-clone package is a JavaScript library available through npm, primarily used for blockchain-related functionalities. It allows developers to interact with various blockchain networks and implement smart contracts. However, this package has been identified to contain malicious code that can compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the nchain-clone package arises from the inclusion of malicious code that can execute unauthorized actions within the user's environment. This issue is traced back to version 3.3.5 of the package, which was flagged by security researchers at ReversingLabs. The ramifications of this vulnerability include potential data breaches, unauthorized access to sensitive information, and the possibility of the affected application being used as a vector for further attacks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nchain-clone

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can remove the nchain-clone package from your project until a secure version is released. You can do this by running the command: 'npm uninstall nchain-clone'. This will prevent any malicious code from executing in your application.

Conclusion

The nchain-clone package has been identified to contain malicious code, posing significant security risks to applications using it. It is crucial to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor your applications for vulnerabilities effectively.

See every vulnerability recorded for nchain-clone →

Share this vulnerability

FAQ

nchain-clone is a JavaScript library used for interacting with blockchain networks and implementing smart contracts.

The vulnerability was discovered by security researchers at ReversingLabs, who identified malicious code in version 3.3.5 of the package.

The risks include unauthorized access to sensitive data, potential data breaches, and the use of the affected application as a launchpad for further attacks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nchain-clone

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback