Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@validates-sdk/v3npm

Malicious code in @validates-sdk/v3 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1940
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @validates-sdk/v3

What this malware does

The package @validates-sdk/v3 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

2 flagged
1.22.161.22.17

Indicators of compromise (SHA-256)

f759df64c23df9ef2aa637105c8a5a6682307bc1e52c84546139c70165d86efe
14f6dc99183ad11d3293d19966af14cd33cf7ed4ad00f3de9d6f07e5842a9234
53bd2f45a544545a31d46ff39cd8e1ce72bf1609fc9d26ca3cfb9ce8b9ad3fbe
af2432ee541349745d2b3511aff32c6dda70e530e5d54f08c7ea4e9b8a88b05a

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @validates-sdk/v3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @validates-sdk/v3 across your stack and pipelines.

  2. If you installed it — respond

    Remove @validates-sdk/v3 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.

  3. Did it already run?

    If @validates-sdk/v3 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.

  4. How O3 protects you

    O3 blocks @validates-sdk/v3 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. @validates-sdk/v3 on npm has been identified as a malicious package (versions 1.22.16, 1.22.17 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6rj6-xwm6-v698RLMA-2026-01708RLUA-2026-01870

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @validates-sdk/v3-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.

@validates-sdk/v3 (npm) malicious package — MAL-2026-1940 | O3 Security