Malicious Code Injection in active_beaver_z3n: A Threat to npm Packages
Summary
MAL-2025-93109: Malicious code in active_beaver_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 active_beaver_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality through reusable code. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in active_beaver_z3n originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package. The ramifications include potential security risks for developers and users, as well as damage to the reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall active_beaver_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 prevent the installation of this package by avoiding its use in your project. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring access to your code or installation. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The active_beaver_z3n package poses a significant threat 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 monitoring tools like Vulert to stay informed about potential vulnerabilities.
See every vulnerability recorded for active_beaver_z3n →
FAQ
active_beaver_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of applications that depend on this package.
You should uninstall the active_beaver_z3n package immediately and monitor your dependencies for any further vulnerabilities.
Yes, you can use tools like Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign 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.
