Malicious Code Injection in broken_bobcat_z3n: A Threat to npm Packages
Summary
MAL-2025-93445: Malicious code in broken_bobcat_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 package 'broken_bobcat_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of these packages is compromised due to the presence of malicious scripts that alter package metadata and republish variants, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'broken_bobcat_z3n' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, change version numbers, and generate random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. The ramifications include a compromised npm ecosystem, potential security risks for developers using these packages, and a degradation of trust in the package management system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall broken_bobcat_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 monitor your package dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup. This tool analyzes your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Conclusion
The 'broken_bobcat_z3n' package poses a significant threat due to its malicious code that alters package metadata and repopulates the npm registry with untrustworthy variants. Developers are advised to uninstall the package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for broken_bobcat_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and republish variants, leading to potential pollution of the npm registry.
You can use Vulert's playground at Vulert Scanner to analyze your package-lock.json file for vulnerabilities.
You should uninstall the package immediately using 'npm uninstall broken_bobcat_z3n' and check for any other affected packages.
Yes, using unverified or malicious npm packages can lead to security vulnerabilities, including data breaches and system compromises.
Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities in real-time.
