Which versions of @validate-pubkey/hex are malicious?

The following npm versions of @validate-pubkey/hex are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate @validate-pubkey/hex if I installed it?

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

If @validate-pubkey/hex 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 @validate-pubkey/hex part of a known attack campaign?

Yes — @validate-pubkey/hex is associated with the GHSA-4f7x-m25q-x292, RLMA-2025-05670, RLUA-2025-06040 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 @validate-pubkey/hex 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 @validate-pubkey/hex (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @validate-pubkey/hex across your stack and pipelines.

Malicious package

@validate-pubkey/hexnpm

Malicious code in @validate-pubkey/hex (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190634

Immediate action

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

npm uninstall @validate-pubkey/hex

What this malware does

The package @validate-pubkey/hex 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.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

6f8ef709a4966e774d65016f58b5e36c55025bd86443d23dc11e837cc563f2fc

05db2afe6b0d7557f2c2153dd15df68ab69667e8402bf92f2b2e2d900eb5728f

15821f9b7e961d4e8653a1d3b77fdd7f85275790a0eaf30f6f3a769aba3417e3

acb86fe2dc7f27799bc3e515e1e35b2a0d3ee4b9273328afa4823c723495c0de

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 @validate-pubkey/hex (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @validate-pubkey/hex across your stack and pipelines.
If you installed it — respond
Remove @validate-pubkey/hex 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 @validate-pubkey/hex 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 @validate-pubkey/hex 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. @validate-pubkey/hex on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4f7x-m25q-x292RLMA-2025-05670RLUA-2025-06040

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @validate-pubkey/hex-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