GitHub Supply Chain Attack: 10,000 Malicious Clones Spread Trojan ZIPs
A significant supply-chain attack targeting GitHub has been identified, involving over 10,000 cloned repositories that use automated commits to spread Trojan malware via concealed ZIP files.
Discovery of the Attack
Security analysts uncovered a coordinated operation leveraging the platform’s popularity to deceive developers. The campaign involved replicating legitimate open-source projects and embedding malicious payloads within cloned repositories.
Initial Detection
Researchers first detected anomalies when a security professional noticed a duplicate of their own repository appearing in search results. The cloned project mirrored the original’s name, commit history, and structure, but contained an altered README file with a link to an external ZIP archive.
Phases of the Attack
The attack infrastructure relied on a dynamic distribution system with three primary phases.
Phase 1: Replication
The first phase involved replicating verified repositories, preserving all original code, commit logs, and contributor information to maintain credibility.
Phase 2: Malicious Redirect
The second phase introduced a modified README file containing a malicious URL that redirected users to a compromised file.
Phase 3: Automated Updates
The third phase utilized automated updates to maintain visibility, with identical “Update README.md” commits pushed every few hours to evade static analysis tools.
Analysis and Findings
Analysis of the malicious ZIP files revealed payloads classified as SmartLoader and StealC, which target Windows systems to extract sensitive data. Researchers developed a custom script to scan GitHub’s public repositories, examining 16 million commits. After filtering out non-malicious activity and evaluating timestamp patterns, they identified approximately 10,000 repositories operating within the same automated threat framework.
Exploitation of Security Gaps
The attack exploited gaps in automated security measures, as many malicious repositories remained active for extended periods without triggering detection mechanisms. Experts highlighted the evolving risks associated with AI-driven development tools that autonomously access public code repositories.
A cybersecurity specialist noted that attackers are exploiting the inherent trust placed in established development platforms. The specialist emphasized that automated workflows frequently reference code from reputable sources, making it easier for malicious actors to infiltrate supply chains.
Recommendations for Developers
- Conduct manual ZIP file reviews
- Avoid embedded links in documentation
- Verify historical release records to identify potential compromises
Conclusion
The incident underscores the growing complexity of securing open-source ecosystems as automation becomes more prevalent in software development processes.
About Author
English