safe-validate
This report shows the evidence for safe-validate@1.0.4. 4 of 4 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-6874 confirms this npm version as malicious.
Advisory
MAL-2026-6874
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in safe-validate (npm)
Details
The package advertises itself as a zero-dependency TypeScript validation library, but lib/index.js unconditionally requires lib/schema/bootstrap.js at module top level. bootstrap.js stores `require` and `module` on the global object, then uses a custom permutation cipher (function YWG with magic constants 2540575/34950/50568/5954865) to decode two large opaque string blobs and invokes them via `YWG[OSN]` — a deliberately renamed reference to `Function.constructor` — to construct and execute code, finishing with `XZs(7942)` and tagging `global._V = 'A6-Shadow-14'` (a fingerprint associated with a commercial JS protector frequently observed on malicious npm releases). Any consumer that does `require('safe-validate')` triggers this decode-and-eval at import time with full process privileges and access to environment variables and the filesystem. There is no documented feature in a validation library that requires runtime code generation, and the obfuscation wrapper itself (custom cipher + Function.constructor lookup via scrambled property name + side-effect-only module) is the canonical shape of a hidden payload loader. The package additionally claims to be a republish of the legacy `funval` library while being authored by an unrelated account (`deepthought26`, repo `schema-checker`), consistent with reputation-trading to attract installs and upgrades.
## Source: ghsa-malware (e338d458760f94be3b39af3d50af0a15a851596c90d00ae819271fb6796753ff) 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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to safe-validate@1.0.4.
The same advisory and Firewall decision cover 4 recorded versions
1.0.1, 1.0.2, 1.0.3, 1.0.4
The versions list below shows the verdict for each recorded version.
- Avoid installing safe-validate@1.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.