Critical Malicious Code Vulnerability in callback-hook Package

callback-hook Updated 10 Dec 2025

Summary

10/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192404: Malicious code in callback-hook (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 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 callback-hook package is an npm library used for managing callback functions in JavaScript applications. It allows developers to easily handle asynchronous operations by providing a straightforward way to register and invoke callbacks. However, this package has been compromised, leading to significant security concerns for any application that relies on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the callback-hook package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, and it poses a severe risk to the integrity and confidentiality of affected systems.

How To Fix

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

npm uninstall callback-hook

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 workaround, if your application relies on the functionality provided by callback-hook, consider using alternative libraries that offer similar capabilities without the associated risks. Always ensure to review the security history of any package before integrating it into your project.

Conclusion

The callback-hook package has been identified as containing malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for callback-hook →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall callback-hook' and rotate any secrets or keys stored on the affected machine.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

No, there is currently no patched version available for the callback-hook package. The only solution is to remove it entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive information, potential data breaches, and complete compromise of the affected system.

It is highly discouraged to use callback-hook due to its malicious nature. Instead, consider finding alternative libraries that provide similar functionality.

How To Fix

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

npm uninstall callback-hook

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