evm-validationnpm
Advisory published Updated
evm-validation is a confirmed malicious npm package (MAL-2026-14301) that typosquats a legitimate package to trick installs (malicious versions 1.0.2, 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in evm-validation (npm)
What this malware does
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.
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
TyposquatFind it
Search your lockfiles and build artifacts for evm-validation (3 malicious versions).
If you installed it — respond
evm-validation is a typosquat — you almost certainly intended a legitimately-named package. Remove evm-validation, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If evm-validation 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 evm-validation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.