Malicious Code Injection in passive_locust_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95853: Malicious code in passive_locust_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 'passive_locust_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'passive_locust_z3n' originates 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 results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for users who inadvertently install these compromised packages. The malicious payload can compromise the integrity of the npm ecosystem by allowing unauthorized access to sensitive data and resources.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall passive_locust_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 'passive_locust_z3n' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'passive_locust_z3n' package poses a significant risk due to its malicious code that alters package metadata and repackages itself. Users are encouraged to update their packages and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and proactive in dependency management is crucial for maintaining application security.
See every vulnerability recorded for passive_locust_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and repackages the software, leading to potential security risks.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you have installed the package, it is advisable to remove it and update to a secure version or use an alternative package.
While specific exploits have not been detailed, the nature of the vulnerability suggests that it could lead to unauthorized access and data exposure.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security updates in the npm ecosystem.
