eslint-publish-releasenpm
Advisory published Updated
eslint-publish-release is a confirmed malicious npm package (MAL-2026-13981) 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-publish-release (npm)
What this malware does
[email protected] is a hollow package (index.js is an empty stub, no lifecycle scripts) whose only effect on install is dependency resolution. Its package.json declares its sole dependency ltidisafe as a direct HTTPS tarball URL pointing at a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.4.tgz) rather than a version resolved from the npm registry. Installing this package causes npm to fetch and install arbitrary code from that bucket into the consumer's node_modules, where it becomes executable at require time by the parent project. The bucket is not a publisher-matched or npm-registry destination, the URL path contains the token depenconf (dependency-confusion), the package name resembles legitimate ESLint release tooling, and the 99.9.1 version number is characteristic of dependency-confusion lures. The package structure — empty main, no independent utility, sole purpose is pulling a tarball from an anonymous bucket — is a delivery-vector shape, not a real library.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for eslint-publish-release (version 99.9.1).
If you installed it — respond
Remove eslint-publish-release 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-publish-release 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks eslint-publish-release-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.