Meta Seeks Legal Shield From Child-Harm Lawsuits Amid KOSA Talks 
Samsung Gains Interest from BYD, Google, AMD as AI Chip Demand Strains TSMC Capacity 
SpaceX Stock Slides After IPO Rally as Valuation Concerns Grow 
WiseTech Global Denies Knowledge of Investigation Into Founder Richard White 
US Raises Concerns Over Possible ASML EUV Machine Transfer to China 
SK Hynix Overtakes Samsung as South Korea’s Most Valuable Company 
Google’s Open-Source AI Data Center Cooling Design Raises Commoditization Concerns 
G7 Explores AI Access Deal With U.S. Amid Anthropic Restrictions 
John Jumper Leaves Google DeepMind for Anthropic Amid Intensifying AI Talent Race 
Apple Signals Product Price Hikes Amid Rising Memory Chip Costs 
World Cup technology: from ref cams to AI analysts, cutting-edge research is changing the game 
How AI prompting turned writerly description into an everyday skill 
Baseten Secures $1.5 Billion Funding at $13 Billion Valuation Amid AI Infrastructure Boom 
Trump Administration Delays DeepSeek and CXMT Trade Blacklist Designations Amid U.S.-China Tensions 
Trump Says Anthropic No Longer Seen as National Security Threat 
Distributed denial of service (DDoS) has been a problem for years and it would seem that GitHub just got hit by the biggest attack using the tactic in history. While this development is already disturbing enough, it might be possible that the perpetrators were only using this opportunity to test a bigger, more effective weapon in their arsenal. An even bigger attack could be on the way.
According to the site, the attack came in two waves, the first being worth 1.35Tbps, which would have been enough to overwhelm most domains’ servers. The second was smaller, at 400Gbps, but it would still have been enough to do some damage. As ZDNet points, the biggest DDoS attack before this incident clocked in at 1.1Tbps, which makes GitHub a winner of sorts.
On its engineering page, GitHub provided users with details with regards to the incident and reassured users that no data was compromised during the attack. Based on its own record, it would seem that the attack only caused minor inconvenience and only a short downtime, lasting only a few minutes.
“On Wednesday, February 28, 2018 GitHub.com was unavailable from 17:21 to 17:26 UTC and intermittently unavailable from 17:26 to 17:30 UTC due to a distributed denial-of-service (DDoS) attack. We understand how much you rely on GitHub and we know the availability of our service is of critical importance to our users. To note, at no point was the confidentiality or integrity of your data at risk. We are sorry for the impact of this incident and would like to describe the event, the efforts we’ve taken to drive availability, and how we aim to improve response and mitigation moving forward,” GitHub wrote.
As to what makes this particular attack unique, it would seem that the perpetrators used memcached traffic that’s based on UDP, which amplified the power of the DDoS strike. The two consecutive strikes were basically meant to take advantage of vulnerabilities in this particular aspect. According to security firm Akamai, this incident revealed a new method of attack for hackers, which could make it more popular.
