Which versions of ovault-evm are malicious?

The following npm versions of ovault-evm are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate ovault-evm if I installed it?

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

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

Yes — ovault-evm is associated with the RLMA-2026-05199, RLUA-2026-06360 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 ovault-evm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ovault-evm (version 99.0.0).

Malicious package

ovault-evmnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in ovault-evm (npm)

MAL-2026-7335

Immediate action

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

npm uninstall ovault-evm

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

7cc29853b5389d3a8caebc24f9a92d9a3b3068821ad4709846f78e25e3862e38

41f367c5e687e14274c3c1f1d73827154341bc8ddb94366113b317ec198d8529

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05199RLUA-2026-06360

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ovault-evm-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