Which versions of h3-next are malicious?

The following npm versions of h3-next are flagged malicious: 99.99.9. Treat any of these as compromised.

How do I remediate h3-next if I installed it?

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

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

Yes — h3-next is associated with the RLMA-2026-01968 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 h3-next across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for h3-next (version 99.99.9).

Malicious package

h3-nextnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

Malicious code in h3-next (npm)

MAL-2026-2768

Immediate action

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

npm uninstall h3-next

What this malware does

The package h3-next was found to contain malicious code.

Malicious versions

1 flagged

99.99.9

Indicators of compromise (SHA-256)

d69e72688f629d7e5d3013109a89146f05d870c76632155ad26dc5c64bd09385

41a779cef19955b279051dff59351c5f041b3834e2c9bd972c0b0be096aa767f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01968

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks h3-next-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