A reported worm tied to 73 Microsoft repositories on GitHub shows how modern coding tools can turn a project open into a security event.
Microsoft is adding a two-hour delay before Visual Studio Code extensions update automatically, turning update timing into a security control against supply chain abuse.
A newly published proof-of-concept tied to VS Code has pushed a familiar developer convenience into uncomfortable territory: if an authentication token can be reached through an editor workflow, the practical risk can be as serious as any password leak.
A newly described flaw in the developer editor underscores a simple but dangerous reality: in modern software workspaces, one user interaction can become a credential incident.
A disclosed attack chain involving VS Code and GitHub.dev shows how a single click can become a credential problem, not just a nuisance.
A reported zero-day in Visual Studio Code puts a familiar workflow under a harsher light: one link click, one credential class, and a potentially wide blast radius depending on token scope.
A reported weakness in Visual Studio Code’s webview layer raises a familiar but dangerous question: what happens when an editor boundary and a GitHub authorization token sit too close together?
A security flaw in the Angular Language Service extension shows how a coding assistant inside VS Code can turn hostile when it processes untrusted project content.
A high-severity flaw in the VS Code Angular Language Service extension shows how a single workspace open can become a local code-execution event if trust boundaries fail.
A reported compromise tied to a Visual Studio Code extension shows how a single trusted tool can become a gateway into source-code assets and internal development workflows.
A brief compromise of a popular VS Code extension shows how one developer workspace can become a gateway to tokens, cloud secrets, and release pipelines.
A poisoned Nx Console extension was tied to a breach of internal repositories, showing how developer tools can become high-value attack surfaces.
A GitHub-linked repository breach tied to a poisoned Nx Console VS Code extension shows how developer tooling can become the soft underbelly of source-code security.
A reported malicious VS Code extension is said to have been tied to the theft of roughly 3,800 internal repositories, underscoring how developer trust can become the fastest route into source code.
GitHub’s confirmed breach shows how a single malicious VS Code extension can turn an everyday coding tool into a high-risk entry point for enterprise code.
A reported malicious VS Code extension is a reminder that developer tools can become high-trust entry points into internal code, secrets, and automation.
A compromised Nx Console package landing in the VS Code marketplace shows how a trusted extension update can become a high-value supply-chain risk for developers.
A reported compromise of the Nx Console VS Code extension shows how a normal workspace open can turn into a security event when a high-trust add-on is tampered with.
A malicious build of a familiar VS Code add-on turned a routine extension update into a supply-chain warning for developers, cloud teams, and anyone storing secrets in their editor session.
A new wave of deceptive VS Code extensions is quietly poisoning software development at the source, raising the stakes for global supply chain security.