Memcache UDP Reflection Amplification Attack II: The Targets, the Sources and Breakdowns
<!--kg-card-begin: markdown--><p>In less then ten days, Memcache DDoS attack has come out of nowhere and really captured lots of attentions within the security community. When we look at the news, we see all sort of reports but hardly can get a good idea what the real situation is, for example the most important question, how many victims are out there? And how big the attack army is?</p>
<p>Our team has been running the free <a href="https://ddosmon.net/memcached_amplification_attack">ddosmon</a> platform for quite some time and with all the massive amount of network data we have good visibility into the ddos world, so, in this blog, we will provide our insights.</p>
<h4 id="thegeneraltrend">The General Trend</h4>
<p>In our previous <a href="__GHOST_URL__/what-we-know-about-memcache-udp-reflection-ddos/">blog</a> we mentioned that there had been hardly any Memcache DDoS  attacks in the last 9 months since our 360 0kee team publicly disclosed this vulnerability. However, since 2018-02-24, the frequency of attacks has increased dramatically. As shown in the following two figures:</p>
<p><img src="__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.1month-3.png" alt="" loading="lazy"><br>
<img src="__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.datasheet.1month-2.png" alt="" loading="lazy"></p>
<p>We can roughly divide this period of time into the following stages.</p>
<ul>
<li>Prior to 2018-02-24, the daily average was less than 50 attacks.</li>
<li>The first stage: 02-24 ~ 02-28, an average of 372 attacks per day</li>
<li>Stage 2: 03-01 ~ 03-05, average daily 1938 attacks</li>
<li>03-08, 721 attacks already took place today, with 12 more hours to go</li>
</ul>
<p><img src="__GHOST_URL__/content/images/2018/03/memcache.drdos.reflector.trend.1month.png" alt="" loading="lazy"></p>
<p>The above figure is the number of daily active reflectors. That is, these memcache servers actually participated in real attacks. After the rapid growth on Feb 24, 2018,, the number of daily active reflectors has been stable.</p>
<p>We also took a real test on the 15k active reflectors on Mar 07. Roughly 15% of them  respond to the &quot;stats&quot; command we request and thus indeed have the ability to engage in actual attacks.</p>
<p>In this case, the ratio at 15% looks a bit low. Maybe more tests needed to understand the situation.</p>
<h4 id="githubattacks">Github attacks</h4>
<p>In the past ten days, quite a few popular websites became victims of this DDoS attack. For example, in github around Feb 28 17:20 UTC suffered a DDoS attack, the peak flow rate reached 1.35Tbps, according to <a href="https://blogs.akamai.com/2018/03/memcached-fueled-13-tbps-attacks.html">akamai</a> and <a href="https://blogs.akamai.com/2018/03/memcached-fueled-13-tbps-attacks.html">github</a>.</p>
<p>Correspondingly, our DDoSmon platform observed two attacks against github, . The former is the one publicly documented.</p>
<ul>
<li><strong>Victim IP</strong>: 192.30.252.113</li>
<li><strong>Occurred at</strong>: 2018-03-01 14:26:22 GMT +8 and 2018-03-02 01:13:44 GMT +8 respectively</li>
<li><strong>Source Port</strong>: UDP 11211 source port</li>
<li><strong>Attack Type</strong>: tagged as &quot;<strong>udp@attack@amp_flood_target-MEMCACHE</strong>&quot;</li>
</ul>
<p>All these technical features are consistent with github's public documents.</p>
<p><img src="__GHOST_URL__/content/images/2018/03/github.under.attack.png" alt="" loading="lazy"></p>
<p>Next, let’s take a look at the most recent 7 days of data on DDoSMon for some detailed breakdown.</p>
<h4 id="thetargets">The Targets</h4>
<p>In just 7 days, our DDoSmon platform logged:</p>
<ul>
<li>10k attack events</li>
<li>7131 unique victim IP addresses</li>
</ul>
<p>In order to make the result more readable, we use our PDNS system to map the victim IPs back to their dns names. Within them, 981 (13%) have recently (within a week) resolvable domain names, and 15k (22%) have historically had domain names.</p>
<p>For all the targets above which have dns names, we checked Alexa top 1m domain list and our Float top 1m to generat two lists.(Float is our internal domain popular ranking system with a focus visits mainly in China.)</p>
<p>Here is a snip for alexa(please bear in mind that we use the most recent PDNS to map the IPs, also we only keep the SLD, not the whole FQDN, so attack against a.com is mostly like attack against subdomains such as zyx.a.com, not necessary a.com itself.</p>
<pre><code>target_ip	rank	belongs to sld
59.37.97.93	9	qq.com
182.254.79.46	9	qq.com
36.110.213.82	21	360.cn
216.18.168.16	32	pornhub.com
192.30.255.113	74	github.com
192.30.253.125	74	github.com
192.30.253.113	74	github.com
192.30.253.112	74	github.com
151.101.128.84	80	pinterest.com
104.155.208.139	112	googleusercontent.com
</code></pre>
<p>Snip for float</p>
<pre><code>target_ip	rank	fqdn
115.239.211.112	12	www.a.shifen.com
182.254.79.46	21	mp.weixin.qq.com
59.37.97.93	464	pingma.qq.com
114.80.223.177	587	interface.hdslb.net
47.91.19.168	587	interface.hdslb.net
222.186.35.81	587	interface.hdslb.net
114.80.223.172	587	interface.hdslb.net
140.205.32.8	867	sh.wagbridge.aliyun.com.gds.alibabadns.com
114.80.223.177	1052	bilibili.hdslb.net
47.91.19.168	1052	bilibili.hdslb.net
</code></pre>
<p>These two lists can be downloaded <a href="__GHOST_URL__/file/memcache.drdos.victim.in.alexa.top.1m.txt">here</a> and  <a href="__GHOST_URL__/file/memcache.drdos.victim.in.float.top.1m.txt">here</a>.</p>
<p>Take a look at both lists, you will spot lots of interesting targets. For example:</p>
<ul>
<li><strong>The regular big players</strong> such as qq,360, google, amamzon.etc</li>
<li><strong>The game industry</strong> such as rockstargames.com, minecraft.net, playstation.net</li>
<li><strong>The porn sites</strong> such as pornhub.com, homepornbay.com</li>
<li><strong>The security industry</strong> such Avast.com, kaspersky-labs.com, 360.cn</li>
<li><strong>The political</strong> related websites such as nra.org, nrafoundation.org ,nracarryguard.com, epochtimes.com</li>
<li>And the guy who always gets to see the newest ddos attack: <strong>krebsonsecurity.com</strong> :)</li>
</ul>
<p>Victims' geo distribution:</p>
<p><img src="__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.victims.geo.distribution.7days-1.png" alt="" loading="lazy"></p>
<p>And asn distribution:</p>
<p><img src="__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.victims.asn.distribution.7days-1.png" alt="" loading="lazy"></p>
<p>Overall, the current 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.</p>
<h4 id="honeypotdata">Honeypot Data</h4>
<p>We set up a honeypot for this type of attack and filtered out over 37k attack instructions.</p>
<p>As shown in the following table, 99% of the attack instructions are based on memcache STATS directives.</p>
<p><img src="__GHOST_URL__/content/images/2018/03/most.attacks.in.real.world.are.stats.command.png" alt="" loading="lazy"></p>
<!--kg-card-end: markdown-->
In less then ten days, Memcache DDoS attack has come out of nowhere and really captured lots of attentions within the security community. When we look at the news, we see all sort of reports but hardly can get a good idea what the real situation is, for example the most important question, how many victims are out there? And how big the attack army is?


