Notifications
Clear all
Topic starter
09/07/2026 12:37 pm
TL;DR: Malicious and hijacked extensions remain publicly available on OpenVSX even after exposure, while dormant projects and low-reputation publishers can be repurposed as malware distribution paths, according to Knostic. The finding shows that extension marketplaces need runtime trust controls, not just review and takedown workflows, as AI coding assistants increasingly consume them.
NHIMG editorial — based on content published by Knostic: compromised OpenVSX extensions remain active after exposure
Questions worth separating out
Q: What breaks when malicious extensions remain available after exposure?
A: When compromised extensions remain available, security teams lose the assumption that discovery equals containment.
Q: Why do AI coding assistants increase extension marketplace risk?
A: AI coding assistants increase risk because they often operate inside high-trust developer environments and can interact with the same packages, files, and credentials as the human user.
Q: How do security teams know if extension governance is actually working?
A: Measure whether unapproved extensions can be installed, whether dormant packages are being reviewed after sudden updates, and whether malicious listings can be blocked before execution.
Practitioner guidance
- Verify publisher lineage before approving extensions Require documented publisher identity, account history, and package provenance before allowing extensions into developer-approved catalogs, especially where dormant projects have resumed activity.
- Restrict AI coding assistants to approved extension sources Limit what assistants can install, recommend, or execute so they cannot freely pull from public marketplaces without policy checks and workspace controls.
- Add install-time inspection and blocking Inspect extension metadata, signatures, and behaviour at the moment of installation so suspicious packages can be stopped before they execute in the developer environment.
What's in the full article
Knostic's full analysis covers the operational detail this post intentionally leaves for the source:
- Step-by-step examples of malicious and hijacked OpenVSX listings that remained live after exposure
- The screenshots and publisher warnings used to distinguish dormant projects from freshly weaponised packages
- How Kirin detects an infected extension at install time and alerts the user before spread
- Operational guidance on stopping risky extensions from reaching developers and AI coding assistants
👉 Read Knostic's analysis of malicious OpenVSX extensions and AI coding risk →
OpenVSX extension abuse: what it means for AI coding security?
Explore further
09/07/2026 12:43 pm
Marketplace trust is becoming a governance control, not a convenience feature. Open extension ecosystems are no longer passive repositories. They are distribution layers that can preserve malicious access long after a compromise is discovered. That means approval, monitoring, and revocation must be treated as lifecycle controls, not one-time publishing checks. Practitioners should manage extension trust with the same discipline they apply to software supply chain governance.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to The State of Secrets in AppSec.
A question worth separating out:
Q: Who is accountable when a compromised extension is installed in a developer workspace?
A: Accountability usually sits with both the platform owner and the security team that defined the trust boundary. If extension intake, publisher verification, and runtime blocking were not clearly assigned, the environment effectively relied on informal trust. Governance frameworks should treat extension control as a shared supply chain and access management responsibility.
👉 Read our full editorial: OpenVSX extension abuse shows the persistence of AI coding risk
