Which versions of hover-design-prototype are malicious?

The following npm versions of hover-design-prototype are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate hover-design-prototype if I installed it?

hover-design-prototype 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.

I already installed hover-design-prototype — how do I know if it already compromised me?

If hover-design-prototype 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 hover-design-prototype part of a known attack campaign?

Yes — hover-design-prototype is associated with the GHSA-qv6c-x8r4-46ff 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 hover-design-prototype 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 hover-design-prototype (version 0.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hover-design-prototype across your stack and pipelines.

Malicious package

hover-design-prototypenpm

Malicious code in hover-design-prototype (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190965

Immediate action

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

npm uninstall hover-design-prototype

What this malware does

The package hover-design-prototype 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.5

Indicators of compromise (SHA-256)

99f0db16f29cd20815ef8a1bcac3009c563f068ce10c240f365d0daefdbe690a

db96c13324b014e92e639e93401c356c60bdd7d020bc22c5327900ccbab0220a

49acc9f0bb88e0cdb23e9c45d2e1bb7448201237c016963545fe34cde54e022e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hover-design-prototype (version 0.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hover-design-prototype across your stack and pipelines.
If you installed it — respond
hover-design-prototype 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.
Did it already run?
If hover-design-prototype 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 hover-design-prototype 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. hover-design-prototype on npm has been identified as a malicious package (version 0.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qv6c-x8r4-46ff

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hover-design-prototype-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