The FakeGit malware operation has returned with a massive automated campaign, deploying 17,610 malicious repositories on GitHub to spread the SmartLoader downloader. According to findings from software supply-chain security platform Apiiro, the campaign resumed activity on October 4 and scaled rapidly, pushing more than 13,000 repositories in just 34 hours and peaking at 2,999 repository updates per hour.
Weaponized READMEs and Compromised Accounts
Apiiro's analysis shows that the attack relies heavily on simple modifications rather than complex code alterations. In sampled commits, 97 percent modified only the project README file, while 88 percent directed the README download button to a ZIP archive designed to execute SmartLoader. Once deployed, SmartLoader delivers secondary payloads, including the StealC infostealer. While the operators behind FakeGit predominantly use disposable accounts, researchers identified at least 700 compromised accounts belonging to legitimate software developers.
Resurgence Following Earlier Summer Outbreaks
This latest activity marks a significant expansion of tactics observed earlier in the year. Security firm Island reported in July that FakeGit pushed 7,600 malicious repositories, 800 of which masqueraded as artificial intelligence skills or Model Context Protocol (MCP) servers listed in public AI registries. Rather than building entirely new infrastructure for the October wave, attackers re-aimed existing repository fleets by swapping out download targets across previously established accounts.
Obstacles in Tipping and Takedowns
Platform defenders face persistent challenges in eradicating the fleet due to fragmented hosting techniques. Apiiro noted that 71 percent of the malicious URLs were absent from threat intelligence registries like URLhaus prior to its report. Furthermore, domain-level blocking cannot target individual GitHub files without disrupting the broader service. The operators maintain backup copies across repository forks, release assets, issue attachments, and older files, allowing quick redirect updates whenever a single download link is removed.
Mitigation Guidelines for Developers
Security researchers recommend inspecting repository ownership and obtaining AI tools or MCP servers exclusively through verified vendor channels and official registries. If a SmartLoader infection occurs, organizations should assume the underlying GitHub account has been compromised, immediately invalidate active sessions and access tokens, and transition to passkey authentication.
AI-generated editorial illustration; not a documentary photograph.
Source: FakeGit malware campaign returns with 17,610 malicious GitHub repos
SIGNAL TITANS
Leave a Reply