✓ Survived Rank 1 of 8 proposedIndie Security Oct 30, 2026

Cross-registry integrity monitoring for IDE extensions

Snapshots VS Code/Cursor/Open VSX extension releases, diffs them across registries, and alerts security teams when a tampered or divergent build ships.

Open the discussion ↗

A ready-to-paste brief for Claude Code, Cursor or any coding agent.

I want to build a small, bootstrappable product. Help me plan and start the MVP.

Product: Cross-registry integrity monitoring for IDE extensions
What it is: Snapshots VS Code/Cursor/Open VSX extension releases, diffs them across registries, and alerts security teams when a tampered or divergent build ships.
Who pays: Security engineering or platform leads at companies with 100+ developers using VS Code forks (Cursor, Windsurf); $500–2,000/mo from the software supply-chain security budget.
Closest alternatives: Socket, Snyk, Endor Labs, StepSecurity
The gap: Existing supply-chain tools watch package registries (npm, PyPI) and CI pipelines; nobody continuously monitors IDE extension marketplaces for tampered releases, publisher changes, or builds that diverge across registries.
Why now: Cursor and other VS Code forks now run their own extension marketplaces with separate, weaker publishing pipelines, and AI extension adoption exploded in the last year — this incident proves the attack path works.
Moat to build toward: Versioned historical snapshot database of extension bundles plus a growing dataset of benign-vs-malicious release diffs; switching costs from alert/MDM integrations.
Biggest risk: Marketplaces (Microsoft, Cursor, Open VSX) add mandatory signing and native anomaly detection, collapsing the gap before the customer base is built.

First three steps:
1. Build crawlers that snapshot the top ~500 extensions across the VS Code Marketplace, Open VSX, and Cursor marketplace, storing versioned bundle hashes and publisher metadata.
2. Build a diff engine flagging versions missing from other registries, publisher/signing-key changes, and new dangerous capabilities (child_process, writes to ~/.ssh, LaunchAgents).
3. Ship Slack/webhook alerting plus a dashboard where teams register the extensions their org uses.

Start by asking me up to five questions about constraints (stack, budget, timeline), then propose the smallest version a paying customer would use, and scaffold it.

Overall6.8/10

Pain7

Willingness to pay6

Timing8

Gap7

Moat5

Feasibility8

For

Who pays

Security engineering or platform leads at companies with 100+ developers using VS Code forks (Cursor, Windsurf); $500–2,000/mo from the software supply-chain security budget.

What people said · 5

A backdoored Claude Code extension sat live on the Cursor Marketplace for ~11 hours before removal, giving it full access to source code and dev tooling. From the article ↗
The compromised version appeared on Open VSX/Cursor but apparently never on the official Microsoft registry, showing dangerous cross-registry divergence. Read the comment ↗
Developers realize AI coding tools run unvetted remote code daily and nobody is checking what these CLIs and extensions actually do. Read the comment ↗
Auto-update delays don't apply to 'trusted publishers' and users can't configure which publishers to trust, so malicious updates can propagate instantly. Read the comment ↗
Expects state actors to increasingly target dev tools and open source, arguing all incoming artifacts must be treated as hostile. Read the comment ↗

Paraphrased from the discussion. Follow the links for the original comments.

Competitors and gap

SocketSnykEndor LabsStepSecurity

Existing supply-chain tools watch package registries (npm, PyPI) and CI pipelines; nobody continuously monitors IDE extension marketplaces for tampered releases, publisher changes, or builds that diverge across registries.

Why now

Cursor and other VS Code forks now run their own extension marketplaces with separate, weaker publishing pipelines, and AI extension adoption exploded in the last year — this incident proves the attack path works.

Moat · 5/10

Versioned historical snapshot database of extension bundles plus a growing dataset of benign-vs-malicious release diffs; switching costs from alert/MDM integrations.

Against

Red team: A live 11-hour backdoor on the Cursor marketplace proves the attack path, supply-chain security budgets exist, and Socket/Snyk cover npm/PyPI but not IDE extension registries with cross-registry divergence detection.
What would kill it: Marketplaces (Microsoft, Cursor, Open VSX) add mandatory signing and native anomaly detection, collapsing the gap before the customer base is built.

Start

First three steps: Build crawlers that snapshot the top ~500 extensions across the VS Code Marketplace, Open VSX, and Cursor marketplace, storing versioned bundle hashes and publisher metadata.
Build a diff engine flagging versions missing from other registries, publisher/signing-key changes, and new dangerous capabilities (child_process, writes to ~/.ssh, LaunchAgents).
Ship Slack/webhook alerting plus a dashboard where teams register the extensions their org uses.
Source discussion: Backdoor in Claude Code for VS Code extension on the Cursor Marketplace ↗ 579 points401 commentsFrom the commentsLinked article

For

Against

Start

More from this issue