Which versions of eslint-commit-parser are malicious?

The following npm versions of eslint-commit-parser are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate eslint-commit-parser if I installed it?

Remove eslint-commit-parser 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.

I already installed eslint-commit-parser — how do I know if it already compromised me?

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

Yes — eslint-commit-parser is associated with the IN-MAL-2026-007769, GHSA-qmq6-r6mp-r586 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-commit-parser 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-commit-parser (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-commit-parser across your stack and pipelines.

Malicious package

eslint-commit-parsernpm

eslint-commit-parser is a confirmed malicious npm package (MAL-2026-6567) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-commit-parser (npm)

MAL-2026-6567

Immediate action

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

npm uninstall eslint-commit-parser

What this malware does

The package is published under the name eslint-commit-parser but its contents are a verbatim copy of the supertest HTTP-testing library — package.json carries supertest's description ("SuperAgent driven library for testing HTTP servers") and repository URL (https://github.com/ladjs/supertest.git), and the shipped source is supertest's. A developer who installs eslint-commit-parser expecting an ESLint commit parser receives unrelated code. package.json additionally declares a runtime dependency on express-mocha-test@^0.0.1, but no file in the tarball requires or imports that module — its only effect on the installer is to be resolved and installed alongside the carrier. The combination of a deceptive package name, contents that have no relation to the advertised identity, and an unused low-version unfamiliar transitive is the standard namespace-abuse / dependency-confusion carrier shape: the host package is hollow with respect to its declared identity and its purpose on install is to drag express-mocha-test onto the installer's machine.

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.

The OpenSSF Package Analysis project identified 'eslint-commit-parser' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8631c673a2ca9fdebee382762a69c849485f6e2aa3c749173dea8d0f0f6e090b

5fc51e200a141d1dbbb4f7eb9e5e3dec18507572e5dc9562278713c554fad195

3705df26e8974022b1cb292288fcd4e043255e0e9e65ead22a287bf148d4bf55

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-007769GHSA-qmq6-r6mp-r586

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks eslint-commit-parser-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