Malicious code in safe-validate (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7501c4aac0734efb1103573bfcd7e85fa6bb251510656c94bc9ceb747c009d2) 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.
AI Analysis
Technical Summary
The 'safe-validate' npm package versions 1.0.1, 1.0.2, 1.0.3, and 1.0.4 have been identified as containing malicious code. Installation or execution of these versions can lead to a full compromise of the affected computer, potentially allowing an attacker to gain complete control. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts.
Potential Impact
Systems with any of the affected 'safe-validate' package versions installed or running are fully compromised. Attackers may have gained complete control over the system, risking exposure and theft of all stored secrets and keys. This necessitates immediate secret/key rotation from a secure environment. The compromise may persist even after package removal.
Mitigation Recommendations
Remove the 'safe-validate' package immediately from all affected systems. Rotate all secrets and keys stored on compromised systems using a separate, trusted computer. Because the system may be fully compromised, consider rebuilding or thoroughly cleaning the affected machines to ensure removal of all malicious software. No official patch or fix is available; the package should be avoided entirely.
Malicious code in safe-validate (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7501c4aac0734efb1103573bfcd7e85fa6bb251510656c94bc9ceb747c009d2) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'safe-validate' npm package versions 1.0.1, 1.0.2, 1.0.3, and 1.0.4 have been identified as containing malicious code. Installation or execution of these versions can lead to a full compromise of the affected computer, potentially allowing an attacker to gain complete control. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts.
Potential Impact
Systems with any of the affected 'safe-validate' package versions installed or running are fully compromised. Attackers may have gained complete control over the system, risking exposure and theft of all stored secrets and keys. This necessitates immediate secret/key rotation from a secure environment. The compromise may persist even after package removal.
Mitigation Recommendations
Remove the 'safe-validate' package immediately from all affected systems. Rotate all secrets and keys stored on compromised systems using a separate, trusted computer. Because the system may be fully compromised, consider rebuilding or thoroughly cleaning the affected machines to ensure removal of all malicious software. No official patch or fix is available; the package should be avoided entirely.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6874
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-xvj3-jjxg-v74h"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c342827e9c797195f9d24
Added to database: 07/06/2026, 23:03:04 UTC
Last enriched: 07/06/2026, 23:23:18 UTC
Last updated: 07/29/2026, 13:51:57 UTC
Views: 26
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.