Malicious Code Injection in arbitrary_beetle_z3n Package - npm Vulnerability
Summary
MAL-2025-93259: Malicious code in arbitrary_beetle_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 arbitrary_beetle_z3n package is part of a series of packages associated with the tea.xyz token reward campaign, which has been known to flood the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in the arbitrary_beetle_z3n package originates from its inclusion in a malicious campaign aimed at inflating developer reputation scores through automated scripts. The package contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall arbitrary_beetle_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 measure, you can avoid using the arbitrary_beetle_z3n package and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and remove any malicious packages.
Conclusion
The arbitrary_beetle_z3n package poses a significant risk due to its malicious code that alters critical project files and repopulates the npm registry with potentially harmful packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for arbitrary_beetle_z3n →
FAQ
It is an npm package that is part of a malicious campaign designed to inflate developer reputation scores by generating and publishing derivative packages.
The vulnerability can lead to the installation of malicious code that modifies your project's files and can potentially compromise your application's security.
You should immediately uninstall the arbitrary_beetle_z3n package and audit your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
