Malicious code in crypto-validate-lib (npm)
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.
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 'crypto-validate-lib' npm package (versions 1.0.0, 1.0.1, 1.0.2, and 1.0.3) contains a self-invoking function that, shortly after loading, reads a base64-encoded payload from a disguised file, decodes it into JavaScript, writes it to a hidden directory in the user's home folder (~/.cache-db/.node-sync/syncd.js), and executes it as a detached Node.js child process. To maintain persistence, it installs a cron job on Linux systems that runs the payload every 12 hours and creates a scheduled task named 'WinNodeSync' on Windows to run it hourly. The naming of the hidden directory and scheduled task is intended to appear as legitimate Node.js caching, masking the malicious activity. This behavior has no relation to the package's stated function as a crypto address validator.
Potential Impact
This malicious package can execute arbitrary code on the affected system with user-level privileges. It establishes persistence mechanisms on both Linux and Windows, enabling ongoing execution of the malicious payload. This can lead to unauthorized system compromise, potential data theft, or further malware deployment. The hidden nature of the files and tasks makes detection more difficult.
Defensive Guidance
No official patch or remediation is currently available for this malicious package. Users should immediately remove 'crypto-validate-lib' versions 1.0.0 through 1.0.3 from their environments. Inspect and remove the hidden directory '~/.cache-db/.node-sync/' and delete the 'WinNodeSync' scheduled task on Windows or the corresponding cron job on Linux to eliminate persistence. Avoid using this package and verify the integrity of npm packages before installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10586
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a85b4c0acd9273b4925243b
Added to database: 08/19/2026, 13:50:56 UTC
Last enriched: 08/19/2026, 14:28:11 UTC
Last updated: 10/03/2026, 05:35:52 UTC
Views: 34
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.