Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ahooks-3.7.8npm

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

MAL-2026-10620
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ahooks-3.7.8

What this malware does

Package published as ahooks-3.7.8 at version 13.1.1 with empty author/description/license impersonates the legitimate ahooks React hooks library. package.json declares a preinstall hook that runs node index.js, which collects the installer's hostname, platform, architecture, username/uid/gid/shell, home directory, current working directory, and the output of whoami and id, and POSTs the JSON to the hardcoded Burp Collaborator subdomain https://q7y246t0aca8jr8vfs8c900s4jaay1mq.oastify.com/detox56. The script auto-executes on npm install without any user interaction.

Malicious versions

1 flagged
13.1.1

Indicators of compromise (SHA-256)

c6816bbe8dc3e7d033a03452f7c1e8f873b97c158165faa863694ee13eb6dd61

Detection & response playbook

Typosquat
  1. Find it

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

  2. If you installed it — respond

    ahooks-3.7.8 is a typosquat — you almost certainly intended a legitimately-named package. Remove ahooks-3.7.8, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If ahooks-3.7.8 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.

  4. How O3 protects you

    O3 blocks ahooks-3.7.8 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. ahooks-3.7.8 on npm has been identified as a malicious package (version 13.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010563

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ahooks-3.7.8-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.