git-config-sync
Affected
- Versions:
0.1.0,0.1.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in git-config-sync (PyPI)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (8e49db03099f1d6053a9ebada346c3816399bc47918c92d765162128a095c401)
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.
Source: kam193 (f1b5dafc5b04761cd45c3c22cb68a171eaf1cf6431189c8fecb1249c3443e042)
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):
Not rated by the source.
0.1.0, 0.1.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0