Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

eslint-plugin-executable-stories-vitestnpm

eslint-plugin-executable-stories-vitest is a confirmed malicious npm package (MAL-2026-5249) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.1, 2.1.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-executable-stories-vitest (npm)

MAL-2026-5249
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eslint-plugin-executable-stories-vitest

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.

Malicious versions

2 flagged
1.2.12.1.8

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
37cda64660196ba2834eebfa1c7c1debc8367bb89d9b953d1c01fa0c5b722e7a
006740a26989144380b61638b2c2fd159daf7e8730a7aa881319e95c1ed2f4bb

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-plugin-executable-stories-vitest (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-executable-stories-vitest across your stack and pipelines.

  2. If you installed it — respond

    eslint-plugin-executable-stories-vitest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If eslint-plugin-executable-stories-vitest 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.

  4. How O3 protects you

    O3 blocks eslint-plugin-executable-stories-vitest 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-executable-stories-vitest on npm has been identified as a malicious package (versions 1.2.1, 2.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008424IN-MAL-2026-008427

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks eslint-plugin-executable-stories-vitest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore