Which versions of validator-node are malicious?

The following npm versions of validator-node are flagged malicious: 3.3.4. Treat any of these as compromised.

How do I remediate validator-node if I installed it?

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

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

Yes — validator-node is associated with the GHSA-hxf9-58r2-q8f4, RLMA-2025-06520 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 validator-node 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 validator-node (version 3.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging validator-node across your stack and pipelines.

Malicious package

validator-nodenpm

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

MAL-2025-190498

Immediate action

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

npm uninstall validator-node

What this malware does

The package validator-node 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

1 flagged

3.3.4

Indicators of compromise (SHA-256)

d3f7ef04f70e6978a9f771255f136d634d2907c42c7acf71a42c4c93e7e5d333

83e37a6017e345fd411d1589cfff26c773d65d94f231505eae6ca3a90b448c4a

6a145d3477b2468b39efee0ea16d1b2356988e2b894d19caa52a1723bf20565b

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

Campaign

GHSA-hxf9-58r2-q8f4RLMA-2025-06520

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks validator-node-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