Actor Profile

FakeGit is a campaign (not a named threat actor group) targeting software developers through a large-scale supply chain attack leveraging GitHub's trusted platform. The campaign's motivation appears to be widespread malware distribution, specifically SmartLoader, by exploiting developer trust in open-source repositories. The operation demonstrates sophisticated social engineering through the creation of nearly 7,600 malicious repositories, over 800 of which impersonate legitimate AI skills and Model Context Protocol (MCP) servers. The campaign employs lookalike developer profiles, copied legitimate projects, and convincing documentation to establish credibility and deceive targets into downloading malicious packages.

TTPs (Tactics, Techniques, Procedures)

The FakeGit campaign employs supply chain compromise techniques consistent with MITRE ATT&CK T1195.001 (Compromise Software Dependencies and Development Tools) and T1195.002 (Compromise Software Supply Chain). Initial access is achieved through T1566.002 (Phishing: Spearphishing Link) by luring developers to malicious repositories. The campaign leverages T1036.005 (Masquerading: Match Legitimate Name or Location) through lookalike repositories and developer profiles. T1608.001 (Stage Capabilities: Upload Malware) is evident in the hosting of SmartLoader payloads within GitHub infrastructure. The operation demonstrates T1583.008 (Acquire Infrastructure: Malvertising) through the creation of fake developer personas and project documentation to establish trust and credibility within the developer community.

Targets & Patterns

The FakeGit campaign specifically targets software developers and technology professionals, with a focus on those working in AI/ML development and seeking Model Context Protocol implementations. The targeting of the Software Development and Technology sectors is strategic, as developers frequently download and integrate third-party code, tools, and libraries into their workflows. The campaign exploits the trust inherent in open-source development communities and GitHub's reputation as a legitimate code-sharing platform. By impersonating AI skills and MCP servers—trending technologies with high developer interest—the campaign maximizes the likelihood of downloads. The scale (7,600+ repositories) suggests an indiscriminate approach within the developer community, aiming for volume rather than specific high-value targets, though the sector focus remains consistent.

Historical Context

The FakeGit campaign represents an evolution in supply chain attacks targeting developer communities through repository poisoning. This activity aligns with broader trends observed in campaigns like the 2021 UAC-0056 npm package poisoning, the 2022 PyPI typosquatting waves, and the 2023 GitHub repository hijacking incidents. The scale of 7,600+ malicious repositories exceeds most previously documented GitHub-based campaigns. The specific impersonation of AI/ML tools and Model Context Protocol servers reflects current developer interests and mirrors tactics seen in recent npm and PyPI campaigns targeting machine learning practitioners. The use of SmartLoader malware as the payload suggests this may be part of a malware-as-a-service operation or a loader distribution network, though specific attribution to known threat actor groups is not provided in available data.

Defensive Recommendations

  • Implement repository verification processes: validate GitHub repository authenticity by checking account age, commit history, contributor legitimacy, and star/fork patterns before downloading code
  • Deploy endpoint detection rules for SmartLoader indicators: monitor for suspicious downloads from GitHub followed by execution of unsigned binaries, particularly those masquerading as AI tools or MCP servers
  • Enforce code signing and software composition analysis (SCA): require digital signatures on all downloaded packages and use SCA tools to detect known malicious repositories and dependencies
  • Restrict execution from user-writable directories: implement application whitelisting and block execution from temp directories and user download folders where malicious GitHub clones are typically saved (T1204.002 mitigation)
  • Conduct developer security awareness training: educate development teams on supply chain risks, repository verification techniques, and the specific tactics used in FakeGit-style campaigns including lookalike profiles and copied documentation