wallet-analyticsnpm
Advisory published Updated
wallet-analytics is a confirmed malicious npm package (MAL-2026-12499) that steals credentials and exfiltrates sensitive data (malicious version 1.4.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in wallet-analytics (npm)
What this malware does
index.js exports a getPlugin function that issues an HTTPS request to a hardcoded bare-IP endpoint at https://46.183.25.232:45000/icons/<n> and passes the response's credits field to new Function('require','module',...,data.credits), invoking the returned function with a live require, process, and Buffer in scope. Any consumer that loads the package's default export executes attacker-supplied JavaScript with full Node privileges on the host. The C2 URL is assembled from split literals (protocol/separator/domain/path) alongside a decoy setDefaultModule that constructs cdnjs font-awesome URLs, disguising the traffic as icon-CDN requests, and the authorization header is spelled bearrtoken to further avoid casual inspection. Declared dependencies (@primno/dpapi for Windows DPAPI unwrap, better-sqlite3, node-machine-id) are consistent with follow-on wallet and browser-secret harvesting delivered by the remote payload.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for wallet-analytics (version 1.4.8).
If you installed it — respond
wallet-analytics is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wallet-analytics was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks wallet-analytics-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.