Which versions of victoria-wallet-validator are malicious?

The following npm versions of victoria-wallet-validator are flagged malicious: 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate victoria-wallet-validator if I installed it?

victoria-wallet-validator is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed victoria-wallet-validator — how do I know if it already compromised me?

If victoria-wallet-validator 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 victoria-wallet-validator part of a known attack campaign?

Yes — victoria-wallet-validator is associated with the GHSA-9h6m-q36c-7hvg 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 victoria-wallet-validator 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 victoria-wallet-validator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging victoria-wallet-validator across your stack and pipelines.

Malicious package

victoria-wallet-validatornpm

Malicious code in victoria-wallet-validator (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191149

Immediate action

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

npm uninstall victoria-wallet-validator

What this malware does

The package victoria-wallet-validator was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

0.1.10.1.2

Indicators of compromise (SHA-256)

2d71ba531fcca563d58aa99862331b9e31cf7907d0ebfd0312cf6e3e40ba33be

7723f2942b453506f418385891fff056efcbce5ef2db023106c8dd9b508fcbe8

305ff7c4db9d9046f3637aeb746d2f95c58e1083e6fd8cfecf220f9a20911162

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for victoria-wallet-validator (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging victoria-wallet-validator across your stack and pipelines.
If you installed it — respond
victoria-wallet-validator is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If victoria-wallet-validator 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 victoria-wallet-validator 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. victoria-wallet-validator on npm has been identified as a malicious package (versions 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9h6m-q36c-7hvg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks victoria-wallet-validator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring