Malicious Code Injection in peculiar_bee_z3n Package - npm Vulnerability
Summary
MAL-2025-89454: Malicious code in peculiar_bee_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 peculiar_bee_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. This package has been identified as part of a broader campaign that exploits npm by flooding the registry with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the peculiar_bee_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to compromised developer environments and potentially expose sensitive data or allow for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall peculiar_bee_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 peculiar_bee_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure no malicious packages are included.
Conclusion
The peculiar_bee_z3n package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package from your projects and monitor your dependencies closely to maintain a secure development environment.
See every vulnerability recorded for peculiar_bee_z3n →
FAQ
The peculiar_bee_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
This vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to further security risks and compromising sensitive data.
If you have installed the peculiar_bee_z3n package, it is crucial to uninstall it immediately and check for any dependencies that may be affected.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.
To prevent future vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert for real-time monitoring.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
