Malicious Code Injection in many_perch_z3n: A Threat to npm Packages
Summary
MAL-2025-88306: Malicious code in many_perch_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 package 'many_perch_z3n' 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 sharing of code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'many_perch_z3n' originates from its association with a malicious campaign that utilizes scripts to automatically publish numerous derivative packages with altered metadata. These scripts modify the package.json file to remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may introduce vulnerabilities or malicious code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall many_perch_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 'many_perch_z3n' package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'many_perch_z3n' package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regular updates and monitoring tools like Vulert can help mitigate these risks effectively.
See every vulnerability recorded for many_perch_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using compromised packages can lead to security breaches, data loss, or unauthorized access to your application.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories.
Remove the package from your project and replace it with a secure alternative. Ensure to audit your code for any potential security issues.
