Malicious Code Injection in practical_marten_z3n: npm Package Vulnerability
Summary
MAL-2025-95965: Malicious code in practical_marten_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The practical_marten_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious code embedded within this package is designed to manipulate package metadata, thereby affecting the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the practical_marten_z3n package, which is linked to a broader malicious campaign targeting npm. The package contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. This behavior not only compromises the reputation of developers but also poses a risk to users who may inadvertently install these malicious packages. The payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to potential security risks and instability within applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall practical_marten_z3nIf 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 avoid using the practical_marten_z3n package altogether. If it is already included in your project, remove it by executing the following command: npm uninstall practical_marten_z3n. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The practical_marten_z3n package poses a significant risk due to its malicious code designed to manipulate npm registry data. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for practical_marten_z3n →
FAQ
practical_marten_z3n is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.
The vulnerability can lead to the installation of malicious packages, compromising the security and integrity of your application.
You should uninstall the practical_marten_z3n package immediately using the command: npm uninstall practical_marten_z3n.
Currently, there is no specific patch for the practical_marten_z3n package. It is recommended to remove the package from your project.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
