Malicious Code Injection in religious_locust_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96280: Malicious code in religious_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 'religious_locust_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that aims to manipulate developer reputation scores through the automatic generation and publication of derivative packages. Such practices can lead to a polluted npm registry, affecting developers and users alike.
Vulnerability Detail
The vulnerability in 'religious_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 behavior not only compromises the integrity of the package but also poses a risk of flooding the npm registry with potentially harmful packages. The malicious scripts included in the package are designed to automate these processes, making it difficult for developers to identify and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall religious_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 'religious_locust_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The 'religious_locust_z3n' package poses a significant threat due to its malicious code that can manipulate package metadata and flood the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove the affected package and seek alternatives.
See every vulnerability recorded for religious_locust_z3n →
FAQ
The primary risk is that it contains malicious code that can modify your package.json file and flood the npm registry with harmful packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall religious_locust_z3n' and consider using alternative packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
Using compromised packages can lead to security breaches, data loss, and damage to your application's reputation, making it crucial to regularly audit and update your dependencies.
