Critical Malicious Code Vulnerability in @validates-sdk/v3 Package

@validates-sdk/v3 Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1940: Malicious code in @validates-sdk/v3 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @validates-sdk/v3 package is a JavaScript library available on npm, designed to facilitate validation processes within applications. It is commonly used in various projects for its ease of integration and functionality. However, this package has been compromised, leading to significant security concerns for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the @validates-sdk/v3 package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to the package being flagged as malicious by security researchers, indicating that it may have been intentionally tampered with to exploit users.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @validates-sdk/v3

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, if you must continue using the package, consider isolating the environment where it is installed and monitor for any suspicious activity. However, the safest approach is to remove the package entirely.

Conclusion

The @validates-sdk/v3 package poses a serious security risk due to embedded malicious code. Users are strongly advised to remove the package and secure their systems by rotating any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @validates-sdk/v3 →

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no patched version available. It is advised to remove the package entirely.

Failing to address this vulnerability could lead to unauthorized access to sensitive data and complete compromise of your system.

It is highly discouraged to use this package due to its malicious nature. Removal is the best course of action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @validates-sdk/v3

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback