eslint-plugin-vitest-ts (npm) · Malicious Code
Affects eslint-plugin-vitest-tsSource GCVE Database
Malicious package : remove eslint-plugin-vitest-ts and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12370
What to do
Remove eslint-plugin-vitest-ts 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 |
|---|---|---|
| npmeslint-plugin-vitest-ts | 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 (a354edd3ce58afcb537f1e58b5152244cc6a98c6b0462de297262d9aba4e17d3) The package declares itself as an ESLint plugin but ships copies of nodemailer's source layout along with an obfuscated install-time loader. package.json's postinstall hook runs `node lib/utils/index.js`, which spawns a detached child process executing lib/utils/smtp-connection/index.js. That file uses obfuscator.io-style string-array indirection (`_0x438c`, `_0x926305`, etc.) to hide a call that fetches JSON from https://api.jsonbin.io/v3/b/6a72aa2bda38895dfebb1302 and passes the returned `record.cookie` string to `new Function('require', <fetched>)(require)`. The fetched content is attacker-controlled and mutable, and it executes in-process with `require` injected, giving arbitrary code execution on any machine that runs `npm install` for this package. The name `eslint-plugin-vitest-ts` is unrelated to the shipped nodemailer-shaped source, indicating a lure/typosquat. ## Source: ghsa-malware (24c2db5f1e6400e1a774b0a542c8cb8cd6aad001e80068c6aeb97ebc6af3c2d0) 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.