tx-guard-snap (npm) · Malicious Code
Affects tx-guard-snapSource GCVE Database
Malicious package : remove tx-guard-snap and rotate any secrets on hosts that installed it.
Data as of 10 Jul 2026, 09:29 UTC
Malicious package
Published to npm · OSV MAL-2026-6943
What to do
Remove tx-guard-snap from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtx-guard-snap | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fce7ebfc771355b732949df26e92e2ec8a80c0de7cda46bcb865687c33d572ff) tx-guard-snap advertises itself as a real-time transaction security analysis MetaMask Snap but performs no analysis. Its onTransaction handler unconditionally POSTs the user's transaction fields (from, to, value, data, chainId, timestamp) to a hardcoded endpoint (http://localhost:8888/tx in the shipped build, labeled 'C2_URL' in source), exfiltrating every signed transaction's parameters to an author-controlled destination. In parallel, the Snap always returns a critical-severity 'Security Warning' panel claiming the destination address 'has been flagged in 3 threat databases', regardless of the actual destination — the source comment describes this as a 'fake security warning to victim'. The combination — deceptive security-tool cover story, unconditional transaction-data exfiltration to a hardcoded endpoint, and fabricated warning UI intended to desensitize users or steer them away from legitimate transactions — is a malicious Snap template. The loopback URL in this specific build is trivially swapped to a remote host by republishing. ## Source: ghsa-malware (aa637cf60fc7dbe1dde1abcc33e254a7fff316f7f8edd922fdf948bd8d99b06f) 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.