Which versions of @hash-validator/v2 are malicious?

The following npm versions of @hash-validator/v2 are flagged malicious: 1.22.1, 1.22.2, 1.22.4, 1.22.5, 1.22.7, 1.22.8, 1.22.9, 1.22.10, 1.22.11. Treat any of these as compromised.

How do I remediate @hash-validator/v2 if I installed it?

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

If @hash-validator/v2 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 @hash-validator/v2 part of a known attack campaign?

Yes — @hash-validator/v2 is associated with the GHSA-c4vv-764j-g33q, RLMA-2025-05240, RLUA-2025-05655, RLUA-2025-06026 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 @hash-validator/v2 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 @hash-validator/v2 (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hash-validator/v2 across your stack and pipelines.

Malicious package

@hash-validator/v2npm

Malicious code in @hash-validator/v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47916

Immediate action

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

npm uninstall @hash-validator/v2

What this malware does

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.

Malicious versions

9 flagged

1.22.11.22.21.22.41.22.51.22.71.22.81.22.91.22.101.22.11

Indicators of compromise (SHA-256)

be7ccca438d061fd1d98fb1061421f517bccb37ba164e017caf7b8f8db366e2e

3954d380ae7d9add7c5483e32fc7fde7725cd392b7bce2e2be66f926fcd78f9e

b9e7f9e58caeb06abb13652bf2272170e95ec6c232af3f795f2096941860c937

309238b49db3c8b577825117b98afd571a682a3700a673622924efd4007bca51

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 @hash-validator/v2 (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hash-validator/v2 across your stack and pipelines.
If you installed it — respond
Remove @hash-validator/v2 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 @hash-validator/v2 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 @hash-validator/v2 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. @hash-validator/v2 on npm has been identified as a malicious package (versions 1.22.1, 1.22.2, 1.22.4, 1.22.5, 1.22.7, 1.22.8, 1.22.9, 1.22.10, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c4vv-764j-g33qRLMA-2025-05240RLUA-2025-05655RLUA-2025-06026

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @hash-validator/v2-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