Our team has been running the free ddosmon platform for quite some time and with all the massive amount of network data we have good visibility into the ddos world, so, in this blog, we will provide our insights.


The General Trend


In our previous blog we mentioned that there had been hardly any Memcache DDoS attacks in the last 9 months since our 360 0kee team publicly disclosed this vulnerability. However, since 2018-02-24, the frequency of attacks has increased dramatically. As shown in the following two figures:







We can roughly divide 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. After the rapid growth on Feb 24, 2018,, the number of daily active reflectors has been stable.


We also took a 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.


In this case, the ratio at 15% looks a bit low. Maybe more tests needed to understand the situation.


Github attacks


In the past ten days, quite a few popular websites became victims of this DDoS attack. For example, in github around Feb 28 17:20 UTC suffered a DDoS attack, the peak flow rate reached 1.35Tbps, according to akamai and github.


Correspondingly, our DDoSmon platform observed two attacks against github, . The former is the one publicly documented.


 * Victim IP: 192.30.252.113
 * Occurred 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: tagged as "udp@attack@amp_flood_target-MEMCACHE"


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





Next, let’s take a look at the most recent 7 days of data on DDoSMon for some detailed breakdown.


The Targets


In just 7 days, our DDoSmon platform logged:


 * 10k attack events
 * 7131 unique victim IP addresses


In order to make the result more readable, we use our PDNS system to map the victim IPs back to their dns names. Within them, 981 (13%) have recently (within a week) resolvable domain names, and 15k (22%) have historically had domain names.


For all the targets above which have dns names, we checked Alexa top 1m domain list and our Float top 1m to generat two lists.(Float is our internal domain popular ranking system with a focus visits mainly in China.)


Here is a snip for alexa(please bear in mind that we use the most recent PDNS to map the IPs, also we only keep the SLD, not the whole FQDN, so attack against a.com is mostly like attack against subdomains such as zyx.a.com, not necessary a.com itself.


target_ip	rank	belongs to sld
59.37.97.93	9	qq.com
182.254.79.46	9	qq.com
36.110.213.82	21	360.cn
216.18.168.16	32	pornhub.com
192.30.255.113	74	github.com
192.30.253.125	74	github.com
192.30.253.113	74	github.com
192.30.253.112	74	github.com
151.101.128.84	80	pinterest.com
104.155.208.139	112	googleusercontent.com



Snip for float


target_ip	rank	fqdn
115.239.211.112	12	www.a.shifen.com
182.254.79.46	21	mp.weixin.qq.com
59.37.97.93	464	pingma.qq.com
114.80.223.177	587	interface.hdslb.net
47.91.19.168	587	interface.hdslb.net
222.186.35.81	587	interface.hdslb.net
114.80.223.172	587	interface.hdslb.net
140.205.32.8	867	sh.wagbridge.aliyun.com.gds.alibabadns.com
114.80.223.177	1052	bilibili.hdslb.net
47.91.19.168	1052	bilibili.hdslb.net



These two lists can be downloaded here and here.


Take a look at both lists, you will spot lots of interesting targets. For example:


 * The regular big players such as qq,360, google, amamzon.etc
 * The game industry such as rockstargames.com, minecraft.net, playstation.net
 * The porn sites such as pornhub.com, homepornbay.com
 * The security industry such Avast.com, kaspersky-labs.com, 360.cn
 * The political related websites such as nra.org, nrafoundation.org ,nracarryguard.com, epochtimes.com
 * And the guy who always gets to see the newest ddos attack: krebsonsecurity.com :)


Victims' geo distribution:





And asn distribution:





Overall, the current 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.


Honeypot Data


We set up a honeypot for this type of attack and filtered out over 37k attack instructions.


As shown in the following table, 99% of the attack instructions are based on memcache STATS directives.




