Invisible Unicode hits GitHub repos

🔑 Enhanced Key Takeaways

• •Threat actor Glassworm, first identified in October 2025 targeting VS Code extensions, returned in March 2026 compromising over 150 GitHub repos, npm packages, and VS Code extensions between March 3-9[1][2].
• •Malicious payloads use Solana blockchain accounts for command-and-control and data exfiltration, fetching instructions and stealing credentials instead of traditional C2 servers[1][3].
• •AI-generated commits provide camouflage by mimicking each target's coding style with documentation tweaks and refactors, enabling scaled attacks across diverse repositories[1][2].
• •Payloads harvest credentials for GitHub tokens, NPM tokens, OpenVSX credentials, and over 70 cryptocurrency wallets to propagate infections and enable further supply chain compromises[4][5].

🛠️ Technical Deep Dive

• •Exploits Private Use Area (PUA) Unicode characters in ranges U+FE00–U+FE0F and U+E0100–U+E01EF, which render invisible in code editors, terminals, and GitHub interfaces[1].
• •Invisible characters encode executable JavaScript payloads, such as decoder strings in backticks that produce code fetching Solana-based instructions[1][2].
• •Payload stages: decodes invisible code, downloads AES-256-CBC encrypted loader via HTTP (keys in headers), harvests credentials including 49+ crypto wallets, GitHub/NPM/OpenVSX tokens[4][5].
• •Self-propagating: stolen credentials used to inject malware into additional repos/packages/extensions, turning infected machines into SOCKS proxies, HVNC servers, and execution nodes[4].

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline