Which versions of @crowdstrike/commitlint are malicious?

The following npm versions of @crowdstrike/commitlint are flagged malicious: 8.1.1, 8.1.2. Treat any of these as compromised.

How do I remediate @crowdstrike/commitlint if I installed it?

@crowdstrike/commitlint 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 @crowdstrike/commitlint — how do I know if it already compromised me?

If @crowdstrike/commitlint 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 @crowdstrike/commitlint part of a known attack campaign?

Yes — @crowdstrike/commitlint is associated with the GHSA-w4gj-8xw5-558p 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 @crowdstrike/commitlint 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 @crowdstrike/commitlint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @crowdstrike/commitlint across your stack and pipelines.

Part of a larger attack: @crowdstrike published 9 malicious packages. See the full campaign →

Malicious package

@crowdstrike/commitlintnpm

@crowdstrike/commitlint is a confirmed malicious npm package (MAL-2025-47233) that steals credentials and exfiltrates sensitive data (malicious versions 8.1.1, 8.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @crowdstrike/commitlint (npm)

MAL-2025-47233

Immediate action

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

npm uninstall @crowdstrike/commitlint

What this malware does

The package was compromised and malicious code added.

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 was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged

8.1.18.1.2

Indicators of compromise (SHA-256)

e58c63ca78f39890835120723ac0ab398dbaddb3018f3b640145685ab38cdd93

1543213669ef70af452c85de1a9c4cdc2d6f0937341cf3860ece34b74d92ed42

ff3c6348bbcc2212d3fa131c4a3a614ad152becdef880906e74537724b69758a

81a774546362bc73a1d1a7c8b329235b560f8ee6cc4afc03d4477f86c1314469

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 @crowdstrike/commitlint (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @crowdstrike/commitlint across your stack and pipelines.
If you installed it — respond
@crowdstrike/commitlint 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 @crowdstrike/commitlint 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 @crowdstrike/commitlint 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. @crowdstrike/commitlint on npm has been identified as a malicious package (versions 8.1.1, 8.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w4gj-8xw5-558p

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @crowdstrike/commitlint-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