PulseAugur
EN
LIVE 10:02:28

GitHub account rename vulnerability exposes MCP namespaces to hijacking

By PulseAugur Editorial · [1 sources] ·

A security vulnerability has been identified in the MCP namespace system, where renaming a GitHub account can lead to the old namespace being claimed by another user. This allows malicious actors to publish new, potentially harmful versions of software under an old, trusted name. Over 111 namespaces have been affected, with some packages still receiving thousands of weekly downloads. The issue stems from the registry assigning io.github namespaces based on the GitHub login name rather than a unique account ID, enabling the hijacking of namespaces after an account rename. AI

IMPACT Exposes risks in software supply chains where namespaces are tied to mutable identifiers, potentially impacting AI agent deployments.

RANK_REASON The item discusses a security vulnerability in a specific software namespace system (MCP) related to GitHub account renaming, impacting package distribution and potentially leading to malicious code execution.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

GitHub account rename vulnerability exposes MCP namespaces to hijacking

How we ranked this

Signal score
2 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
The item discusses a security vulnerability in a specific software namespace system (MCP) related to GitHub account renaming, impacting package distribution and potentially leading to malicious cod…
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, safety
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Same-day
Cluster formed today. Ranking reflects the current source set at time of score.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Iain ·

    Whoever takes your old GitHub name gets your MCP namespace

    <p>Rename your GitHub account and your MCP servers stay in the official registry under your old name. Whoever registers that name next can publish new versions of them, and the registry can't tell it isn't you.</p> <p>On 2 November I checked every <code>io.github</code> name in t…

RELATED ENTITIES

RELATED TOPICS