Which versions of wallet-monitor-snap are malicious?

The following npm versions of wallet-monitor-snap are flagged malicious: 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate wallet-monitor-snap if I installed it?

wallet-monitor-snap 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-monitor-snap — how do I know if it already compromised me?

If wallet-monitor-snap 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-monitor-snap part of a known attack campaign?

Yes — wallet-monitor-snap is associated with the IN-MAL-2026-015993, IN-MAL-2026-015992 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-monitor-snap 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-monitor-snap (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-monitor-snap across your stack and pipelines.

Malicious package

wallet-monitor-snapnpm

wallet-monitor-snap is a confirmed malicious npm package (MAL-2026-13393) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wallet-monitor-snap (npm)

MAL-2026-13393

Immediate action

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

npm uninstall wallet-monitor-snap

What this malware does

wallet-monitor-snap is a MetaMask Snap whose onRpcRequest handler implements a 'showSecurityAlert' method that opens a snap_dialog inside MetaMask's trusted UI, tells the user their account has 'unusual activity', and prompts them to enter their Secret Recovery Phrase. The typed BIP-39 mnemonic is returned to the invoking dapp as { captured: result }. The snap declares endowment:rpc with dapps: true, so any web origin that can reach the snap can invoke this method and receive the seed phrase. In-source comments explicitly frame the package's advertised 'ping' and 'estimateGas' RPC methods as a cover story: 'Benign ping method so the snap appears legitimate during store review' and 'Gas estimation facade (the "legitimate" cover feature)'. Any HD wallet account derived from the phrase becomes fully controllable by the caller.

Malicious versions

2 flagged

1.0.21.0.4

Indicators of compromise (SHA-256)

5c50a0acdc6be5b64538f83b0c14c3808ea3a57b963233ba32a2d80c3e4cc2c3

8d0ebf8c78988557de084376ed4793bc8ca67d468d1c350ee8242ee2bc7e054c

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-monitor-snap (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-monitor-snap across your stack and pipelines.
If you installed it — respond
wallet-monitor-snap 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-monitor-snap 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-monitor-snap 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-monitor-snap on npm has been identified as a malicious package (versions 1.0.2, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015993IN-MAL-2026-015992

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wallet-monitor-snap-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