GitHub Empire on the Brink of Collapse: Source Code Leak, 18-Year Veteran Leaves, Microsoft Loses 1.5 Billion Developers

marsbitPubblicato 2026-05-22Pubblicato ultima volta 2026-05-22

Introduzione

GitHub is facing an unprecedented crisis, marked by a massive exodus of developers and severe operational failures. The tipping point came when Mitchell Hashimoto, creator of Ghostty and an 18-year GitHub user, publicly severed ties, citing persistent platform outages that made serious work impossible. This departure highlights a broader pattern of user frustration. The platform's instability has drawn complaints from major corporate clients like Citibank and Intel, forcing Microsoft to issue substantial service credits. A critical incident last month saw an accidentally triggered, unreleased feature cause widespread repository rollbacks, erasing recent code changes and pushing enterprises to migrate. Security has catastrophically breached. In May 2026, hackers infiltrated over 3,800 of GitHub's internal repositories via a poisoned VS Code extension installed by a developer, leading to the attempted sale of core source code for $50,000. This follows the discovery of a critical zero-day vulnerability in March that threatened access to millions of repositories. Internally, GitHub's autonomy has collapsed. After the resignation of CEO Thomas Dohmke in mid-2025, Microsoft eliminated the CEO role, folding GitHub into its CoreAI division under the unpopular leadership of Jay Parikh. This triggered a talent drain, with key executives and engineers leaving. A disruptive migration of GitHub's infrastructure to Azure servers, pushed by CTO Vladimir Fedorov, is blamed for the recurri...

GitHub is experiencing an unprecedented major collapse.

Recently, the global open-source tech community witnessed a shocking rift.

Mitchell Hashimoto, an 18-year veteran fan of GitHub and the famous developer of the Ghostty terminal, posted a sensational 'farewell letter' that went viral—every word bleeding with pain.

GitHub fails me every day.

I wish it were better, but I want to program more. I can no longer program using GitHub. I'm sorry, after 18 years, I have to go.

If a platform locks you out for hours every day, it is no longer suitable for serious work.

Subsequently, Ghostty packed up all its assets and decisively left.

His departure is just the tip of the iceberg in an avalanche.

GitHub's Life or Death

In recent months, giants like Citibank and Intel have expressed dissatisfaction to Microsoft over GitHub's ongoing failures. Even OpenAI has begun exploring self-built solutions.

To appease customers, Microsoft had to issue a large number of Credits to enterprise users as compensation for losses, leading directly to a bleeding of profits.

The most severe incident occurred last month: a mistakenly triggered, unreleased feature on GitHub caused numerous repositories to 'roll back,' with recent code modifications disappearing directly. Many enterprises have been forced to migrate.

Nearly eight years ago, when Microsoft acquired GitHub for $7.5 billion, global programmers were filled with concern.

As expected, after a brief golden period, this 'programmer's sanctuary'—hosting over 1.5 billion developers and 10 billion code repositories worldwide—now stands at a critical juncture of life or death in an extremely brutal manner.

3800+ Repositories 'Wiped Out' by Hackers

Even more serious, a recent security storm has completely stripped GitHub bare.

On May 21, 2026, a message instantly exploded on the hacker forum BreachForums: a hacker group openly offered GitHub's core source code for sale at a mere $50,000!

They arrogantly wrote:

Everything of the main platform is here. I would be happy to send samples to interested buyers for verification. This is not blackmail; we are too lazy to extort GitHub. If one person buys, we will completely destroy the data. If no buyer is found, we will soon make it public for free.

Subsequently, GitHub officially reluctantly confirmed: over 3,800 internal code repositories were indeed compromised.

The origin of this disaster is absurdly unbelievable: a GitHub internal developer installed a malicious, poisoned VS Code extension plugin on their work device. After credentials were leaked, over 3,800 repositories were breached.

VS Code and GitHub, both belonging to Microsoft, should have been a 'family ecosystem combination.' However, VS Code plugins lack high-intensity review mechanisms, making them the perfect entry point for hackers.

Because VS Code frequently prompts developers to install various plugins, these 'Trojan horses' can freely access local files, system terminals, etc.

