Malicious Code Injection in adjacent_marten_z3n: npm Package Vulnerability
Summary
MAL-2025-99183: Malicious code in adjacent_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 adjacent_marten_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that serve no legitimate purpose.
Vulnerability Detail
The vulnerability in adjacent_marten_z3n stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall adjacent_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 adjacent_marten_z3n package and monitor your dependencies for any signs of malicious activity. Implementing strict package management practices and using tools like Vulert can help you identify vulnerabilities in your project.
Conclusion
The adjacent_marten_z3n package poses a significant risk due to its malicious code that alters package management files and floods the npm registry. It is crucial for developers to be vigilant about the packages they use and to implement monitoring tools like Vulert to safeguard their projects.
See every vulnerability recorded for adjacent_marten_z3n →
FAQ
adjacent_marten_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can compromise the integrity of your project by introducing malicious code that alters your package management files and inflates reputation scores.
If you have installed adjacent_marten_z3n, you should uninstall it immediately using 'npm uninstall adjacent_marten_z3n' and review your project for any other vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
