Malicious Code Injection in content_locust_z3n Package - npm Vulnerability
Summary
MAL-2025-93765: Malicious code in content_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The content_locust_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign linked to the tea.xyz token reward initiative. Its primary function is to facilitate the automatic generation and publishing of derivative packages, which can lead to reputation inflation for developers involved in the campaign. However, this functionality is compromised by the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in the content_locust_z3n package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, potentially leading to security breaches in applications that utilize them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall content_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 content_locust_z3n package altogether. If it is already included in your project, remove it by running: npm uninstall content_locust_z3n. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The content_locust_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for content_locust_z3n →
FAQ
The content_locust_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity by introducing unwanted behavior or dependencies.
You can use the Vulert platform to monitor your package-lock.json file for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
If you have installed the content_locust_z3n package, it is advisable to uninstall it immediately using the command: npm uninstall content_locust_z3n.
Currently, there are no patches available for the content_locust_z3n package. The best course of action is to remove the package from your project.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
