Actor Profile

FakeGit is a campaign-level threat activity targeting software developers through malicious GitHub repositories. The operation demonstrates sophisticated social engineering by impersonating legitimate AI tools and Model Context Protocol servers. The campaign's motivation appears to be widespread malware distribution to the developer community, leveraging trust in open-source ecosystems. With nearly 7,600 compromised or malicious repositories discovered, FakeGit represents a significant supply chain threat to the software development sector. The ultimate attribution and sponsorship of this campaign remains unclear from available data.

TTPs (Tactics, Techniques, Procedures)

The FakeGit campaign employs supply chain compromise techniques targeting developer workflows. Key TTPs include: Initial Access via malicious repositories masquerading as legitimate AI tools and MCP servers (T1195.001 - Compromise Software Supply Chain); social engineering through lookalike developer profiles and convincing documentation to establish credibility; delivery of SmartLoader malware through cloned and trojanized open-source projects. The campaign leverages trusted platforms (GitHub) to bypass initial suspicion (T1608.001 - Upload Malware). The scale of 7,600+ repositories suggests automated infrastructure for repository creation and maintenance, indicating sophisticated operational capabilities and persistence mechanisms within the GitHub ecosystem.

Targets & Patterns

FakeGit specifically targets software developers and technology professionals, particularly those working with AI technologies and Model Context Protocol implementations. The campaign exploits developer workflows that involve discovering, cloning, and integrating third-party code from GitHub repositories. By focusing on trending technologies like AI skills and MCP servers, the threat actors capitalize on high developer interest and urgency to adopt emerging tools. The targeting pattern suggests the actors understand developer behavior, including reliance on GitHub for code discovery, trust in repository documentation, and the tendency to quickly integrate promising tools. This focus on the software development sector enables potential downstream supply chain attacks affecting end-user applications and enterprise environments.

Historical Context

The FakeGit campaign represents an evolution in supply chain attacks targeting developer communities through source code repositories. While similar to previous campaigns like npm typosquatting and PyPI package poisoning, FakeGit's scale (7,600+ repositories) and focus on AI-related tools reflects current threat trends. The use of GitHub as an attack vector builds on established patterns seen in operations like the 2021 UAC-0056 campaign and various cryptocurrency wallet-stealing repository attacks. The SmartLoader malware distribution method through fake AI tools aligns with increasing threat actor interest in exploiting the rapid adoption of AI technologies. This campaign demonstrates maturation in repository-based attacks, moving from simple typosquatting to comprehensive impersonation with copied projects and fabricated developer personas.

Defensive Recommendations

  • Implement GitHub repository vetting procedures: verify contributor history, check repository age, review commit patterns, and validate project authenticity before cloning or integrating code
  • Deploy endpoint detection rules to identify SmartLoader malware indicators and monitor for suspicious execution chains originating from developer tools or cloned repositories
  • Establish software composition analysis (SCA) tools in CI/CD pipelines to scan for known malicious packages and detect anomalous dependencies in third-party code
  • Conduct security awareness training for developers on supply chain risks, emphasizing verification of AI tools and MCP servers through official channels before adoption
  • Monitor network traffic for C2 communications associated with SmartLoader and implement application whitelisting to prevent unauthorized loader execution in development environments