FakeGit Campaign Exploits Thousands of GitHub Repos to Distribute SmartLoader Malware

Malicious Repositories Masquerading as AI Tools and MCP Servers

A coordinated effort called „FakeGit” has flooded GitHub with roughly 7,600 malicious repositories. The operation began early 2024 and has already generated more than 14 million downloads of the SmartLoader and StealC payloads. Researchers first noticed the surge in late June, linking it to a wave of compromised developer tools.

The campaign relies on repositories that masquerade as legitimate AI skill packages or MCP (Microsoft Cloud Platform) servers. By embedding malicious code in seemingly innocuous projects, attackers trick developers into pulling infected libraries. Once cloned, the code executes a loader that fetches additional malware, including the credential‑stealing StealC. The scale suggests a well‑funded group targeting the open‑source supply chain to reach a broad audience.

Over 800 of the fake repositories claim to provide AI‑related functionality or act as MCP endpoints. Their README files describe advanced features, while the actual code contains hidden scripts that download SmartLoader from obscure URLs. Security analyst Maya Patel noted, „The naming conventions mimic popular AI packages, making detection by casual users unlikely.” GitHub’s automated scanning missed many of these repos, allowing them to persist for weeks. The attackers also use repository forks to amplify visibility, spreading the malicious code across multiple accounts.

Why Is SmartLoader a Growing Threat to Developers?

SmartLoader serves as a versatile dropper, capable of installing a range of secondary payloads on compromised machines. Its modular design lets attackers customize attacks for specific targets, from desktop workstations to cloud‑based CI pipelines. The malware can exfiltrate credentials, inject backdoors, and persist across system reboots. Researchers warn that developers who integrate these rogue libraries may inadvertently expose entire development environments, risking both proprietary code and user data.

The fallout from the FakeGit operation could be extensive. Enterprises that rely on open‑source components may face widespread breaches, while individual developers risk personal data loss. GitHub has pledged to improve its detection mechanisms, but the sheer volume of malicious repos means remediation will be a prolonged effort. Continuous vigilance and stricter supply‑chain reviews are essential to curb future abuse.

Frequently Asked Questions

How can developers identify a FakeGit repository? Look for inconsistencies between the repository description and its actual content, check the number of stars and forks, and run code through a reputable scanner before use.

What immediate steps should organizations take after discovering an infection? Isolate affected systems, remove the malicious loader, rotate compromised credentials, and conduct a thorough audit of all third‑party dependencies.

Will GitHub remove all malicious repositories automatically? GitHub plans to enhance automated detection, but manual reporting and community vigilance remain crucial for swift removal.