As DDoS attack that started on Thursday continues, Github says it has mitigated some of the impact; Baidu denies involvement
Eva Dou / Wall Street Journal :
Context & Ripple Effects
The GreatFire report landing a day after this story is the pivot point: an anti-censorship group attributed the GitHub attack to China just as Baidu publicly denied any role, turning a traffic incident into an attribution fight. GitHub's own framing — mitigated 'some' of the impact on an attack still running days after it began Thursday — signals an unusually sustained campaign rather than a hit-and-run flood.
First-order effects
- Developers relying on GitHub face degraded availability while mitigation is partial, and Baidu is immediately put on the defensive, denying involvement in an attack others pin on Chinese state-linked actors.
Second-order effects
- Attribution shifts from the target to independent researchers — as with the later DynDNS outage traced to a Mirai botnet in XiongMai hardware, third-party forensics become the deciding voice when accused companies deny responsibility.
Third-order effects
- If politically motivated floods keep escalating against code-hosting infrastructure, the endpoint is the record-breaking territory GitHub later saw in its 1.35Tbps memcached-amplified attack, forcing continuous investment in absorption capacity as table stakes for operating developer platforms.
The trend: DDoS attacks are shifting from criminal extortion tools to instruments of geopolitical pressure aimed at open-source infrastructure.