Which versions of zeal-rq-hooks are malicious?

The following npm versions of zeal-rq-hooks are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate zeal-rq-hooks if I installed it?

Remove zeal-rq-hooks 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 zeal-rq-hooks — how do I know if it already compromised me?

If zeal-rq-hooks 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 zeal-rq-hooks part of a known attack campaign?

Yes — zeal-rq-hooks is associated with the IN-MAL-2026-017374 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 zeal-rq-hooks across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zeal-rq-hooks (version 0.0.0).

Malicious package

zeal-rq-hooksnpm

Advisory published Aug 11, 2026Updated Aug 11, 2026

zeal-rq-hooks is a confirmed malicious npm package (MAL-2026-13742) that executes malicious code on install (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zeal-rq-hooks (npm)

MAL-2026-13742

Immediate action

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

npm uninstall zeal-rq-hooks

What this malware does

The package includes canary.js which imports os/http/https and, at line 123, POSTs a JSON body containing os.hostname(), os.userInfo(), process.platform, node/npm version, and cwd to the hardcoded endpoint https://npm-canary.aveliscare.com. The hostname is not associated with the npm registry or a documented publisher and is embedded directly in the package's own shipped code. The collected fields (hostname, username, platform, cwd) are host-identifying reconnaissance data, and the network destination is not user-configurable in the flagged code path.

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

dcf7e926ec85f72f362263a19d4f99c4b215ddd94ed4454c669c3387cacee164

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zeal-rq-hooks (version 0.0.0).
If you installed it — respond
Remove zeal-rq-hooks 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 zeal-rq-hooks 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. zeal-rq-hooks on npm has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017374

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zeal-rq-hooks-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