Warning: Satori, a Mirai Branch Is Spreading in Worm Style on Port 37215 and 52869
<!--kg-card-begin: markdown--><p>Author: 360 netlab</p>
<pre><code>[Update History]
- At 2017-12-05 18:56:40 UTC, 2 hours after our blog goes live, we observed the C2 sending kill scan command to the bots, and that explains why the scan activities on the two ports started to drop on a global scale.

- The C2 address 95.211.123.69:7654 is the typo for 95.211.123.69:7645
</code></pre>
<p>In our last <a href="__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/">blog</a>, we mentioned there were almost 100k unique scanner IPs from Argentina scanning port 2323 and port 23, and we concluded it was a new mirai variant. For the last few days, the scanning behavior has gotten more intense, and more countries started to show up on our ScanMon platform as scan source. We have been able to dig more into this situation and see some bigger picture, and realized that the 2323|23 scan is only a piece of a big puzzler, while we are still doing more in-depth research into this matter, we bumped into a new situation today which we think needs some immediate attention from the security community, so here is a very brief and rough write-up.</p>
<p><strong>About 12 hours ago</strong> (2017-12-05 11:57 AM GMT+8), we noticed a new version of Satori (a mirai variant which we named Satori), starting to propagate very quickly on port 37215 and 52869. This new variant has two significant differences from known mirai variants:</p>
<ul>
<li>
<p>The bot itself now does NOT rely on loader|scanner mechanism to perform remote planting, instead, bot itself performs the scan activity. This worm like behavior is quite significant.</p>
</li>
<li>
<p>Two new exploits, which work on port 37215 and 52869 have been added, see below for more details. Due to the worm like behavior, we all should be on the lookout for the port 37215 and 52869 scan traffic. (For those who don’t have the visibility, feel free to check out our free Scanmon system for port <a href="http://scan.netlab.360.com/#/dashboard?tsbeg=1511884800000&amp;tsend=1512489600000&amp;dstport=37215&amp;toplistname=srcip&amp;topn=10&amp;sortby=sum">37215</a> and <a href="http://scan.netlab.360.com/#/dashboard?tsbeg=1511884800000&amp;tsend=1512489600000&amp;dstport=52869&amp;toplistname=srcip&amp;topn=10&amp;sortby=sum">52869</a>, or ISC port pages for <a href="https://isc.sans.edu/port.html?port=37215">37215</a> and <a href="https://isc.sans.edu/port.html?port=52869">52869</a>.</p>
</li>
</ul>
<p><strong>This malware is the newest version of Satori</strong>. We have been tracking Satori for months, and have strong evidence this new wave of attack can be linked to <a href="__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/">previous attack</a> on port 23 and 2323 scanning traffic upticks.</p>
<p>The scanning IP (aka, the bot) numbers are now climbing straight up. For example, during last recent 12 hours we have seen 263,250 different IPs scanning port 37215, and 19,403 IPs scanning port 52869.</p>
<p><img src="__GHOST_URL__/content/images/2017/12/11_sharp_increase_of_scanning_ip_on_port_52869_in_darknet-1.png" alt="" loading="lazy"></p>
<h5 id="themalwaresampleandthec2s">The Malware Sample and the C2s</h5>
<p>We have collected following samples from our honeypot.</p>
<pre><code>df9c48e8bc7e7371b4744a2ef8b83ddf	hxxp://95.211.123.69/b
a7922bce9bb0cf58f305d17ccbc78d98	hxxp://95.211.123.69/fahwrzadws/okiru.mipsel
37b7c9831334de97c762dff7a1ba7b3f	hxxp://95.211.123.69/fahwrzadws/okiru.arm7
e1411cc1726afe6fb8d09099c5fb2fa6	hxxp://95.211.123.69/fahwrzadws/okiru.x86
cd4de0ae80a6f11bca8bec7b590e5832	hxxp://95.211.123.69/fahwrzadws/okiru.x86
7de55e697cd7e136dbb82b0713a01710	hxxp://95.211.123.69/fahwrzadws/okiru.mips
797458f9cee3d50e8f651eabc6ba6031	hxxp://95.211.123.69/fahwrzadws/okiru.m68k
353d36ad621e350f6fce7a48e598662b	hxxp://95.211.123.69/fahwrzadws/okiru.arm
8db073743319c8fca5d4596a7a8f9931	hxxp://95.211.123.69/fahwrzadws/okiru.sparc
0a8efeb4cb15c5b599e0d4fb9faba37d	hxxp://95.211.123.69/fahwrzadws/okiru.powerpc
08d48000a47af6f173eba6bb16265670	hxxp://95.211.123.69/fahwrzadws/okiru.x86_64
e9038f7f9c957a4e1c6fc8489994add4	hxxp://95.211.123.69/fahwrzadws/okiru.superh
</code></pre>
<p>Satori borrows code from mirai with some major changes.</p>
<p>there are 3 C2s in the sample e1411cc1726afe6fb8d09099c5fb2fa6 we got,</p>
<ul>
<li>95.211.123.69:7645</li>
<li>network.bigbotpein.com:23</li>
<li>control.almashosting.ru</li>
</ul>
<p>Note: the only working c2 is <strong>95.211.123.69:7645</strong>, the other network.bigbotpein.com:23 and control.almashosting.ru is not actually being used here, they might be there just to trick security researcher to connect to the wrong C2s. (Note again, we also have old samples, as well as some fresh new samples coming in, in which control.almashosting.ru is really been used.)</p>
<h5 id="thescanningactivity">The Scanning Activity</h5>
<p>As can be seen from the following picture, the bot will scan port 37215 and 52869 randomly, determined by the remainder of a random integer mod 3.</p>
<p><img src="__GHOST_URL__/content/images/2017/12/12_scanning_activity_in_samples.png" alt="" loading="lazy"></p>
<h5 id="theexploits">The Exploits</h5>
<p>During the scanning, Satori will utilize two different exploits, one on port 37215, while the other on 52869.</p>
<ul>
<li>The one on port 37215 is not fully disclosed yet, our team has been tracking this in  the last few days and got quite some insight, but we will not discuss it here right now.(stay tuned for our update later).</li>
<li>The one on port 52869 is derived from <a href="https://www.exploit-db.com/exploits/37169/">CVE-2014-8361</a>.</li>
</ul>
<p>Not only are Satori penetrating with these exploits, but they also drive infected devices to download themselves from the same original download URL. This makes a loop, and causes Satori spreading in a <code>worm</code> manner.</p>
<h5 id="theconnectiontopreviousport23and2323scanningupticks">The Connection to Previous Port 23 and 2323 Scanning Upticks</h5>
<p>In our <a href="__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/">previous blog</a>, we have mentioned an upticks on port 23 and 2323 scanning traffic in Argentina.</p>
<p>Actually, in the next few days, more countries such as Egypt, Tunisia, Columbia have been picked up by our monitoring system, as we mentioned in the beginning of this blogpost, our investigation reveals the port scan is only part of the whole picture.</p>
<p>Right now we just want to point out that the 2323|23 attacks and today Satori’s attack shares some common factors, for example, the samples’ name and static features, some of the C2 protocols and sharing of the same exploits. These make we believe they two are connected.</p>
<p>We will share more details on our blog later on.</p>
<h5 id="ioc">IoC</h5>
<h6 id="samplesinthiswave">Samples in This Wave</h6>
<p>Satori is evolving as of our writing, we have capture some more samples with difference c2..etc, so here is only some of the IoCs.</p>
<pre><code>df9c48e8bc7e7371b4744a2ef8b83ddf	hxxp://95.211.123.69/b
a7922bce9bb0cf58f305d17ccbc78d98	hxxp://95.211.123.69/fahwrzadws/okiru.mipsel
37b7c9831334de97c762dff7a1ba7b3f	hxxp://95.211.123.69/fahwrzadws/okiru.arm7
e1411cc1726afe6fb8d09099c5fb2fa6	hxxp://95.211.123.69/fahwrzadws/okiru.x86
cd4de0ae80a6f11bca8bec7b590e5832	hxxp://95.211.123.69/fahwrzadws/okiru.x86
7de55e697cd7e136dbb82b0713a01710	hxxp://95.211.123.69/fahwrzadws/okiru.mips
797458f9cee3d50e8f651eabc6ba6031	hxxp://95.211.123.69/fahwrzadws/okiru.m68k
353d36ad621e350f6fce7a48e598662b	hxxp://95.211.123.69/fahwrzadws/okiru.arm
8db073743319c8fca5d4596a7a8f9931	hxxp://95.211.123.69/fahwrzadws/okiru.sparc
0a8efeb4cb15c5b599e0d4fb9faba37d	hxxp://95.211.123.69/fahwrzadws/okiru.powerpc
08d48000a47af6f173eba6bb16265670	hxxp://95.211.123.69/fahwrzadws/okiru.x86_64
e9038f7f9c957a4e1c6fc8489994add4	hxxp://95.211.123.69/fahwrzadws/okiru.superh

</code></pre>
<h6 id="someearliersamples">Some Earlier Samples</h6>
<pre><code>c63820d8aff3b18b3ee0eaee4e9d26b0	hxxp://172.93.97.219/okiru.mipsel
fd2bd0bf25fc306cc391bdcde1fcaeda	hxxp://172.93.97.219/okiru.arm
ba98c78a65ebf17615fee9a7ef34b405	hxxp://172.93.97.219/okiru.arm7
8a561bda915c89668e611b0ba72b0429	hxxp://172.93.97.219/okiru.m68k
f8130e86dc0fcdbcfa0d3b2425d3fcbf	hxxp://172.93.97.219/okiru.x86
7a38ee6ee15bd89d50161b3061b763ea	hxxp://172.93.97.219/okiru.mips
3f401fc6b8a5847376e4d070505bd9fe	hxxp://172.93.97.219/cryptonite.mips
a69692a2506f2127b23a8c35abe11427	hxxp://165.227.220.202/bins/mips
hxxp://198.7.59.177/fahwrzadws/okiru.mips
hxxp://198.7.59.177/cryptonite.mips
</code></pre>
<!--kg-card-end: markdown-->
Author: 360 netlab


[Update History]
- At 2017-12-05 18:56:40 UTC, 2 hours after our blog goes live, we observed the C2 sending kill scan command to the bots, and that explains why the scan activities on the two ports started to drop on a global scale.

- The C2 address 95.211.123.69:7654 is the typo for 95.211.123.69:7645



In our last blog, we mentioned there were almost 100k unique scanner IPs from Argentina scanning port 2323 and port 23, and we concluded it was a new mirai variant. For the last few days, the scanning behavior has gotten more intense, and more countries started to show up on our ScanMon platform as scan source. We have been able to dig more into this situation and see some bigger picture, and realized that the 2323|23 scan is only a piece of a big puzzler, while we are still doing more in-depth research into this matter, we bumped into a new situation today which we think needs some immediate attention from the security community, so here is a very brief and rough write-up.


About 12 hours ago (2017-12-05 11:57 AM GMT+8), we noticed a new version of Satori (a mirai variant which we named Satori), starting to propagate very quickly on port 37215 and 52869. This new variant has two significant differences from known mirai variants:


 * 
   
   
   The bot itself now does NOT rely on loader|scanner mechanism to perform remote planting, instead, bot itself performs the scan activity. This worm like behavior is quite significant.
   

 * 
   
   
   Two new exploits, which work on port 37215 and 52869 have been added, see below for more details. Due to the worm like behavior, we all should be on the lookout for the port 37215 and 52869 scan traffic. (For those who don’t have the visibility, feel free to check out our free Scanmon system for port 37215 and 52869, or ISC port pages for 37215 and 52869.
   


This malware is the newest version of Satori. We have been tracking Satori for months, and have strong evidence this new wave of attack can be linked to previous attack on port 23 and 2323 scanning traffic upticks.


The scanning IP (aka, the bot) numbers are now climbing straight up. For example, during last recent 12 hours we have seen 263,250 different IPs scanning port 37215, and 19,403 IPs scanning port 52869.





The Malware Sample and the C2s


We have collected following samples from our honeypot.


df9c48e8bc7e7371b4744a2ef8b83ddf	hxxp://95.211.123.69/b
a7922bce9bb0cf58f305d17ccbc78d98	hxxp://95.211.123.69/fahwrzadws/okiru.mipsel
37b7c9831334de97c762dff7a1ba7b3f	hxxp://95.211.123.69/fahwrzadws/okiru.arm7
e1411cc1726afe6fb8d09099c5fb2fa6	hxxp://95.211.123.69/fahwrzadws/okiru.x86
cd4de0ae80a6f11bca8bec7b590e5832	hxxp://95.211.123.69/fahwrzadws/okiru.x86
7de55e697cd7e136dbb82b0713a01710	hxxp://95.211.123.69/fahwrzadws/okiru.mips
797458f9cee3d50e8f651eabc6ba6031	hxxp://95.211.123.69/fahwrzadws/okiru.m68k
353d36ad621e350f6fce7a48e598662b	hxxp://95.211.123.69/fahwrzadws/okiru.arm
8db073743319c8fca5d4596a7a8f9931	hxxp://95.211.123.69/fahwrzadws/okiru.sparc
0a8efeb4cb15c5b599e0d4fb9faba37d	hxxp://95.211.123.69/fahwrzadws/okiru.powerpc
08d48000a47af6f173eba6bb16265670	hxxp://95.211.123.69/fahwrzadws/okiru.x86_64
e9038f7f9c957a4e1c6fc8489994add4	hxxp://95.211.123.69/fahwrzadws/okiru.superh



Satori borrows code from mirai with some major changes.


there are 3 C2s in the sample e1411cc1726afe6fb8d09099c5fb2fa6 we got,


 * 95.211.123.69:7645
 * network.bigbotpein.com:23
 * control.almashosting.ru


Note: the only working c2 is 95.211.123.69:7645, the other network.bigbotpein.com:23 and control.almashosting.ru is not actually being used here, they might be there just to trick security researcher to connect to the wrong C2s. (Note again, we also have old samples, as well as some fresh new samples coming in, in which control.almashosting.ru is really been used.)


The Scanning Activity


As can be seen from the following picture, the bot will scan port 37215 and 52869 randomly, determined by the remainder of a random integer mod 3.





The Exploits


During the scanning, Satori will utilize two different exploits, one on port 37215, while the other on 52869.


 * The one on port 37215 is not fully disclosed yet, our team has been tracking this in the last few days and got quite some insight, but we will not discuss it here right now.(stay tuned for our update later).
 * The one on port 52869 is derived from CVE-2014-8361.


Not only are Satori penetrating with these exploits, but they also drive infected devices to download themselves from the same original download URL. This makes a loop, and causes Satori spreading in a worm manner.


The Connection to Previous Port 23 and 2323 Scanning Upticks


In our previous blog, we have mentioned an upticks on port 23 and 2323 scanning traffic in Argentina.


Actually, in the next few days, more countries such as Egypt, Tunisia, Columbia have been picked up by our monitoring system, as we mentioned in the beginning of this blogpost, our investigation reveals the port scan is only part of the whole picture.


Right now we just want to point out that the 2323|23 attacks and today Satori’s attack shares some common factors, for example, the samples’ name and static features, some of the C2 protocols and sharing of the same exploits. These make we believe they two are connected.


We will share more details on our blog later on.


IoC


Samples in This Wave


Satori is evolving as of our writing, we have capture some more samples with difference c2..etc, so here is only some of the IoCs.


df9c48e8bc7e7371b4744a2ef8b83ddf	hxxp://95.211.123.69/b
a7922bce9bb0cf58f305d17ccbc78d98	hxxp://95.211.123.69/fahwrzadws/okiru.mipsel
37b7c9831334de97c762dff7a1ba7b3f	hxxp://95.211.123.69/fahwrzadws/okiru.arm7
e1411cc1726afe6fb8d09099c5fb2fa6	hxxp://95.211.123.69/fahwrzadws/okiru.x86
cd4de0ae80a6f11bca8bec7b590e5832	hxxp://95.211.123.69/fahwrzadws/okiru.x86
7de55e697cd7e136dbb82b0713a01710	hxxp://95.211.123.69/fahwrzadws/okiru.mips
797458f9cee3d50e8f651eabc6ba6031	hxxp://95.211.123.69/fahwrzadws/okiru.m68k
353d36ad621e350f6fce7a48e598662b	hxxp://95.211.123.69/fahwrzadws/okiru.arm
8db073743319c8fca5d4596a7a8f9931	hxxp://95.211.123.69/fahwrzadws/okiru.sparc
0a8efeb4cb15c5b599e0d4fb9faba37d	hxxp://95.211.123.69/fahwrzadws/okiru.powerpc
08d48000a47af6f173eba6bb16265670	hxxp://95.211.123.69/fahwrzadws/okiru.x86_64
e9038f7f9c957a4e1c6fc8489994add4	hxxp://95.211.123.69/fahwrzadws/okiru.superh




Some Earlier Samples


c63820d8aff3b18b3ee0eaee4e9d26b0	hxxp://172.93.97.219/okiru.mipsel
fd2bd0bf25fc306cc391bdcde1fcaeda	hxxp://172.93.97.219/okiru.arm
ba98c78a65ebf17615fee9a7ef34b405	hxxp://172.93.97.219/okiru.arm7
8a561bda915c89668e611b0ba72b0429	hxxp://172.93.97.219/okiru.m68k
f8130e86dc0fcdbcfa0d3b2425d3fcbf	hxxp://172.93.97.219/okiru.x86
7a38ee6ee15bd89d50161b3061b763ea	hxxp://172.93.97.219/okiru.mips
3f401fc6b8a5847376e4d070505bd9fe	hxxp://172.93.97.219/cryptonite.mips
a69692a2506f2127b23a8c35abe11427	hxxp://165.227.220.202/bins/mips
hxxp://198.7.59.177/fahwrzadws/okiru.mips
hxxp://198.7.59.177/cryptonite.mips


{"version":"0.3.1","markups":[],"atoms":[],"cards":[["markdown",{"cardName":"card-markdown","markdown":"Author: 360 netlab\n\n```\n[Update History]\n- At 2017-12-05 18:56:40 UTC, 2 hours after our blog goes live, we observed the C2 sending kill scan command to the bots, and that explains why the scan activities on the two ports started to drop on a global scale.\n\n- The C2 address 95.211.123.69:7654 is the typo for 95.211.123.69:7645\n```\n\nIn our last [blog](__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/), we mentioned there were almost 100k unique scanner IPs from Argentina scanning port 2323 and port 23, and we concluded it was a new mirai variant. For the last few days, the scanning behavior has gotten more intense, and more countries started to show up on our ScanMon platform as scan source. We have been able to dig more into this situation and see some bigger picture, and realized that the 2323|23 scan is only a piece of a big puzzler, while we are still doing more in-depth research into this matter, we bumped into a new situation today which we think needs some immediate attention from the security community, so here is a very brief and rough write-up.\n\n**About 12 hours ago** (2017-12-05 11:57 AM GMT+8), we noticed a new version of Satori (a mirai variant which we named Satori), starting to propagate very quickly on port 37215 and 52869. This new variant has two significant differences from known mirai variants:\n\n - The bot itself now does NOT rely on loader|scanner mechanism to perform remote planting, instead, bot itself performs the scan activity. This worm like behavior is quite significant.\n\n - Two new exploits, which work on port 37215 and 52869 have been added, see below for more details. Due to the worm like behavior, we all should be on the lookout for the port 37215 and 52869 scan traffic. (For those who don’t have the visibility, feel free to check out our free Scanmon system for port [37215](http://scan.netlab.360.com/#/dashboard?tsbeg=1511884800000&tsend=1512489600000&dstport=37215&toplistname=srcip&topn=10&sortby=sum) and [52869](http://scan.netlab.360.com/#/dashboard?tsbeg=1511884800000&tsend=1512489600000&dstport=52869&toplistname=srcip&topn=10&sortby=sum), or ISC port pages for [37215](https://isc.sans.edu/port.html?port=37215) and [52869](https://isc.sans.edu/port.html?port=52869).\n\n**This malware is the newest version of Satori**. We have been tracking Satori for months, and have strong evidence this new wave of attack can be linked to [previous attack](__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/) on port 23 and 2323 scanning traffic upticks.\n\nThe scanning IP (aka, the bot) numbers are now climbing straight up. For example, during last recent 12 hours we have seen 263,250 different IPs scanning port 37215, and 19,403 IPs scanning port 52869.\n\n![](__GHOST_URL__/content/images/2017/12/11_sharp_increase_of_scanning_ip_on_port_52869_in_darknet-1.png)\n\n\n#####The Malware Sample and the C2s\nWe have collected following samples from our honeypot.\n\n```\ndf9c48e8bc7e7371b4744a2ef8b83ddf\thxxp://95.211.123.69/b\na7922bce9bb0cf58f305d17ccbc78d98\thxxp://95.211.123.69/fahwrzadws/okiru.mipsel\n37b7c9831334de97c762dff7a1ba7b3f\thxxp://95.211.123.69/fahwrzadws/okiru.arm7\ne1411cc1726afe6fb8d09099c5fb2fa6\thxxp://95.211.123.69/fahwrzadws/okiru.x86\ncd4de0ae80a6f11bca8bec7b590e5832\thxxp://95.211.123.69/fahwrzadws/okiru.x86\n7de55e697cd7e136dbb82b0713a01710\thxxp://95.211.123.69/fahwrzadws/okiru.mips\n797458f9cee3d50e8f651eabc6ba6031\thxxp://95.211.123.69/fahwrzadws/okiru.m68k\n353d36ad621e350f6fce7a48e598662b\thxxp://95.211.123.69/fahwrzadws/okiru.arm\n8db073743319c8fca5d4596a7a8f9931\thxxp://95.211.123.69/fahwrzadws/okiru.sparc\n0a8efeb4cb15c5b599e0d4fb9faba37d\thxxp://95.211.123.69/fahwrzadws/okiru.powerpc\n08d48000a47af6f173eba6bb16265670\thxxp://95.211.123.69/fahwrzadws/okiru.x86_64\ne9038f7f9c957a4e1c6fc8489994add4\thxxp://95.211.123.69/fahwrzadws/okiru.superh\n```\nSatori borrows code from mirai with some major changes. \n\n\nthere are 3 C2s in the sample e1411cc1726afe6fb8d09099c5fb2fa6 we got,\n\n - 95.211.123.69:7645\n - network.bigbotpein.com:23\n - control.almashosting.ru\n\nNote: the only working c2 is **95.211.123.69:7645**, the other network.bigbotpein.com:23 and control.almashosting.ru is not actually being used here, they might be there just to trick security researcher to connect to the wrong C2s. (Note again, we also have old samples, as well as some fresh new samples coming in, in which control.almashosting.ru is really been used.)\n\n#####The Scanning Activity\n\nAs can be seen from the following picture, the bot will scan port 37215 and 52869 randomly, determined by the remainder of a random integer mod 3.\n\n![](__GHOST_URL__/content/images/2017/12/12_scanning_activity_in_samples.png)\n\n#####The Exploits\nDuring the scanning, Satori will utilize two different exploits, one on port 37215, while the other on 52869.\n\n - The one on port 37215 is not fully disclosed yet, our team has been tracking this in  the last few days and got quite some insight, but we will not discuss it here right now.(stay tuned for our update later). \n - The one on port 52869 is derived from [CVE-2014-8361](https://www.exploit-db.com/exploits/37169/).\n\nNot only are Satori penetrating with these exploits, but they also drive infected devices to download themselves from the same original download URL. This makes a loop, and causes Satori spreading in a `worm` manner.\n\n\n#####The Connection to Previous Port 23 and 2323 Scanning Upticks\nIn our [previous blog](__GHOST_URL__/early-warning-a-new-mirai-variant-is-spreading-quickly-on-port-23-and-2323-en/), we have mentioned an upticks on port 23 and 2323 scanning traffic in Argentina. \n\nActually, in the next few days, more countries such as Egypt, Tunisia, Columbia have been picked up by our monitoring system, as we mentioned in the beginning of this blogpost, our investigation reveals the port scan is only part of the whole picture.\n\nRight now we just want to point out that the 2323|23 attacks and today Satori’s attack shares some common factors, for example, the samples’ name and static features, some of the C2 protocols and sharing of the same exploits. These make we believe they two are connected.\n\nWe will share more details on our blog later on.\n\n\n#####IoC\n\n######Samples in This Wave\nSatori is evolving as of our writing, we have capture some more samples with difference c2..etc, so here is only some of the IoCs.\n```\ndf9c48e8bc7e7371b4744a2ef8b83ddf\thxxp://95.211.123.69/b\na7922bce9bb0cf58f305d17ccbc78d98\thxxp://95.211.123.69/fahwrzadws/okiru.mipsel\n37b7c9831334de97c762dff7a1ba7b3f\thxxp://95.211.123.69/fahwrzadws/okiru.arm7\ne1411cc1726afe6fb8d09099c5fb2fa6\thxxp://95.211.123.69/fahwrzadws/okiru.x86\ncd4de0ae80a6f11bca8bec7b590e5832\thxxp://95.211.123.69/fahwrzadws/okiru.x86\n7de55e697cd7e136dbb82b0713a01710\thxxp://95.211.123.69/fahwrzadws/okiru.mips\n797458f9cee3d50e8f651eabc6ba6031\thxxp://95.211.123.69/fahwrzadws/okiru.m68k\n353d36ad621e350f6fce7a48e598662b\thxxp://95.211.123.69/fahwrzadws/okiru.arm\n8db073743319c8fca5d4596a7a8f9931\thxxp://95.211.123.69/fahwrzadws/okiru.sparc\n0a8efeb4cb15c5b599e0d4fb9faba37d\thxxp://95.211.123.69/fahwrzadws/okiru.powerpc\n08d48000a47af6f173eba6bb16265670\thxxp://95.211.123.69/fahwrzadws/okiru.x86_64\ne9038f7f9c957a4e1c6fc8489994add4\thxxp://95.211.123.69/fahwrzadws/okiru.superh\n\n```\n\n######Some Earlier Samples\n```\nc63820d8aff3b18b3ee0eaee4e9d26b0\thxxp://172.93.97.219/okiru.mipsel\nfd2bd0bf25fc306cc391bdcde1fcaeda\thxxp://172.93.97.219/okiru.arm\nba98c78a65ebf17615fee9a7ef34b405\thxxp://172.93.97.219/okiru.arm7\n8a561bda915c89668e611b0ba72b0429\thxxp://172.93.97.219/okiru.m68k\nf8130e86dc0fcdbcfa0d3b2425d3fcbf\thxxp://172.93.97.219/okiru.x86\n7a38ee6ee15bd89d50161b3061b763ea\thxxp://172.93.97.219/okiru.mips\n3f401fc6b8a5847376e4d070505bd9fe\thxxp://172.93.97.219/cryptonite.mips\na69692a2506f2127b23a8c35abe11427\thxxp://165.227.220.202/bins/mips\nhxxp://198.7.59.177/fahwrzadws/okiru.mips\nhxxp://198.7.59.177/cryptonite.mips\n```"}]],"sections":[[10,0]],"ghostVersion":"3.0"}