Which versions of eslint-plugin-vitest-ts are malicious?

The following npm versions of eslint-plugin-vitest-ts are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate eslint-plugin-vitest-ts if I installed it?

eslint-plugin-vitest-ts is a typosquat — you almost certainly intended a legitimately-named package. Remove eslint-plugin-vitest-ts, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed eslint-plugin-vitest-ts — how do I know if it already compromised me?

If eslint-plugin-vitest-ts 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 eslint-plugin-vitest-ts part of a known attack campaign?

Yes — eslint-plugin-vitest-ts is associated with the IN-MAL-2026-014704, GHSA-pw3r-jw68-935v 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 eslint-plugin-vitest-ts 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 eslint-plugin-vitest-ts (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-vitest-ts across your stack and pipelines.

Malicious package

eslint-plugin-vitest-tsnpm

eslint-plugin-vitest-ts is a confirmed malicious npm package (MAL-2026-12370) that typosquats a legitimate package to trick installs (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-vitest-ts (npm)

MAL-2026-12370

Immediate action

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

npm uninstall eslint-plugin-vitest-ts

What this malware does

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.

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

1 flagged

1.0.4

Indicators of compromise (SHA-256)

a354edd3ce58afcb537f1e58b5152244cc6a98c6b0462de297262d9aba4e17d3

24c2db5f1e6400e1a774b0a542c8cb8cd6aad001e80068c6aeb97ebc6af3c2d0

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 eslint-plugin-vitest-ts (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-vitest-ts across your stack and pipelines.
If you installed it — respond
eslint-plugin-vitest-ts is a typosquat — you almost certainly intended a legitimately-named package. Remove eslint-plugin-vitest-ts, 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 eslint-plugin-vitest-ts 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 eslint-plugin-vitest-ts 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. eslint-plugin-vitest-ts on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014704GHSA-pw3r-jw68-935v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eslint-plugin-vitest-ts-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