Malicious Code Injection in frightened_bear_z3n Package
Summary
MAL-2025-102938: Malicious code in frightened_bear_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 frightened_bear_z3n package is part of the npm ecosystem, often utilized in JavaScript projects. It is typically involved in token reward campaigns, which can lead to the proliferation of derivative packages. This package has been identified as part of a malicious scheme that aims to inflate developer reputation scores through automated publishing of compromised packages.
Vulnerability Detail
The vulnerability originates from the package being linked to the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious payload alters 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 a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall frightened_bear_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 remove the frightened_bear_z3n package from your project by executing the command: 'npm uninstall frightened_bear_z3n'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The frightened_bear_z3n package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for frightened_bear_z3n →
FAQ
frightened_bear_z3n is an npm package associated with token reward campaigns that have been found to contain malicious code.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.
Using compromised packages can lead to unauthorized access, data breaches, and the potential for your application to be used in malicious activities.
Yes, you can use tools like Vulert to monitor your dependencies for vulnerabilities without needing to access the code or install additional software.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
