Malicious Code Injection in husky_bobcat-tool: A Threat to npm Packages

husky_bobcat-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103865: Malicious code in husky_bobcat-tool (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The husky_bobcat-tool package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security risks for developers who utilize it.

Vulnerability Detail

The vulnerability in husky_bobcat-tool stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify package.json files, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected packages but also pollutes the npm registry, making it difficult for developers to trust the ecosystem. The malicious payload can lead to unauthorized access and manipulation of projects that rely on these packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall husky_bobcat-tool

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 avoid using husky_bobcat-tool and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The husky_bobcat-tool package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for husky_bobcat-tool →

Share this vulnerability

FAQ

Husky_bobcat-tool is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.

The vulnerability can lead to unauthorized modifications of your project's package.json file and the introduction of potentially harmful code.

You should uninstall the package immediately and check for any other affected packages in your project.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall husky_bobcat-tool

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback