Saturday, December 28, 2024
HomeDDOSMemcache Based DDOS Attack Heavily Targeted NRA and Highly Ranked Top Order...

Memcache Based DDOS Attack Heavily Targeted NRA and Highly Ranked Top Order Websites

Published on

SIEM as a Service

The Memcached-Based DDOS attack heavily targeted NRA Websites and also targeting top order website such as QQ.com and 360.com.

 The National Rifle Association is America’s longest-standing civil rights organization. The National Rifle Association of America (NRA) is an American nonProfit Organization that advocates for gun rights.

Apart from NRA, attack targets top order companies such as Google, Amazon, PornHub, PSN via vulnerable Memcached servers.

- Advertisement - SIEM as a Service

Memcached-Based DDOS attack Activities

Since 2018 february, the frequency of Memcache Based DDOS Attack have increased dramatically. As shown in the following two figures:

Netlab has been roughly divided this period of time into the following stages.

  • Prior to 2018-02-24, the daily average was less than 50 attacks.
  • The first stage: 02-24 ~ 02-28, an average of 372 attacks per day
  • Stage 2: 03-01 ~ 03-05, average daily 1938 attacks.
  • 03-08, 721 attacks already took place today, with 12 more hours to go

The above figure is the number of daily active reflectors. That is, these memcache servers actually participated in real attacks and later the Memcache Based DDOS Attack vector was stabled.

Researchers conducted real test on the 15k active reflectors on Mar 07. Roughly 15% of them respond to the “stats” command we request and thus indeed have the ability to engage in actual attacks.

Github Memcache Based DDOS Attack 

GitHub DDoS attack recorded the largest yet DDoS attack that peaked at 1.35Tbps via 126.9 million packets per second. The Volumetric DDOS attack takes place between 17:21 and 17:30 UTC on February 28th.

According to netlab, they observed two Memcache Based DDOS Attack against github, . The former is the one publicly documented.

  • Victim IP: 192.30.252.113
  • Fired at: 2018-03-01 14:26:22 GMT +8 and 2018-03-02 01:13:44 GMT +8 respectively.
  • Source Port: UDP 11211 source port
  • Attack Type: udp@attack@amp_flood_target-MEMCACHE

All these technical features are consistent with github’s public documents.

The recent victims are mainly concentrated in the United States, China (including Hong Kong, China), South Korea, Brazil, France, Germany, the United Kingdom, Canada, and the Netherlands.

There are some target IPs and their rank listed below :

Target IP                       Rank              Belongs to SLD
59.37.x.x                         09                    qq.com
36.110.x.x                       21                    360.cn
192.30.x.x                       74                    github.com
151.101.x.x                     80                    pinterest.com

IN this case with in 7 days, 10k attack events and  7131 unique victim IP addresses has been logged.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Europol Shutsdown 27 DDoS Service Provider Platforms

In a major international operation codenamed “PowerOFF,” Europol, collaborating with law enforcement agencies across...

Hackers Exploit Docker Remote API Servers To Inject Gafgyt Malware

Attackers are exploiting publicly exposed Docker Remote API servers to deploy Gafgyt malware by...