Which versions of evm-validation are malicious?

The following npm versions of evm-validation are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate evm-validation if I installed it?

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.

I already installed evm-validation — how do I know if it already compromised me?

If evm-validation 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 evm-validation part of a known attack campaign?

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

Malicious package

evm-validationnpm

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). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in evm-validation (npm)

MAL-2026-14301

Immediate action

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

npm uninstall evm-validation

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.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

8b39d83a94d652f10bd7e87a7680ce70d197876379fcaf6de4b11546289d344f

d3c551a6031e48a54b550a604e2198a4491cf935407744bba8ef0c11c54086c4

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for evm-validation (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evm-validation across your stack and pipelines.
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 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 evm-validation 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. evm-validation on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018422IN-MAL-2026-018421

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database