Which versions of next-runtimejs are malicious?

The following npm versions of next-runtimejs are flagged malicious: 1.0.0, 1.0.2, 1.0.3, 1.0.4, 1.1.4. Treat any of these as compromised.

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

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

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

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

Search your lockfiles and build artifacts for next-runtimejs (5 malicious versions).

Malicious package

next-runtimejsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

next-runtimejs is a confirmed malicious npm package (MAL-2026-7327) that executes malicious code on install (malicious versions 1.0.0, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in next-runtimejs (npm)

MAL-2026-7327

Immediate action

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

npm uninstall next-runtimejs

Malicious versions

5 flagged

1.0.01.0.21.0.31.0.41.1.4

Indicators of compromise (SHA-256)

ea91e4732110379c6295af47d523a85180ef24adc496bfa40dc7bfdbcf9e48c7

99c00ba9da49982c3a40a42ed3c60d0292fadcc7534dfc0d995b1e084c9a19cb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05174RLUA-2026-06344

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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