crypto-validate-lib (npm) · Malicious Code
Affects crypto-validate-libSource GCVE Database
Malicious package : remove crypto-validate-lib and rotate any secrets on hosts that installed it.
Data as of 19 Aug 2026, 14:28 UTC
Malicious package
Published to npm · OSV MAL-2026-10586
What to do
Remove crypto-validate-lib from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmcrypto-validate-lib | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'crypto-validate-lib' versions 1.0.0 through 1.0.3 contains malicious code that executes a hidden payload. After being required, it waits 37 seconds, then decodes a base64 blob from a disguised data file into JavaScript, writes this to a hidden directory in the user's home folder, and executes it as a detached process. It also establishes persistence by adding a cron job on Linux or a scheduled task on Windows, both masquerading as benign Node.js caching mechanisms. This behavior is unrelated to the advertised purpose of the package as a crypto address validator.