When the GitHub engineer downloaded the malicious plugin, their long-term valid personal access token was instantly intercepted by the hackers!

For a platform built on 'code security and hosting,' having its source code publicly offered for sale is undoubtedly a resounding slap in the face.

This is just the tip of the iceberg.

In March of this year, security agencies discovered a 0-day-level critical vulnerability in GitHub's internal Git infrastructure.

If exploited, attackers could directly and unlimitedly access millions of public and private code repositories across the entire network, with consequences a hundred times more terrifying than this incident!

Management Shake-up: No More CEO, Reduced to a Microsoft Vassal

Behind the frequent security and technical incidents is GitHub's internal 'leaderless state' for nearly a year.

Last summer, the beloved former CEO Thomas Dohmke suddenly resigned. Microsoft then made a decision that shocked all employees: completely abolish the GitHub CEO position.

GitHub CEO Thomas Dohmke

Dohmke thanked everyone: 'GitHub has never been stronger, with over 1 billion repositories and branches, and over 1.5 billion developers. It is thanks to your relentless efforts that GitHub Copilot has brought the biggest transformation in software development since the advent of the PC.'

For seven years, GitHub proudly maintained its status as an 'independent subsidiary.' But last summer, it was merged into the newly formed CoreAI team.

This drastic change directly pushed GitHub executives into an awkward position: they lost their direct line of communication with Microsoft's top leadership and were forced to report to Parikh, the head of the CoreAI team and former Meta executive.

However, Parikh is extremely unpopular internally. It was he who insisted on erasing the GitHub CEO position.

'There's basically no GitHub here anymore; it's now completely a department of Microsoft,' one senior employee angrily stated. 'Management and technical talent are fleeing madly.'

This was followed by a loss of top talent: former CEO Dohmke founded the next-generation developer platform Entire, poaching 11 people; 34-year veteran Julia Liuson resigned; Senior Vice President of Product Engineering Jared Palmer transferred to the Xbox team; the Chief Revenue Officer resigned.

Current CTO Vladimir Fedorov aggressively promoted the project to migrate GitHub to Azure servers. This complex MySQL cluster relocation directly caused the chain of outages over the past year.

Thus, GitHub's R&D, finance, and marketing have been comprehensively strangled and devoured. Internally, there is division and discord, with the loss of technical backbone.

GitHub's once-proud 'pure developer culture' is being gnawed away by Microsoft's bureaucratic and powerful system!

Moat Breached: Cursor and Claude Code's Dimensional Reduction Strike

The external outages and internal turmoil have torn open huge cracks for predators.

Once, Copilot was almost synonymous with AI-assisted programming.

However, in 2024, Cursor emerged out of nowhere. While GitHub Copilot was still stuck in the 'you write a line, I guess the next line' code completion stage, Cursor could already understand the entire project context and generate entire modules with one click.

In 2025, Claude Code launched a dimensional reduction strike—it could not only write code but also automate complex debugging, testing, and multi-file collaborative modifications.

Microsoft was thrown into unprecedented panic internally. According to leaks, Jay Parikh warned with an ashen face in a meeting: GitHub is facing a 'death threat.'

Parikh's core fear is: once developers get used to completing all development in Cursor, they will no longer upload their code to GitHub.

To this end, Microsoft seriously evaluated acquiring Cursor but hesitated for a moment. In the blink of an eye, Cursor was snapped up by SpaceX.

What's even more amusing is that Claude Code is so incredibly good that tens of thousands of engineers in Microsoft's Windows and Office departments have all become die-hard fans of CC. Microsoft executives were completely broken!

Rajesh Jha issued a strict order to all staff, forcibly revoking all CC licenses by the end of June and forcing engineers to revert to using GitHub Copilot CLI.

Financial Avalanche: The 'Subsidy Black Hole' of Making More Money, Losing More Money

Moreover, GitHub's commercial operations are also deeply mired, even starting to backfire on Microsoft.

On the surface, GitHub's data still looks impressive. By the end of 2025, Copilot paid users surpassed 4.7 million, and GitHub's annual recurring revenue crossed the $3 billion threshold.

But behind the pretty numbers, it's all Microsoft's blood.

