EARF
United States Flag
United StatesNorth America
Japan Flag
JapanAsia
Italy Flag
ItalyEurope
Netherlands Flag
NetherlandsEurope
United Kingdom Flag
United KingdomEurope
EARFSTAGE
EARFSTAGEFestivals and live sets
METAR | EARF
EARFWeatherLive weather stations
EARFWiki
EARFWikiCountries and public records
EARFguessGuess where on Earth
/cyberattack/github-ddos-attack-2018
221/430

File EL-0210HighResolvedCyberattack / Distributed Denial of Service (DDoS)

GitHub DDoS Attack (2018)

Also filed as GitHub Service Disruption · March 2018 GitHub Outage

The attack involved a massive Distributed Denial of Service (DDoS) campaign targeting GitHub's infrastructure on March 1, 2018. The disruption significantly impacted global software development, preventing developers from accessing repositories and collaboration tools. Attribution pointed toward state-sponsored actors linked to China, aiming to destabilize Western technology platforms.

  • #ddos
  • #github
  • #service-disruption
  • #china
  • #great-cannon
Notoriety7/10
Event
1 Mar 2018
Disclosed
1 Mar 2018
Target
GitHub
Actor
Great Cannon
Scale
Unknown (Volumetric)
Status
Resolved

01Summary

The incident saw GitHub, a critical platform for open-source software development, suffer a major service outage due to a coordinated DDoS attack. The attack was characterized by high volume traffic designed to overwhelm GitHub's network capacity, making core services inaccessible. While the specific technical details of the attack vector were not widely disclosed, the sheer scale of the traffic indicated a sophisticated, state-level operation. The disruption was particularly damaging because GitHub hosts millions of repositories essential for global software supply chains. The incident raised immediate concerns regarding the vulnerability of critical Western digital infrastructure to foreign state-sponsored cyber aggression, prompting calls for stronger international cyber norms.

02Background

GitHub's prominence in the global open-source ecosystem made it a high-value target for geopolitical adversaries. Prior to this incident, there was growing international concern regarding the increasing use of cyberattacks as tools of state power, particularly targeting economic and technological assets. This attack was viewed as part of a broader pattern of Chinese cyber aggression against Western interests.

03Key revelations

  1. 01The vulnerability of global open-source development to state-sponsored cyberattacks.
  2. 02The ability of foreign actors to disrupt critical Western digital infrastructure without direct physical confrontation.
  3. 03The high cost of maintaining resilience against massive, coordinated volumetric DDoS attacks.

04Technical analysis

The attack utilized volumetric DDoS techniques, aiming to saturate the network bandwidth of GitHub's data centers. Such attacks typically involve botnets of compromised IoT devices or cloud resources, generating massive amounts of junk traffic (e.g., SYN floods, UDP floods). The sophistication suggests the use of command-and-control infrastructure capable of coordinating a large, distributed attack force.

Attack vector
Volumetric DDoS (Network Layer)
Attack method
Denial of Service
Initial access
Network Flooding
Malware type
DDoS Botnet

MITRE ATT&CK techniques

  • T1499

05Threat actor

Great Cannon is an attributed moniker for cyber threat actors believed to be sponsored by the Chinese government. Their operations typically focus on disrupting foreign digital infrastructure and gathering intelligence, aligning with broader Chinese state cyber objectives.

Aliases

  • China-linked actors

MITRE groups

  • T1499

Attribution sources

  • Security Researchers
  • Industry Reports

06Victims and impact

Additional victims

  • Global software development community

Countries affected

  • USA
  • Global

07Data exposed

Data types

  • Service Availability

Notable documents

  • GitHub Status Page Alerts

08Financial damage

Damage was primarily measured in lost productivity and operational downtime for the global software industry.

09Timeline

  1. 2018-03-01DDoS attack begins, causing service degradation and eventual outage for GitHub.
  2. 2018-03-01GitHub begins public communication regarding the service disruption.

10Reaction and fallout

Public reaction

The global developer community reacted with alarm, recognizing the immediate halt to collaborative work. The incident spurred immediate discussions about the need for better global cyber resilience and the protection of open-source assets.

Political impact

The attack heightened geopolitical tensions regarding cyber warfare, particularly between the US and China. It fueled policy debates in Western nations about critical infrastructure protection and the need for international cyber norms.

Geopolitical consequences

It reinforced the narrative of cyber conflict as a primary tool of great power competition, specifically targeting the economic lifelines of Western democracies.

11Legal

No specific legal action was publicly reported against the perpetrators, as the attack was attributed to a foreign state actor.

12Aftermath

Policy changes

  • Increased focus on critical infrastructure protection (CIP) in software supply chains.

Regulatory changes

  • Calls for mandatory DDoS mitigation standards for critical online services.

Security improvements

  • Enhanced use of cloud-based scrubbing centers and advanced traffic filtering at the network edge.

13Significance and legacy

Significance

This incident is a key example of how state-sponsored actors can leverage cyberattacks to achieve geopolitical goals by disrupting the global digital economy. It demonstrated that critical infrastructure, even if decentralized like open-source code, can be brought to a standstill by sheer volume of malicious traffic.

Legacy

The attack contributed to the industry's shift toward assuming a state of perpetual cyber conflict. It accelerated the adoption of advanced, multi-layered DDoS mitigation services and increased corporate awareness of geopolitical cyber risks.

14Disclosure and media

Authentication
Industry reporting and network traffic analysis

Media partners

  • The Hacker News
  • TechCrunch

Publishing organisations

  • Security Research Firms

15Field notes

  1. 01The attack highlighted the critical dependency of modern software development on centralized, accessible platforms like GitHub.
  2. 02DDoS attacks of this nature are often difficult to trace back to a specific physical location, making attribution challenging.

16Resolution

GitHub and its cloud providers successfully mitigated the attack by implementing advanced traffic filtering and scaling up their scrubbing capacity, restoring service functionality within hours.

17Sources

Official documents

  • GitHub Status Updates (March 2018)

References

  1. [1]Security Industry Reports on DDoS Attacks
  2. [2]Tech News Coverage of 2018 Outage
Fact sheetEL-0210

Dates

Event
1 Mar 2018
Started
1 Mar 2018
Ended
1 Mar 2018
Duration
1 days
Discovered
1 Mar 2018
Disclosed
1 Mar 2018
Resolved
1 Mar 2018
Ongoing
No

Target

Organisation
GitHub, Inc.
Type
Technology Company
Sector
Software Development/Cloud Hosting
Country
USA

Actor

Name
Great Cannon
Type
Nation-State Actor
Nationality
China
Nation-state
China
Motivation
Geopolitical disruption, targeting Western technology infrastructure, or intellectual property theft.
Attribution
Medium
Status
Active
Arrested
No
Convicted
No

Data

Volume
Unknown (Volumetric)
Sensitivity
Internal
Published
No

EARFLeaks documents publicly known security incidents. It does not host, store or distribute leaked data.

© 2026 EARF. All rights reserved.