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

@seung-ju/react-hooksnpm

Malicious code in @seung-ju/react-hooks (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190757
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @seung-ju/react-hooks

What this malware does

The package @seung-ju/react-hooks 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
0.0.2

Indicators of compromise (SHA-256)

250259b58afbee07591bb7d75ebcda7526cb81964eada7076fb2074b6a97c181
4adf0b1f6ebc35246707044936c68dfe237eb92c6e65e24e87383fcfb2dbe55f
e51a450449a1f50c9ae717696b3aa224304974727c9a57b2dbe4625f0663f123
ed9fd901394e5dc97a5d362ada0ebab5aec2b66f41708d326448cdbf3301882d

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @seung-ju/react-hooks is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @seung-ju/react-hooks 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 @seung-ju/react-hooks 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. @seung-ju/react-hooks on npm has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9xrj-x664-6rgw

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @seung-ju/react-hooks-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring