Which versions of callback-hook are malicious?

Every published version of callback-hook on npm is considered malicious. Remove the package entirely.

How do I remediate callback-hook if I installed it?

Remove callback-hook from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed callback-hook — how do I know if it already compromised me?

If callback-hook was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is callback-hook part of a known attack campaign?

Yes — callback-hook is associated with the GHSA-ppjg-6q9j-w45r campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find callback-hook across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for callback-hook (all published versions).

Malicious package

callback-hooknpm

Advisory published Dec 10, 2025Updated Dec 10, 2025

callback-hook is a confirmed malicious npm package (MAL-2025-192404) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in callback-hook (npm)

MAL-2025-192404

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall callback-hook

What this malware does

The package callback-hook was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

1364de9f464fd8aded92e338cbdd79f31c716643bb6fb136bca46a04939132f1

4b89f8889dc19bc6058a5fbd01a2ff7d154ae3229f128981e84a24bdef3f4daf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for callback-hook (all published versions).
If you installed it — respond
Remove callback-hook from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If callback-hook was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. callback-hook on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ppjg-6q9j-w45r

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks callback-hook-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database