VS Code 1.123 Adds Two-Hour Extension Update Delay to Limit Supply Chain Attacks

2026-06-18 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Cybersecurity & Data Privacy · Depth: Intermediate, short

Summary

VS Code 1.123, released on June 3, introduces a two-hour delay for newly published extension versions before automatic updates are deployed to users. This measure aims to provide a window to detect and pull malicious updates if an extension maintainer's account is compromised, preventing widespread distribution to millions of developers. However, extensions from "trusted publishers" like Microsoft, GitHub, and OpenAI are exempt from this delay. This change aligns with similar supply chain security controls in other package ecosystems, such as Pip 26.1's configurable dependency cooldowns (up to seven days) and RubyGems' opt-in cooldowns. Community feedback on Reddit largely criticized the two-hour duration as insufficient, citing that many supply chain compromises are discovered days or weeks later. Alternative suggestions included sandboxing extensions with explicit permissions or implementing staged rollouts. The article also highlights the lack of similar cooldown mechanisms in WordPress, where attackers have previously exploited long-term vulnerabilities.

Key takeaway

For IT Professionals managing VS Code deployments, the new two-hour extension update delay offers a minimal but automatic layer of protection against supply chain attacks. You should not rely solely on this short window for critical security. Consider disabling automatic updates and implementing policy-based allowlists or a curated internal marketplace to enforce longer, more robust cooldowns or manual vetting. This approach provides greater control and aligns with practices proven to avoid more problems than they cause in other package ecosystems.

Key insights

Implementing update delays for software components can mitigate supply chain attack impact by providing a detection window.

Principles

• Longer update cooldowns significantly reduce supply chain attack success.
• Automated security scanners are critical for early malicious package detection.
• Sandboxing extensions enhances security more fundamentally than delays.

In practice

• Configure internal package registries with minimum release age settings.
• Disable auto-updates for critical tools to manage extension versions manually.
• Implement policy-based allowlists for approved software components.

Topics

• VS Code
• Supply Chain Security
• Extension Management
• Software Updates
• Package Ecosystems
• Cybersecurity Policy

Best for: CTO, VP of Engineering/Data, Director of AI/ML, Software Engineer, Security Engineer, IT Professional

Related on AIssential

• Pip 26.1 Ships Dependency Cooldowns and Experimental Lockfile Support to Combat Supply Chain Attacks — Pip 26.1 enhances Python supply chain security through dependency cooldowns and experimental "pylock.toml" lockfile support.
• v2.1.32 — Recent Claude Code updates enhance performance, fix critical bugs, and expand agent capabilities for developers.
• Astral has been acquired by OpenAI (News) — Rapid shifts in developer tools highlight critical interdependencies of trust and control.
• GitHub confirms 3,800 internal repos stolen through poisoned VS Code extension as supply chain worm hits Microsoft’s Python SDK — Chained supply chain and AI agent vulnerabilities are actively exploited, bypassing traditional security measures.
• Anthropic study shows AI needs hours, not weeks, to build exploits from security patches — LLMs can build software exploits from patches in hours, not weeks, fundamentally changing cybersecurity defense timelines.
• Our response to the TanStack npm supply chain attack — Supply chain attacks targeting open-source dependencies pose a significant and evolving threat to modern software ecosystems.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.