Malicious code in wallet-watcher (npm)
Description
The wallet-watcher npm package version 1.0.2 contains malicious code that scans the user's project files and environment for sensitive information such as BIP-39 mnemonics, private keys, and API keys. This data is encrypted with a hardcoded AES-256-GCM key and exfiltrated to a remote server. The malicious behavior occurs both during installation and at runtime, ensuring continuous data harvesting even if installation scripts are skipped.
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 wallet-watcher npm package (version 1.0.2) includes a postinstall script (src/scan.cjs) that recursively scans files in the user's project directory tree for sensitive credentials including BIP-39 mnemonics, 0x-prefixed 64-hex private keys, and patterns matching secret or API keys. The harvested data is encrypted using AES-256-GCM with a hardcoded 32-byte key and sent to a remote endpoint (https://pkg-delivery-collector.vernal-dabs-tools.workers.dev/ingest) along with a hashed host fingerprint and package name. Additionally, the main ESM entry dynamically imports this scanning module at runtime on every call to getBalances(), ensuring ongoing data exfiltration even if the postinstall hook is bypassed. This client-side encryption conceals the exfiltrated data from network inspection.
Potential Impact
Sensitive credentials such as cryptocurrency wallet mnemonics and private keys, as well as API keys, can be stolen from the user's environment and project files. This compromises the confidentiality of the user's assets and secrets, potentially leading to unauthorized access and theft. The continuous runtime scanning increases exposure risk beyond installation time.
Mitigation Recommendations
No official patch or remediation is currently available. Users should immediately uninstall version 1.0.2 of wallet-watcher and avoid using this package. Review your environment and project files for potential credential exposure and consider rotating any compromised secrets. Monitor for updates from the package maintainer or trusted sources for remediation guidance. Since this is a malicious package, do not rely on the package itself for fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15871
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a9ad4f3acd9273b49b67960
Added to database: 09/04/2026, 14:25:55 UTC
Last enriched: 09/07/2026, 16:23:36 UTC
Last updated: 10/04/2026, 01:42:31 UTC
Views: 19
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.
External Links
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.