Critical Malicious Code Vulnerability in @huntersofbook/core Package

@huntersofbook/core Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191229: Malicious code in @huntersofbook/core (npm). Affects @huntersofbook/core versions 0.5.1. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @huntersofbook/core package is a Node.js library used in various applications for its core functionalities. It is designed to facilitate specific tasks within the Node.js ecosystem, providing developers with essential tools. However, this package has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from a malicious code injection in the @huntersofbook/core package, specifically version 0.5.1. This package was infected by the Sha1-Hulud: The Second Coming NPM worm, which is designed to steal tokens and credentials from the user's environment. The worm not only propagates itself to other NPM packages owned by the user but also establishes persistence through GitHub actions. Furthermore, it poses a risk of destroying the user's home directory, making it critical for users to act swiftly.

How To Fix

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

npm uninstall @huntersofbook/core

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 measure, users can isolate their development environment by using Docker or similar containerization tools to prevent the malicious code from affecting their main system. Additionally, ensure that sensitive data is stored securely and not accessible to the compromised package.

Conclusion

The @huntersofbook/core package has been compromised by a malicious worm that poses severe risks to users. Immediate action is required to mitigate the impact of this vulnerability. Users should uninstall the package, rotate their credentials, and consider using tools like Vulert for ongoing monitoring.

See every vulnerability recorded for @huntersofbook/core →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys stored on your computer.

The malicious code can steal sensitive tokens and credentials, propagate to other packages, and potentially destroy your home directory.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

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

Always keep your packages updated, regularly audit your dependencies, and use tools to monitor for vulnerabilities.

How To Fix

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

npm uninstall @huntersofbook/core

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