Which versions of bitcommit are malicious?

The following PyPI versions of bitcommit are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate bitcommit if I installed it?

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

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

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

Malicious package

bitcommitPyPI

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

MAL-2024-12219

Immediate action

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

pip uninstall bitcommit

What this malware does

Packages exfiltrate the diff of the current repository. The code in "main.py" suggests it's not a real attempt to provide AI-generated commit message, but a security research attempting to leverage typosquatting.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-08-old-bitcommit

Reasons (based on the campaign):

exfiltration-generic
typosquatting

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

1e76f4677106336ffc35a33b9e7da1cb116f6f06a9da5c082d66fb75344067eb

d0e954ac7acd6af73d285edea41177ee09be01a2e14a1b4e6b195ba7e07b9515

2a020389ce496861e8849d835858058ce8f56e3bf75e18fdc8bf7fd87f8d5ca0

0457bd0732088ad4a34bb934b0dea41226eeedfeaa466292df267ff341da99b3

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

Campaign

2024-08-old-bitcommit

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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