With the AI explosion, GitHub traffic surged 14 times. However, AI features for code hosting and open-source projects remain completely free.

Meanwhile, the inference costs for running AI models remain high. The computing power consumed by heavy users far exceeds the $10 monthly subscription fee—the more they sell, the more they lose.

During Microsoft's earnings call in April this year, the CFO rarely admitted: the significant increase in GitHub Copilot usage directly lowered the gross margin of the entire core cloud business.

Under pressure from Wall Street, GitHub announced last month: abolish the unlimited monthly usage model and fully transition to 'pay-as-you-go.' Once credits are depleted, AI services are immediately cut off.

This move, perceived as greedy, completely infuriated developers!

The global IT services giant NinjaOne immediately publicly stated: they are comprehensively guiding engineers to abandon GitHub and turn to the Claude Code ecosystem.

Will GitHub Die?

This year, Microsoft's stock price has fallen by over 10%, performing the worst among the 'Magnificent Seven' tech stocks.

Its developer ecosystem cornerstone, GitHub, is pushing everything toward the abyss.

To break free from dependence on OpenAI and Anthropic, CoreAI has ordered the comprehensive collection of all code to train Microsoft's own native large model.

This practice of recklessly depleting the ecosystem for its own benefit has completely chilled developers worldwide.

The trust of the open-source community, the neutral ecological environment, and the free, pure developer culture are rapidly vanishing from this $7.5 billion behemoth.

Now, the most fatal question facing Satya Nadella is: In the era of AI agents, do global developers still need a central code repository platform like GitHub?

If Microsoft cannot provide a convincing answer, it will lose the soul it has cultivated around its ecosystem for decades—

'Developers, developers, developers!'

References:

https://www.theverge.com/tech/935250/microsoft-github-struggles-notepadhttps://mitchellh.com/writing/ghostty-leaving-githubhttps://www.wired.com/story/teampcp-software-supply-chain-attack-spree-github/?utm_source=chatgpt.com

This article comes from the WeChat public account "Xinzhiyuan," author: ASI Revelation.

Domande pertinenti

QWho is Mitchell Hashimoto and what significant action did he take regarding GitHub?

AMitchell Hashimoto is the developer of the Ghostty terminal and a long-time GitHub user. He recently announced his departure from the platform, citing frequent outages that prevented serious work, and moved the Ghostty project assets away from GitHub.

QWhat major security incident involving GitHub's source code is detailed in the article?

AA hacker group breached and stole the source code for over 3,800 of GitHub's internal repositories. The breach originated from a GitHub engineer installing a malicious VS Code extension, which compromised their credentials, allowing the hackers to access and later attempt to sell the code.

QHow has Microsoft's internal restructuring impacted GitHub's leadership?

AMicrosoft disbanded GitHub's independent subsidiary status and merged it into the CoreAI team. The CEO position was eliminated, and GitHub's leadership now reports to the CoreAI head, Jay Parikh, leading to a loss of autonomy, internal dissatisfaction, and a significant exodus of senior talent.

QWhat competitive threats to GitHub Copilot are mentioned, and what was Microsoft's internal reaction?

AThe article cites Cursor and Claude Code as major competitive threats, offering more advanced AI-assisted programming features. Microsoft was internally alarmed, with executives describing it as an 'existential threat.' Notably, many Microsoft engineers preferred using Claude Code, prompting management to forcibly revoke its licenses within the company.

QWhat financial and operational challenges is GitHub facing according to the article?

AGitHub is struggling with profitability despite high revenue. The massive computational costs of running free AI features like Copilot exceed subscription income, negatively impacting Microsoft's cloud margins. In response, GitHub shifted from a flat-rate subscription to a pay-as-you-go model, which angered many developers and prompted some companies to consider alternatives.

Letture associate

GitHub, Transfixed by AI

