Which versions of eslint-disable-next-line are malicious?

The following npm versions of eslint-disable-next-line are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate eslint-disable-next-line if I installed it?

eslint-disable-next-line 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.

I already installed eslint-disable-next-line — how do I know if it already compromised me?

If eslint-disable-next-line 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-disable-next-line part of a known attack campaign?

Yes — eslint-disable-next-line is associated with the GHSA-rggv-8xvv-qjg5, RLMA-2025-05783 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-disable-next-line 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-disable-next-line (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-disable-next-line across your stack and pipelines.

Malicious package

eslint-disable-next-linenpm

eslint-disable-next-line is a confirmed malicious npm package (MAL-2025-48996) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-disable-next-line (npm)

MAL-2025-48996

Immediate action

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

npm uninstall eslint-disable-next-line

What this malware does

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.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

c260c70270e5f716b6e8197913327633d64aa0ee2e18ebde88c8f53f06893c62

1dc55c7bae0cb90341b9ef16633f9d7bd4057934f0b849ede16f89964146ffc9

2b6f5fe59eaf7a79b08233b9670ac25867f5170b6f495a19bd901421142fad99

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-disable-next-line (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-disable-next-line across your stack and pipelines.
If you installed it — respond
eslint-disable-next-line 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.
Did it already run?
If eslint-disable-next-line 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-disable-next-line 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-disable-next-line on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rggv-8xvv-qjg5RLMA-2025-05783

References

Credits

ReversingLabs · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database