Which versions of vaildator are malicious?

The following npm versions of vaildator are flagged malicious: 13.15.15, 13.15.16, 13.15.17, 13.15.18. Treat any of these as compromised.

How do I remediate vaildator if I installed it?

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

If vaildator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vaildator part of a known attack campaign?

Yes — vaildator is associated with the RLMA-2025-04722, RLUA-2025-05975 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 vaildator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vaildator (4 malicious versions).

Malicious package

vaildatornpm

Advisory published Aug 14, 2025Updated Dec 2, 2025

vaildator is a confirmed malicious npm package (MAL-2025-38045) that executes malicious code on install (malicious versions 13.15.15, 13.15.16, 13.15.17…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vaildator (npm)

MAL-2025-38045

Immediate action

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

npm uninstall vaildator

What this malware does

The package vaildator was found to contain malicious code.

Malicious versions

4 flagged

13.15.1513.15.1613.15.1713.15.18

Indicators of compromise (SHA-256)

707820036e8687cf54114876067fb412f4b14b2018854e6fbb7c2294a740e9b8

06878c30dfeb1110c58e035ff62cd15347c5746fe37a13f76751289f48387f1c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vaildator (4 malicious versions).
If you installed it — respond
Remove vaildator 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 vaildator was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vaildator on npm has been identified as a malicious package (versions 13.15.15, 13.15.16, 13.15.17, 13.15.18 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04722RLUA-2025-05975

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vaildator-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