Which versions of git-config-sync are malicious?

The following PyPI versions of git-config-sync are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

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

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

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

Yes — git-config-sync is associated with the 2026-05-eth-security-auditor, IN-MAL-2026-004424, IN-MAL-2026-004428 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-config-sync 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-config-sync (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging git-config-sync across your stack and pipelines.

Malicious package

git-config-syncPyPI

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

MAL-2026-4273

Immediate action

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

pip uninstall git-config-sync

What this malware does

On import gitconfig_sync, the package's _core.py spawns a daemon thread (after a 3-15 second random delay) that walks ~/.ssh, ~/.aws, ~/.ethereum, ~/.config, ~/.docker, ~/.kube, and the current working directory, regex-matching private keys, BIP39 mnemonics, OpenAI sk- keys, GitHub ghp_ tokens, AWS AKIA keys, and passwords. Harvested findings (up to 200) are bundled with the host's hostname, platform, and CWD into a JSON payload and POSTed to webhook endpoints fetched dynamically from https://ddjidd564.github.io/defi-security-best-practices/config.json with TLS verification explicitly disabled (ctx.check_hostname = False; ctx.verify_mode = ssl.CERT_NONE). The remote config-driven webhook list lets the operator rotate exfil destinations without republishing. The package presents a benign cover (sync.py/cli.py claiming git-config-sync functionality, generic 'DevOps Tools' author metadata, README that never mentions _scan_and_report) to mask the harvester. The defi-security-best-practices path on the C2 domain plus the .ethereum scan and BIP39 mnemonic regex indicate crypto-wallet targeting.

During import, the package runs the code to exfiltrates credentials, private keys and other sensitive data.

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

Campaign: 2026-05-eth-security-auditor

Reasons (based on the campaign):

files-exfiltration
exfiltration-env-variables
crypto-related
Downloads and executes a remote malicious script.
exfiltration-crypto
exfiltration-credentials

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

f1b5dafc5b04761cd45c3c22cb68a171eaf1cf6431189c8fecb1249c3443e042

5d71ccb34f946bbc8f9f6a517eefc23e987ad2a9c2bfe335f58d6b0047d31685

8e49db03099f1d6053a9ebada346c3816399bc47918c92d765162128a095c401

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

Campaign

2026-05-eth-security-auditorIN-MAL-2026-004424IN-MAL-2026-004428

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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