FakeGit Campaign Exploits 7,600 Repos for Malware Spread

In a significant security breach, a malicious operation known as 'FakeGit' is leveraging a staggering 7,600 GitHub repositories to disseminate SmartLoader and StealC malware. This campaign has alarmingly garnered over 14 million downloads, raising concerns among developers and cybersecurity experts alike.

Understanding FakeGit's Tactics

FakeGit's deceptive strategy includes over 800 repositories masquerading as artificial intelligence (AI) tools or MCP servers. These repositories have been spotted more than 600 times across various public AI directories, which significantly increases their visibility to unsuspecting developers.

This tactic, referred to as 'agentbaiting,' is designed to attract AI agents and developers. By blending into legitimate AI spaces, these malicious repositories enhance their chances of being recognized and used.

The Evolution of FakeGit

This campaign is not entirely new; it is an evolution of a prior operation that utilized Lumma Stealer malware, attributed to a threat actor identified as 'Water Kurita' by cybersecurity analysts at Trend Micro. The recent focus on AI tools began in March, peaking in April with the creation of 300 new GitHub repositories associated with AI functionalities.

The Scale of Deception

As the campaign unfolded, FakeGit expanded to encompass over 1,400 repositories dedicated to AI tools, workflows, and agents, all linked to either SmartLoader or StealC malware downloads. These repositories often mimic well-known consumer and enterprise applications, including Gmail, WhatsApp, Databricks, Jenkins, and Docker.

To make these repositories appear credible, attackers include convincing documentation, fake star ratings, and fork counts. They also replicate project descriptions and utilize legitimate developer account names to deceive potential users.

Malicious Payloads and Their Impact

The README files within these repositories typically instruct users to download ZIP files that masquerade as legitimate installers or project releases. However, these ZIP files contain disguised Lua payloads that activate SmartLoader upon execution.

Once initiated, SmartLoader establishes persistence on the infected system through scheduled tasks and retrieves its command-and-control (C2) address via a Polygon smart contract. From there, it downloads additional encrypted stages from GitHub, ultimately delivering the StealC information stealer.

The AgentBaiting Technique

Researchers at Island have identified this emerging technique known as AgentBaiting, which aims to enhance the visibility of malicious repositories to AI agents. In a typical scenario, these agents may interpret the README content as genuine documentation, leading them to recommend the repository or ZIP file to human operators.

Protecting Against FakeGit

To safeguard against such threats, developers and users should remain vigilant when downloading software from GitHub and other platforms. Some steps to consider include:

• Verify repository authenticity and owner profiles.
• Check for trustworthy documentation and community feedback.
• Avoid downloading files from unknown or suspicious sources.
• Keep security software updated and perform regular scans.

Technology teams are watching fakegit campaign exploits 7,600 repos for malware spread closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.

Technology teams are watching fakegit campaign exploits 7,600 repos for malware spread closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

As the landscape of cybersecurity continues to evolve, awareness and proactive measures will be key in mitigating risks associated with malicious campaigns like FakeGit.