Which versions of hammer-jquery are malicious?

The following npm versions of hammer-jquery are flagged malicious: 0.0.1-security, 99.0.0, 99.9.0. Treat any of these as compromised.

How do I remediate hammer-jquery if I installed it?

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

If hammer-jquery was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is hammer-jquery part of a known attack campaign?

Yes — hammer-jquery is associated with the GHSA-732r-c6r2-x55r, RLMA-2026-01340 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 hammer-jquery across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hammer-jquery (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hammer-jquery across your stack and pipelines.

Malicious package

hammer-jquerynpm

Malicious code in hammer-jquery (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-521

Immediate action

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

npm uninstall hammer-jquery

What this malware does

The package hammer-jquery 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

3 flagged

0.0.1-security99.0.099.9.0

Indicators of compromise (SHA-256)

72eb1b0f96efc21e3317dc341fbe50547a0d31332d3fc8470fc5a6c1c85053be

c0e80d8bb4c65368f8c47250020a44866a9d32f6182fb7b5f2aed113723d35d8

b2092385b4f1a8c488df14fbba240ba128a2f2190bb5e776562b5b643f518b61

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hammer-jquery (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hammer-jquery across your stack and pipelines.
If you installed it — respond
Remove hammer-jquery 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 hammer-jquery was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks hammer-jquery before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. hammer-jquery on npm has been identified as a malicious package (versions 0.0.1-security, 99.0.0, 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-732r-c6r2-x55rRLMA-2026-01340

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks hammer-jquery-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