On the night of February 9th, GitHub suffered a major outage caused by a simple configuration change—reducing a cache refresh interval from 12 to 2 hours—that triggered a cascade of failures. This was not an isolated event, but part of a broader pattern. In early 2026, GitHub experienced at least 8 major incidents, failing to meet its promised 99.9% availability. These outages stemmed from structural issues: explosive growth in load, tight service coupling, and insufficient protection against abnormal traffic. This unprecedented load is driven by AI Agents. In 2025, GitHub handled ~1 billion commits. By 2026, weekly commits reached 275 million, projecting to ~14 billion for the year—a 14x increase. AI tools like Claude Code now contribute 4.5% of all public repository commits, with weekly submissions surging 25x in just three months. AI-generated pull requests jumped from 4 million to 17 million per month in half a year. Unlike human developers, AI Agents work continuously, generating commits at a scale that overwhelms infrastructure designed for human rhythms. The surge also shattered GitHub's business model. Copilot's flat-rate pricing, based on assisting human developers, became unsustainable as Agentic AI sessions consumed resources worth hundreds of dollars for a few dollars in fees. In response, GitHub imposed usage limits and, by June 1st, shifted to a pay-per-use "AI Credits" system. Facing this new reality, GitHub realized a 10x scaling plan was insufficient. It announced a need to *redesign* its architecture for 30x current scale—decoupling services, adding fault isolation, and improving change management to prevent cascading failures. Other platforms like Stripe and AWS are facing similar challenges with AI Agents. Fundamentally, GitHub is transitioning from a human collaboration platform to an "exhaust pipe" for automated AI workflows. Its detailed post-mortem reports aim to maintain trust during this turbulent rebuild. The February outage was not just a technical glitch, but a signal of the software industry's entry into a new, AI-driven era.

marsbit19 min fa

GitHub, Transfixed by AI

marsbit19 min fa

Both Suffer Massive Losses Exceeding $90 Billion, Which Is in Greater Peril: Strategy or Bitmine?

Facing massive paper losses exceeding $90 billion each amidst a sharp market downturn, "Digital Asset Treasury" (DAT) giants Strategy and Bitmine find themselves in a precarious position, but with different underlying risks. Strategy, heavily invested in Bitcoin (BTC), faces significant financial strain. Its strategy relies heavily on debt, including convertible notes and preferred stock (STRC) requiring substantial dividend payments. With its cash reserves dwindling and BTC offering no staking yield for cash flow, Strategy's high leverage makes it vulnerable. A continued price decline could force asset sales to meet obligations, potentially creating a negative feedback loop. Its market value has already fallen sharply. In contrast, Bitmine, an Ethereum (ETH) holder, appears on firmer financial ground. It primarily funds its purchases through equity offerings (like ATM programs), avoiding debt pressure. It also generates income by staking a large portion of its ETH holdings. While not immune to market drops and shareholder dilution concerns, Bitmine maintains more flexibility, recently announcing a new preferred share offering to raise further capital. The core divergence lies in their financing: Bitmine uses equity (investor money), while Strategy uses debt (borrowed money). Consequently, Bitmine currently faces less immediate liquidity pressure than Strategy, which must navigate the dual challenge of servicing debt/dividends and a declining core asset (BTC) price.

marsbit26 min fa

Both Suffer Massive Losses Exceeding $90 Billion, Which Is in Greater Peril: Strategy or Bitmine?

marsbit26 min fa

Where the AI Bubble Really Is: Which Layer of Players Are Naked

