Malicious Code Injection in static_bobcat_z3n Package
Summary
MAL-2025-96750: Malicious code in static_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 static_bobcat_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the static_bobcat_z3n package originates from its involvement in a token reward campaign that exploits npm's package publishing system. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted and potentially harmful packages in the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_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 temporary workaround, you can remove the static_bobcat_z3n package from your project by executing: npm uninstall static_bobcat_z3n. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The static_bobcat_z3n package has been identified as a vector for malicious code that can compromise the integrity of npm projects. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your software.
See every vulnerability recorded for static_bobcat_z3n →
FAQ
The static_bobcat_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code can modify your package.json file, remove private flags, and publish unwanted packages, potentially compromising your project's integrity.
If you have installed the static_bobcat_z3n package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package.json and package-lock.json files for any suspicious packages.
