GitHub Codespaces and VS Code Extension Ecosystem Targeted in Developer Supply-Chain Attacks
Supply Chain Risk · 2 sources · Updated 4mo ago · First seen Feb 7, 2026

Security researchers reported multiple attack paths in GitHub Codespaces where opening a malicious repository or pull request can trigger remote code execution (RCE) by abusing repository-controlled VS Code configuration that Codespaces automatically honors (e.g., .vscode/ and .devcontainer/). The described impact includes arbitrary command execution inside the Codespace, exfiltration of GitHub tokens and secrets, and abuse of hidden APIs to access premium Copilot models—highlighting developer environments as a high-value supply-chain entry point because they often contain credentials outside centralized secret management.
In parallel, the Eclipse Foundation announced it will mandate pre-publish security checks for extensions uploaded to the Open VSX Registry to reduce supply-chain risk from malicious or compromised extensions. The planned controls aim to detect and quarantine suspicious uploads (e.g., namespace/name impersonation, accidentally published secrets, and known malicious patterns) before they are publicly available, following a trend of increased attacks on extension/package ecosystems (including recent cases where a compromised publisher account was used to ship poisoned updates).


