eslint-generate-prereleasenpm
eslint-generate-prerelease is a confirmed malicious npm package (MAL-2026-13979) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eslint-generate-prerelease (npm)
What this malware does
Package ships an empty module (index.js = 'module.exports = {};') under a name that resembles internal tooling, published at an inflated version 99.9.1 — the canonical shape used to win version resolution against a private-registry package of the same name. Its single dependency, 'ltidisafe', is declared not as a registry package but as a direct tarball URL on a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.2.tgz). On npm install, npm fetches that tarball from a location the registry does not audit and executes any lifecycle scripts and main module it contains. The path segment 'depenconf' and the version-inflation pattern are consistent with a targeted dependency-confusion attack. The lure package itself is hollow; the harm arrives through the URL-pinned transitive dependency.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-generate-prerelease (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-generate-prerelease across your stack and pipelines.
If you installed it — respond
Remove eslint-generate-prerelease 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.
Did it already run?
If eslint-generate-prerelease 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-generate-prerelease 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks eslint-generate-prerelease-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.