Which versions of giteegit are malicious?

The following PyPI versions of giteegit are flagged malicious: 1.0.0, 1.0.1, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate giteegit if I installed it?

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

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

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

Malicious package

giteegitPyPI

Malicious code in giteegit (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191739

Immediate action

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

pip uninstall giteegit

What this malware does

Package exfiltrates source code files to a telegram channel, while the description promises saving them to a git service

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-giteegit

Reasons (based on the campaign):

files-exfiltration
A Telegram webhook is used to send collected data.

Malicious versions

4 flagged

1.0.01.0.11.0.41.0.5

Indicators of compromise (SHA-256)

0d3c825f8bc82aad69a0a011e332ebf1656a3560414d67c85273dedb76df6980

4a26c5d911f4394086eca9dfca0dfb8b05cc0675bac36dfdbec08e30f6d1abed

3ea37a29534d40261a920fed4880384263ad7ac95f3e053b160fabf232ebf464

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

Campaign

2025-08-giteegit

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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