Malware · Threat Intelligence
FakeGit campaign floods GitHub with over 17,000 malware-laden repositories
Researchers report over 17,000 fake GitHub repositories are spreading SmartLoader malware in a renewed FakeGit campaign. Attackers use convincing download links to trick developers.
Ross GrantUpdated 3 min read
The short version
Researchers have found over 17,000 fake GitHub repositories spreading malware called SmartLoader. These fake projects trick people into downloading malicious files by looking like real software tools. If run, the malware can steal information or install more harmful software. Developers and users should be careful where they download code and always check the source.
By the numbers
- 17,610fake GitHub repositories spreading malwareBleepingComputer
- 13,000+repositories created in 34 hours during the surgeBleepingComputer
- 700accounts appearing to belong to real developers used in the campaignBleepingComputer
- 71%of malicious repos missing from URLhaus before the reportBleepingComputer
What happened?
Researchers say the FakeGit malware campaign has reactivated, using over 17,000 fake GitHub repositories to distribute SmartLoader malware. Attackers use convincing README files with download links to trick users into running malicious code. The campaign surged in early October 2026.
A surge in malicious GitHub repositories
Researchers have reported a major resurgence of the FakeGit malware campaign, which is now using more than 17,000 fake repositories on GitHub to distribute malware known as SmartLoader. According to BleepingComputer (opens in a new tab) and SC Media (opens in a new tab), this wave began in early October 2026. In just 34 hours, over 13,000 repositories were created, peaking at nearly 3,000 per hour. The campaign targets developers and users searching for open-source tools, especially those interested in AI skills or MCP (Minecraft server) plugins.
How attackers lure victims
The malicious repositories are designed to look legitimate. Most use README files with clear instructions and a prominent download button. This button links to a ZIP archive containing the SmartLoader malware. Once downloaded and run, SmartLoader can install other malware, including the StealC infostealer, which is designed to steal sensitive information from infected systems.
Researchers found that the attackers used mostly throwaway GitHub accounts, but at least 700 accounts appeared to belong to real developers. This increases the risk that users will trust and download from these repositories. The campaign is not new: similar activity has been tracked since January 2026, but the FakeGit name was first used in July when a report from Island highlighted 7,600 fake repositories. At that time, 800 of them pretended to be AI-related tools or Minecraft plugins, making them more attractive to developers.
Why the campaign is hard to stop
One of the reasons FakeGit has been so persistent is the way GitHub and other security tools try to block malicious content. According to researchers at Apiiro, many blocklists and removal efforts only catch a fraction of the malicious repositories. Attackers can keep the same repository active and simply change the download link to point to a new malicious file. Even if one file is deleted, the attacker can redirect users to a backup copy stored in a fork, an older ZIP file, a release asset, or an issue attachment. Apiiro found that 71% of the malicious repositories were not listed on URLhaus, a popular malware tracking service, before their report.
Traditional domain-level blocking is also ineffective. Blocking a single file on GitHub would require blocking the entire domain, which is not practical for most organisations. This allows attackers to keep their infrastructure running with minimal disruption.
Advice for developers and users
Researchers recommend several steps to avoid falling victim to this campaign. First, always verify the owner of a repository before downloading or running any code. For AI skills, Minecraft plugins, or similar tools, use only official registries or vendor repositories. If you suspect that you have run SmartLoader, treat the incident as a potential compromise of your GitHub account. Revoke all active sessions and access tokens, and consider switching to passkeys for stronger authentication.
The scale and persistence of supply chain threats
The FakeGit campaign highlights the ongoing risks of supply chain attacks in open-source software. Attackers are increasingly targeting platforms like GitHub, where trust in community-contributed code can be exploited. The speed and scale of this campaign, over 17,000 repositories, with thousands created in just hours, show how quickly attackers can adapt and overwhelm manual defences. As open-source software becomes more central to development, both individuals and organisations need to be vigilant about the sources of their code and the security of their accounts.
Claimed vs confirmed
- Confirmed
Over 17,000 fake GitHub repositories are distributing SmartLoader malware.
Reported by BleepingComputer and SC Media based on security researchers' findings.
- Confirmed
Attackers are using accounts that appear to belong to real developers.
Researchers identified at least 700 such accounts, according to BleepingComputer.
- Confirmed
Most malicious repositories are not detected by popular blocklists.
Apiiro researchers found 71% of the fleet missing from URLhaus before their report.
The impact
- Money
- There is no reported financial loss yet, but if user data is stolen or accounts are compromised, affected organisations could face costs for incident response, remediation, and possible regulatory fines (for example, GDPR fines can reach €20m or 4% of global turnover).
- Reputation
- GitHub's reputation as a trusted platform may be affected if users lose trust in open-source repositories. Developers who fall victim may also face reputational harm if their accounts are misused.
- Customers
- Developers and users who download code from GitHub are at risk of malware infection and data theft. Users should verify repository sources and take action if they suspect compromise, such as revoking tokens and switching to passkeys.
Why it matters
Anyone who downloads code from GitHub could be at risk if they trust the wrong repository. This campaign shows how attackers can use trusted platforms to spread malware on a large scale, putting both individuals and organisations in danger of data theft or account compromise.
How does it work?
Attackers create fake GitHub repositories with README files containing download links to ZIP files. These ZIPs install SmartLoader, which can then download and run other malware such as StealC. Attackers use backup copies and change links to avoid removal.
Key points
- Over 17,000 fake GitHub repositories are spreading SmartLoader malware.
- Attackers use convincing README files to lure victims into downloading malicious files.
- Traditional blocklists and removal efforts are not catching most malicious repos.
- Attackers can quickly redirect download links to backup copies, making removal difficult.
- Developers should verify repository owners and use official sources for software.
Sources
BleepingComputer
Reference
SC Media
Reference
