Malicious Code Injection in personal_bug_z3n Package - npm Vulnerability
Summary
MAL-2025-95880: Malicious code in personal_bug_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 personal_bug_z3n package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only undermines the integrity of the npm registry but also poses significant risks to developers who may unknowingly incorporate these malicious packages into their projects.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the personal_bug_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to potential security risks and reputational damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall personal_bug_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 the personal_bug_z3n package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from installing this package until a fix is available.
Conclusion
The personal_bug_z3n package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.
See every vulnerability recorded for personal_bug_z3n →
FAQ
The personal_bug_z3n package is an npm package associated with token reward campaigns that manipulate developer reputation scores.
The malicious code modifies your package.json file, potentially exposing your project to security vulnerabilities and affecting its integrity.
You should remove the personal_bug_z3n package from your project and update your dependencies to ensure your application remains secure.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
