Which versions of web3-runtime-engine are malicious?

The following npm versions of web3-runtime-engine are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate web3-runtime-engine if I installed it?

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

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

Yes — web3-runtime-engine is associated with the RLMA-2026-05362, RLUA-2026-06547 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 web3-runtime-engine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for web3-runtime-engine (version 1.0.3).

Malicious package

web3-runtime-enginenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

web3-runtime-engine is a confirmed malicious npm package (MAL-2026-7437) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web3-runtime-engine (npm)

MAL-2026-7437

Immediate action

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

npm uninstall web3-runtime-engine

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

0a145131ffbe4ff9ff6024ba38035ea50509e942b0d376a35f233cbdd533ca6d

cfc8cfc16f86c0ee8857ae1850258b2b44e1cf3ac960ff0d5ea78994595454cb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05362RLUA-2026-06547

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks web3-runtime-engine-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