ANAVEM
Reference
Languagefr
Laptop screen showing GitHub code repository with security warning indicators

GitHub Accounts Breached in VS Code GlassWorm Aftermath

Hundreds of GitHub accounts compromised using stolen credentials from the VS Code GlassWorm malware campaign targeting Python repositories.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
16 Mar 2026, 12:51 2 min read 2

Last updated 16 Mar 2026, 15:41

SEVERITYHigh
EXPLOITActive Exploit
PATCH STATUSUnavailable
VENDORGitHub
AFFECTEDGitHub repositories, Visual St...
CATEGORYCyber Attacks

Key Takeaways

ForceMemo Campaign Exploits GlassWorm Credential Theft

Attackers compromised hundreds of GitHub accounts on March 16, 2026, using credentials stolen during the earlier VS Code GlassWorm malware campaign. The breach specifically targeted Python repositories, with hackers gaining unauthorized access to developer accounts through previously harvested authentication tokens.

The attack represents a secondary exploitation phase following the initial GlassWorm infection that targeted Visual Studio Code users. Security researchers identified the campaign as "ForceMemo" due to distinctive indicators found in the compromised repositories.

Python Developers and VS Code Users at Risk

The breach primarily affects Python developers who were previously infected by the GlassWorm malware through compromised VS Code extensions. GitHub users who stored authentication credentials locally on infected systems face account takeover risks.

Organizations relying on affected Python repositories may encounter supply chain security issues if malicious code was injected during the breach window.

Credential Harvesting Leads to Repository Compromise

The GlassWorm malware initially infected developer workstations through malicious VS Code extensions, stealing stored GitHub tokens and authentication credentials. Attackers then used these harvested credentials to access legitimate developer accounts and modify Python package repositories.

GitHub users should immediately rotate all authentication tokens and review recent repository activity for unauthorized changes. The CISA Known Exploited Vulnerabilities catalog provides guidance on securing development environments against similar attacks.

Frequently Asked Questions

How were GitHub accounts compromised in the GlassWorm attack?+
Attackers used credentials stolen by GlassWorm malware that infected VS Code installations. The malware harvested GitHub authentication tokens from infected developer workstations, which were later used to access legitimate accounts.
What should developers do if affected by the GitHub breach?+
Developers should immediately rotate all GitHub authentication tokens and personal access tokens. They should also review recent repository activity for unauthorized changes and scan their VS Code installations for malicious extensions.
Which repositories were targeted in the ForceMemo campaign?+
The campaign specifically targeted Python repositories hosted on GitHub. Attackers focused on compromising Python package repositories that could be used for supply chain attacks against downstream users.
Emanuel DE ALMEIDA
About the Author

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...