Malicious Code Injection in Temporary Bobolink Z3N Package
Summary
MAL-2025-96948: Malicious code in temporary_bobolink_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 'temporary_bobolink_z3n' package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants of itself, often with misleading names.
Vulnerability Detail
The vulnerability originates from the package's malicious design, which includes scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself and other variants, polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to the installation of unwanted or harmful software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall temporary_bobolink_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 workaround, you can avoid using the 'temporary_bobolink_z3n' package altogether. If it is already installed, you can uninstall it using the command: npm uninstall temporary_bobolink_z3n.
Conclusion
The 'temporary_bobolink_z3n' package poses a significant risk due to its malicious design aimed at manipulating the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity.
See every vulnerability recorded for temporary_bobolink_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
Using this package can lead to the installation of unwanted software and compromise the security of your project.
You should uninstall the package immediately using the command: npm uninstall temporary_bobolink_z3n.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly update your packages and use tools like Vulert to monitor for vulnerabilities in your dependencies.
