Which versions of git-git-git are malicious?

The following npm versions of git-git-git are flagged malicious: 1.0.8, 1.0.9, 1.0.10, 1.0.11, 1.0.12. Treat any of these as compromised.

How do I remediate git-git-git if I installed it?

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

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

Yes — git-git-git is associated with the GHSA-w8x9-9886-9m73 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 git-git-git 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 git-git-git (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging git-git-git across your stack and pipelines.

Malicious package

git-git-gitnpm

Malicious code in git-git-git (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3504

Immediate action

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

npm uninstall git-git-git

What this malware does

The package git-git-git 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 as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

5 flagged

1.0.81.0.91.0.101.0.111.0.12

Indicators of compromise (SHA-256)

fa5e0d5e3dc2a5a2cf5a7219b747a751510b5e030e512f041e52851fe28cbe34

13f3e8d4ce1fbd7d58dcb8dbb39b292f29ef0af488d660904405e011cb7db917

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

aee29b689edc0620e25183b269a2b0f9bb0a0e84e74f19d7c876e46712720e72

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

Campaign

GHSA-w8x9-9886-9m73

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks git-git-git-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