Which versions of eslint-generate-release are malicious?

The following npm versions of eslint-generate-release are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate eslint-generate-release if I installed it?

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

I already installed eslint-generate-release — how do I know if it already compromised me?

If eslint-generate-release 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-generate-release part of a known attack campaign?

Yes — eslint-generate-release is associated with the IN-MAL-2026-017679 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-generate-release 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-generate-release (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-release across your stack and pipelines.

Malicious package

eslint-generate-releasenpm

eslint-generate-release is a confirmed malicious npm package (MAL-2026-13980) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-generate-release (npm)

MAL-2026-13980

Immediate action

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

npm uninstall eslint-generate-release

What this malware does

[email protected] is a hollow package whose index.js exports an empty object and whose only effect on install is dependency resolution. package.json declares a runtime dependency ltidisafe whose version specifier is not an npm-registry version but a direct HTTPS tarball URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.3.tgz. On npm install, npm fetches and installs that off-registry tarball into node_modules, introducing code that never passed through the npm registry. The package name mimics the ESLint ecosystem and the 99.9.1 version is a version-squat pattern; combined with the empty main entry, the package functions purely as a smuggling wrapper for the URL-referenced payload.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

4478598213eba844460a99bf323ef024e2fb906c918736cc7e593745029e16b4

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-generate-release (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-release across your stack and pipelines.
If you installed it — respond
eslint-generate-release is a typosquat — you almost certainly intended a legitimately-named package. Remove eslint-generate-release, 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-generate-release 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-release 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-generate-release on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017679

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database