Which versions of @zva/web are malicious?

The following npm versions of @zva/web are flagged malicious: 99.49.54, 99.50.54, 99.50.55. Treat any of these as compromised.

How do I remediate @zva/web if I installed it?

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

If @zva/web 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 @zva/web part of a known attack campaign?

Yes — @zva/web is associated with the RLMA-2024-06093, RLUA-2024-10415, RLUA-2026-10663 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 @zva/web across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zva/web (3 malicious versions).

Malicious package

@zva/webnpm

Advisory published Oct 16, 2024Updated Sep 24, 2026

@zva/web is a confirmed malicious npm package (MAL-2024-9490) that executes malicious code on install (malicious versions 99.49.54, 99.50.54, 99.50.55). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zva/web (npm)

MAL-2024-9490

Immediate action

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

npm uninstall @zva/web

Malicious versions

3 flagged

99.49.5499.50.5499.50.55

Indicators of compromise (SHA-256)

51206b6382d6cb3f011c90b9178cf99bd8541844166dfcd65b118c8dfb33ba6c

e7730370d76320a7016b4359cb478a8206209738035c1a7fca994edb9f573ebc

3988db43ad4b00098181e211a115d682cb9cea06fcebeb85ab21cefc845591c2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @zva/web (3 malicious versions).
If you installed it — respond
Remove @zva/web 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 @zva/web 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. @zva/web on npm has been identified as a malicious package (versions 99.49.54, 99.50.54, 99.50.55 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06093RLUA-2024-10415RLUA-2026-10663

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @zva/web-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