Which versions of wallet-analytics are malicious?

The following npm versions of wallet-analytics are flagged malicious: 1.4.8. Treat any of these as compromised.

How do I remediate wallet-analytics if I installed it?

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.

I already installed wallet-analytics — how do I know if it already compromised me?

If wallet-analytics was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is wallet-analytics part of a known attack campaign?

Yes — wallet-analytics is associated with the IN-MAL-2026-014802 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find wallet-analytics across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wallet-analytics (version 1.4.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-analytics across your stack and pipelines.

Malicious package

wallet-analyticsnpm

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)

MAL-2026-12499

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall wallet-analytics

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.

Malicious versions

1 flagged

1.4.8

Indicators of compromise (SHA-256)

bfc85c0238f90672b0cc329cae3487061924ed5a6458644a97cd90a830ace807

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wallet-analytics (version 1.4.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-analytics across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks wallet-analytics before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. wallet-analytics on npm has been identified as a malicious package (version 1.4.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014802

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database