Which versions of jh5o are malicious?

Every published version of jh5o on npm is considered malicious. Remove the package entirely.

How do I remediate jh5o if I installed it?

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

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

Yes — jh5o is associated with the GHSA-rp2f-3wxj-cm3p 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 jh5o 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 jh5o (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jh5o across your stack and pipelines.

Malicious package

jh5onpm

Malicious code in jh5o (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-116

Immediate action

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

npm uninstall jh5o

What this malware does

The package jh5o 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

01eaba01805549a7aa5e246fd04674dd562885c5fa3e0d4a6d30e1595e3fe945

bec5d7cca5e58324cc7dea4623e12ad7bfad0a9ac6812a49373017a13c195a5b

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 jh5o (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jh5o across your stack and pipelines.
If you installed it — respond
Remove jh5o 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 jh5o 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 jh5o 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. jh5o on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rp2f-3wxj-cm3p

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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