Which versions of super-commit are malicious?

The following npm versions of super-commit are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate super-commit if I installed it?

super-commit 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 super-commit — how do I know if it already compromised me?

If super-commit 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.

Is super-commit part of a known attack campaign?

Yes — super-commit is associated with the GHSA-23rm-x3xw-w5w2 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 super-commit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for super-commit (version 1.0.1).

Malicious package

super-commitnpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

super-commit is a confirmed malicious npm package (MAL-2025-191015) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in super-commit (npm)

MAL-2025-191015

Immediate action

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

npm uninstall super-commit

What this malware does

The package super-commit was found to contain malicious code.

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 Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

4ef89565a74f08dc54807acd41e1218c07d6d9ffdb73411163e95c66ba080e61

6c1af7533a4794e88dc233547249b656c3a1fd1a87109827755918da11151fbe

11a2a12f73d717b717d9fb4b0af32222bc44692f3d7cb12f1ba7564bcf1b6cc7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for super-commit (version 1.0.1).
If you installed it — respond
super-commit 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 super-commit 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

No. super-commit on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-23rm-x3xw-w5w2

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks super-commit-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