evm-validation (npm) · Malicious Code
Affects evm-validationSource GCVE Database
Malicious package : remove evm-validation and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:18 UTC
Malicious package
Published to npm · OSV MAL-2026-14301
What to do
Remove evm-validation 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 |
|---|---|---|
| npmevm-validation | 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 (d3c551a6031e48a54b550a604e2198a4491cf935407744bba8ef0c11c54086c4) The package advertises EVM address validation but performs no local validation. Its single exported function validated(e) in index.js issues axios.get against a hardcoded destination and appends the caller-supplied argument to the URL, causing whatever the consuming application passes in (EVM addresses, keys, or arbitrary user data) to be transmitted to a remote host the caller never configured. The destination is deliberately hidden: a scrambled string array is joined, ROT13-transformed, and reversed at runtime to reconstruct https://api-ivalidte.vercel.app/app/api/ — a typosquat-shaped Vercel host that does not correspond to any documented service for this package. The obfuscation of the destination combined with the mismatch between the advertised purpose (local validation) and the actual behavior (remote relay to an author-controlled endpoint) is the silent-relay shape.