AI Bubble: Where It Really Is and Who's Swimming Naked This analysis dissects the AI industry not as a single entity but as a five-layer pyramid, arguing that bubbles are concentrated in specific tiers, not uniformly distributed. **Key Distinction from the 2000 Dot-com Bubble:** Unlike 2000, where companies had stock prices before revenue, today's leading AI players have massive, contract-backed revenue driving their valuations. Core infrastructure demand is real, with every GPU running at full capacity for paying customers. **The Five-Layer Pyramid & Bubble Assessment:** * **L0 (Fab/Manufacturing) & Top L4 (Leading AI Apps): NO BUBBLE.** Companies like TSMC, NVIDIA, major cloud providers (Microsoft, Google, Meta, Amazon), and top AI labs have real revenues and orders. Supply is tightly constrained by TSMC's disciplined capacity control and physical limits like power/land for data centers, preventing a supply glut. * **L1 (Memory): BATTLEGROUND.** Sky-high HBM margins could signal a new structural cycle or a classic "boom before bust." The oligopoly of three major players may enforce supply discipline, making this a high-stakes bet. * **L2 (Interconnect/Optical Modules): BUBBLE TERRITORY.** Companies like Lumentum and AAOI have seen stock surges (4-10x) far outpacing revenue growth. This hardware segment has lower physical barriers to expansion than fabs, allowing speculation. It mirrors the 2000 bubble's epicenter—optics. * **L3 (Infrastructure/"GPU Landlords"): VULNERABLE.** GPU leasing companies profit from the current compute shortage but own no long-term moat. Their business model relies on a temporary bottleneck that will ease as big tech expands and new tech (e.g., potential space-based data centers) emerges. * **L4 Long Tail (VC-backed Startups): STRONG BUBBLE SIGNALS.** VC funding concentration in AI is twice that of the 1999 peak. Many startups with little revenue use the valuation logic of successful giants to justify their own, creating high risk of a "valuation crunch" when funding dries up. **Critical Risks to Monitor:** 1. **GPU Depreciation & Accounting:** Companies extending the assumed useful life of GPUs artificially boost profits. The true economic life depends on future generational leaps from NVIDIA. 2. **"GPU Credit" & Off-Balance-Sheet Leverage:** Emerging structures where shell companies borrow to buy GPUs and lease them out (with chipmakers sometimes investing) move debt off major balance sheets. This echoes the "vendor financing" of 2000 and the securitization risks of 2008, though currently small-scale. 3. **TSMC Abandoning Caution:** If the primary supply bottleneck (TSMC's conservative capacity planning) breaks, runaway supply could trigger a bust. 4. **Algorithmic Efficiency Breakthrough:** A major leap in software efficiency could drastically reduce the need for raw compute hardware, undermining the investment thesis. **Conclusion:** The AI boom is expensive and has frothy areas, but its core is underpinned by real demand and physical supply constraints. The bubble risk is layered: most present in optical components, GPU leasing, and the long-tail startup ecosystem, while the foundational chip manufacturing and leading application layers remain relatively solid—for now.

marsbit39 min fa

Where the AI Bubble Really Is: Which Layer of Players Are Naked

marsbit39 min fa

Trading

Spot
Futures

Articoli Popolari

Come comprare OP

Benvenuto in HTX.com! Abbiamo reso l'acquisto di Optimism (OP) semplice e conveniente. Segui la nostra guida passo passo per intraprendere il tuo viaggio nel mondo delle criptovalute.Step 1: Crea il tuo Account HTXUsa la tua email o numero di telefono per registrarti il tuo account gratuito su HTX. Vivi un'esperienza facile e sblocca tutte le funzionalità,Crea il mio accountStep 2: Vai in Acquista crypto e seleziona il tuo metodo di pagamentoCarta di credito/debito: utilizza la tua Visa o Mastercard per acquistare immediatamente OptimismOP.Bilancio: Usa i fondi dal bilancio del tuo account HTX per fare trading senza problemi.Terze parti: abbiamo aggiunto metodi di pagamento molto utilizzati come Google Pay e Apple Pay per maggiore comodità.P2P: Fai trading direttamente con altri utenti HTX.Over-the-Counter (OTC): Offriamo servizi su misura e tassi di cambio competitivi per i trader.Step 3: Conserva Optimism (OP)Dopo aver acquistato Optimism (OP), conserva nel tuo account HTX. In alternativa, puoi inviare tramite trasferimento blockchain o scambiare per altre criptovalute.Step 4: Scambia Optimism (OP)Scambia facilmente Optimism (OP) nel mercato spot di HTX. Accedi al tuo account, seleziona la tua coppia di trading, esegui le tue operazioni e monitora in tempo reale. Offriamo un'esperienza user-friendly sia per chi ha appena iniziato che per i trader più esperti.

473 Totale visualizzazioniPubblicato il 2024.12.12Aggiornato il 2026.06.02

Come comprare OP

Discussioni

Benvenuto nella Community HTX. Qui puoi rimanere informato sugli ultimi sviluppi della piattaforma e accedere ad approfondimenti esperti sul mercato. Le opinioni degli utenti sul prezzo di OP OP sono presentate come di seguito.

活动图片