Malicious Code Injection in specified_bobolink_z3n Package
Summary
MAL-2025-96708: Malicious code in specified_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 specified_bobolink_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the specified_bobolink_z3n package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and potentially compromise the security of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specified_bobolink_z3n
If 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 specified_bobolink_z3n package from your project by executing the following command: npm uninstall specified_bobolink_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The specified_bobolink_z3n package has been identified as containing malicious code that compromises its integrity and the security of the npm registry. It is crucial to take immediate action by updating or removing the package to protect your applications.
See every vulnerability recorded for specified_bobolink_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that depend on this package.
You should update the package to the latest patched version or remove it from your project until a secure version is available.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability.