Which versions of hrp9872 are malicious?

The following npm versions of hrp9872 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hrp9872 if I installed it?

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

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

Yes — hrp9872 is associated with the GHSA-fc8q-7g22-2mh2 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 hrp9872 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hrp9872 (version 1.0.0).

Malicious package

hrp9872npm

Advisory published Aug 14, 2026Updated Aug 17, 2026

hrp9872 is a confirmed malicious npm package (MAL-2026-14085) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hrp9872 (npm)

MAL-2026-14085

Immediate action

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

npm uninstall hrp9872

What this malware does

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e3863301b783d96a98f60f37331d4a61f921e6dee3c5c35f8788df21da5fd549

Detection & response playbook

Malicious package

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

Campaign

GHSA-fc8q-7g22-2mh2

References

github.com

Detect & block this

O3 blocks hrp9872-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