How do I remediate ve.zz if I installed it?

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

If ve.zz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ve.zz part of a known attack campaign?

Yes — ve.zz is associated with the RLMA-2025-05977 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 ve.zz across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ve.zz (23 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ve.zz across your stack and pipelines.

Malicious package

ve.zznpm

ve.zz is a confirmed malicious npm package (MAL-2025-49243) that executes malicious code on install (malicious versions 1.0.0, 1.0.5, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ve.zz (npm)

MAL-2025-49243

Immediate action

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

npm uninstall ve.zz

What this malware does

The package ve.zz was found to contain malicious code.

Malicious versions

23 flagged

1.0.01.0.51.1.01.2.01.2.51.7.52.7.54.7.54.7.64.7.74.7.85.0.05.1.05.1.25.1.35.1.45.1.55.1.65.1.75.1.85.2.05.2.15.2.2

Indicators of compromise (SHA-256)

9c8e2a95c2e552463055500ef58802c8dc7f83bd43774593724692cdc43d9a93

2c194102c92211d4bbbf7d81f903322bc8a643b8a4060e70f0a796fb6b211ec4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ve.zz (23 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ve.zz across your stack and pipelines.
If you installed it — respond
Remove ve.zz 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 ve.zz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ve.zz before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ve.zz on npm has been identified as a malicious package (versions 1.0.0, 1.0.5, 1.1.0, 1.2.0, 1.2.5, 1.7.5, 2.7.5, 4.7.5, and 15 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05977

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ve.zz-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