Malicious Code Exploit in digital_beetle_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-98677: Malicious code in digital_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
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 package digital_beetle_z3n is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential vector for malicious activities.
Vulnerability Detail
The vulnerability in digital_beetle_z3n arises from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious code by developers who may unknowingly install these packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting the tea protocol token reward system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall digital_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 workaround, avoid using the digital_beetle_z3n package and monitor your dependencies for any unauthorized changes. You can also use tools like Vulert to scan your package-lock.json for vulnerabilities. This can be done without any signup by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The digital_beetle_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for digital_beetle_z3n →
FAQ
digital_beetle_z3n is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the installation of malicious code, which may compromise your project's integrity and security by polluting the npm registry.
You should immediately uninstall the package using 'npm uninstall digital_beetle_z3n' and check your project for any unauthorized changes.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
