# MAL-2026-14301: Malicious code in evm-validation (npm)


- **Type:** Malicious package
- **Package:** `evm-validation` (npm)
- **Published:** 19 Aug 2026
- **Also known as:** GHSA-gvxq-2rq2-f7x6

## What is MAL-2026-14301?

MAL-2026-14301 is a malicious package in evm-validation, published on 19 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-14301?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14301 is a malicious package: evm-validation (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14301/ (Markdown: https://insights.sbomify.com/MAL-2026-14301/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14301

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14301/
Summaries are generated and may contain mistakes; the official description above is the record.