{"version":"0.3.1","markups":[],"atoms":[],"cards":[["markdown",{"cardName":"card-markdown","markdown":"In less then ten days, Memcache DDoS attack has come out of nowhere and really captured lots of attentions within the security community. When we look at the news, we see all sort of reports but hardly can get a good idea what the real situation is, for example the most important question, how many victims are out there? And how big the attack army is?\n\nOur team has been running the free [ddosmon](https://ddosmon.net/memcached_amplification_attack) platform for quite some time and with all the massive amount of network data we have good visibility into the ddos world, so, in this blog, we will provide our insights.\n\n#### The General Trend\n\nIn our previous [blog](__GHOST_URL__/what-we-know-about-memcache-udp-reflection-ddos/) we mentioned that there had been hardly any Memcache DDoS  attacks in the last 9 months since our 360 0kee team publicly disclosed this vulnerability. However, since 2018-02-24, the frequency of attacks has increased dramatically. As shown in the following two figures:\n\n\n![](__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.1month-3.png)\n![](__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.datasheet.1month-2.png)\n\nWe can roughly divide this period of time into the following stages. \n\n - Prior to 2018-02-24, the daily average was less than 50 attacks.\n - The first stage: 02-24 ~ 02-28, an average of 372 attacks per day\n - Stage 2: 03-01 ~ 03-05, average daily 1938 attacks\n - 03-08, 721 attacks already took place today, with 12 more hours to go\n\n![](__GHOST_URL__/content/images/2018/03/memcache.drdos.reflector.trend.1month.png)\n\nThe above figure is the number of daily active reflectors. That is, these memcache servers actually participated in real attacks. After the rapid growth on Feb 24, 2018,, the number of daily active reflectors has been stable.\n\nWe also took a 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.\n\nIn this case, the ratio at 15% looks a bit low. Maybe more tests needed to understand the situation.\n\n#### Github attacks\n\nIn the past ten days, quite a few popular websites became victims of this DDoS attack. For example, in github around Feb 28 17:20 UTC suffered a DDoS attack, the peak flow rate reached 1.35Tbps, according to [akamai](https://blogs.akamai.com/2018/03/memcached-fueled-13-tbps-attacks.html) and [github](https://blogs.akamai.com/2018/03/memcached-fueled-13-tbps-attacks.html).\n\nCorrespondingly, our DDoSmon platform observed two attacks against github, . The former is the one publicly documented.\n\n - **Victim IP**: 192.30.252.113 \n - **Occurred at**: 2018-03-01 14:26:22 GMT +8 and 2018-03-02 01:13:44 GMT +8 respectively\n - **Source Port**: UDP 11211 source port\n - **Attack Type**: tagged as \"**udp@attack@amp\\_flood\\_target-MEMCACHE**\"\n\nAll these technical features are consistent with github's public documents.\n\n![](__GHOST_URL__/content/images/2018/03/github.under.attack.png)\n\nNext, let’s take a look at the most recent 7 days of data on DDoSMon for some detailed breakdown.  \n\n#### The Targets\n\nIn just 7 days, our DDoSmon platform logged:\n\n - 10k attack events\n - 7131 unique victim IP addresses\n\nIn order to make the result more readable, we use our PDNS system to map the victim IPs back to their dns names. Within them, 981 (13%) have recently (within a week) resolvable domain names, and 15k (22%) have historically had domain names.\n\nFor all the targets above which have dns names, we checked Alexa top 1m domain list and our Float top 1m to generat two lists.(Float is our internal domain popular ranking system with a focus visits mainly in China.)\n\nHere is a snip for alexa(please bear in mind that we use the most recent PDNS to map the IPs, also we only keep the SLD, not the whole FQDN, so attack against a.com is mostly like attack against subdomains such as zyx.a.com, not necessary a.com itself.\n\n```\ntarget_ip\trank\tbelongs to sld\n59.37.97.93\t9\tqq.com\n182.254.79.46\t9\tqq.com\n36.110.213.82\t21\t360.cn\n216.18.168.16\t32\tpornhub.com\n192.30.255.113\t74\tgithub.com\n192.30.253.125\t74\tgithub.com\n192.30.253.113\t74\tgithub.com\n192.30.253.112\t74\tgithub.com\n151.101.128.84\t80\tpinterest.com\n104.155.208.139\t112\tgoogleusercontent.com\n```\n\nSnip for float\n\n```\ntarget_ip\trank\tfqdn\n115.239.211.112\t12\twww.a.shifen.com\n182.254.79.46\t21\tmp.weixin.qq.com\n59.37.97.93\t464\tpingma.qq.com\n114.80.223.177\t587\tinterface.hdslb.net\n47.91.19.168\t587\tinterface.hdslb.net\n222.186.35.81\t587\tinterface.hdslb.net\n114.80.223.172\t587\tinterface.hdslb.net\n140.205.32.8\t867\tsh.wagbridge.aliyun.com.gds.alibabadns.com\n114.80.223.177\t1052\tbilibili.hdslb.net\n47.91.19.168\t1052\tbilibili.hdslb.net\n```\n\nThese two lists can be downloaded [here](__GHOST_URL__/file/memcache.drdos.victim.in.alexa.top.1m.txt) and  [here](__GHOST_URL__/file/memcache.drdos.victim.in.float.top.1m.txt).\n\n\nTake a look at both lists, you will spot lots of interesting targets. For example:\n\n - **The regular big players** such as qq,360, google, amamzon.etc\n - **The game industry** such as rockstargames.com, minecraft.net, playstation.net\n - **The porn sites** such as pornhub.com, homepornbay.com\n - **The security industry** such Avast.com, kaspersky-labs.com, 360.cn\n - **The political** related websites such as nra.org, nrafoundation.org ,nracarryguard.com, epochtimes.com\n - And the guy who always gets to see the newest ddos attack: **krebsonsecurity.com** :)\n\n\n\nVictims' geo distribution:\n\n\n![](__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.victims.geo.distribution.7days-1.png)\n\nAnd asn distribution:\n\n![](__GHOST_URL__/content/images/2018/03/memcache.drdos.trend.victims.asn.distribution.7days-1.png)\n\nOverall, the current 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.\n\n\n#### Honeypot Data\n\nWe set up a honeypot for this type of attack and filtered out over 37k attack instructions.\n\nAs shown in the following table, 99% of the attack instructions are based on memcache STATS directives.\n\n![](__GHOST_URL__/content/images/2018/03/most.attacks.in.real.world.are.stats.command.png)\n\n"}]],"sections":[[10,0]],"ghostVersion":"3.0"}