Early Warning: ADB.Miner A Mining Botnet Utilizing Android ADB Is Now Rapidly Spreading
<!--kg-card-begin: markdown--><p>Author：Hui Wang, RootKiter,<br>
<a href="https://twitter.com/360Netlab">twitter/360Netlab</a></p>
<p>About 24 hours ago, around 2018-02-03 15:00(GMT +8), a set of malicious code began to spread rapidly, here are some quick facts:</p>
<ul>
<li><strong>Timeline</strong> : the earliest time of the infection can be traced back to January 31. And the current worm-like infection was detected by our system from around 2018-02-03 15:00</li>
<li><strong>Infected port</strong> : 5555, which is the working port of adb debugging interface on Android device, this port should be normally closed</li>
<li><strong>Worm behavior</strong> : The Malicious code looks for open 5555 adb debug interface after successful infection, which is worm like.</li>
<li><strong>Target equipment</strong> : Most are android based devices. We will not publish details as of now.</li>
<li><strong>The number of infected equipment</strong> : 2.75 ~ 5k, so far mainly in China (~ 40%) and South Korea (~ 30%)</li>
</ul>
<p>Also, this malware borrows some of the mirai's scanning code, this is the first time we see the mirai code being used by Android bot</p>
<p>Overall, we think there is a new and active worm targeting android system's adb debug interface spreading, and this worm has probably infected more than 5,000 devices in just 24 hours.</p>
<h4 id="infectiontrendonport5555">Infection Trend on Port 5555</h4>
<p><img src="__GHOST_URL__/content/images/2018/02/5555_scanning_trend.png" alt="" loading="lazy"></p>
<p>As can be seen from the figure above, the scan traffic on port 5555 starts around 15:00 pm on 2018-02-03 , reaches 3 times the daily average number, and has a tenfold increase around 24:00. the number of IPs initiating scanning and the total scanning traffic are still growing as of now.</p>
<p>As it can be seen below, the current 5555 port scan traffic has been gone up to the top ten of all ports on our <a href="http://scan.netlab.360.com">scanmon</a> system. The last time we saw a new port suddenly jumped to the top 10 list was the mirai botnet, which goes back to September 2016.</p>
<p><img src="__GHOST_URL__/content/images/2018/02/scanned_port_top10.png" alt="" loading="lazy"></p>
<p>The number of unique scan sources is 2.75k on our scanmon system, and 5.5k on our botnet tracking system.</p>
<p><img src="__GHOST_URL__/content/images/2018/02/scanner_are_from_China_and_Korea.png" alt="" loading="lazy"><br>
<img src="__GHOST_URL__/content/images/2018/02/scanner_from_botnetmon.png" alt="" loading="lazy"></p>
<h4 id="mostoftheinfecteddevicesareandroidsmartphonesortvboxwithadbdebugginginterfaceopened">Most of the Infected devices Are Android Smart Phones or TV Box with ADB Debugging Interface Opened</h4>
<p>Those infected devices are actively trying to spread malicious code. By analyzing the spreading source, we found that most of them are smart phones and smart TV (TV box) based on Android.</p>
<p>We will not publish detailed infected models here. Till now, we don't think it is a vendor level issue.</p>
<h4 id="infecteddevicesareusedtodigxmrcoins">Infected Devices are Used to Dig XMR Coins</h4>
<p>A set of malicious code are located till now. Among them, the xmrig related ones are involved in digging XMR tokens, with two groups of configurations.</p>
<p>These two share the same wallet address but with different mining pool address:</p>
<ul>
<li><strong>Mining Pool</strong> : pool.monero.hashvault.pro:5555 or pool.minexmr.com:7777</li>
<li><strong>Wallet Address</strong> : 44XT4KvmobTQfeWa6PCQF5RDosr2MLWm43AsaE3o5iNRXXTfDbYk2VPHTVedTQHZyfXNzMn8YYF2466d3FSDT7gJS8gdHAr</li>
<li><strong>Pool Pass</strong> : x</li>
</ul>
<p>Till now, zero coins have been paid, as can be seen in below:</p>
<p><img src="__GHOST_URL__/content/images/2018/02/zero_incoming_till_now.png" alt="" loading="lazy"></p>
<p>We will post any important update here to further illustrate this, stay tuned.</p>
<!--kg-card-end: markdown-->
Author：Hui Wang, RootKiter,

twitter/360Netlab


About 24 hours ago, around 2018-02-03 15:00(GMT +8), a set of malicious code began to spread rapidly, here are some quick facts:


 * Timeline : the earliest time of the infection can be traced back to January 31. And the current worm-like infection was detected by our system from around 2018-02-03 15:00
 * Infected port : 5555, which is the working port of adb debugging interface on Android device, this port should be normally closed
 * Worm behavior : The Malicious code looks for open 5555 adb debug interface after successful infection, which is worm like.
 * Target equipment : Most are android based devices. We will not publish details as of now.
 * The number of infected equipment : 2.75 ~ 5k, so far mainly in China (~ 40%) and South Korea (~ 30%)


Also, this malware borrows some of the mirai's scanning code, this is the first time we see the mirai code being used by Android bot


Overall, we think there is a new and active worm targeting android system's adb debug interface spreading, and this worm has probably infected more than 5,000 devices in just 24 hours.


Infection Trend on Port 5555





As can be seen from the figure above, the scan traffic on port 5555 starts around 15:00 pm on 2018-02-03 , reaches 3 times the daily average number, and has a tenfold increase around 24:00. the number of IPs initiating scanning and the total scanning traffic are still growing as of now.


As it can be seen below, the current 5555 port scan traffic has been gone up to the top ten of all ports on our scanmon system. The last time we saw a new port suddenly jumped to the top 10 list was the mirai botnet, which goes back to September 2016.





The number of unique scan sources is 2.75k on our scanmon system, and 5.5k on our botnet tracking system.







Most of the Infected devices Are Android Smart Phones or TV Box with ADB Debugging Interface Opened


Those infected devices are actively trying to spread malicious code. By analyzing the spreading source, we found that most of them are smart phones and smart TV (TV box) based on Android.


We will not publish detailed infected models here. Till now, we don't think it is a vendor level issue.


Infected Devices are Used to Dig XMR Coins


A set of malicious code are located till now. Among them, the xmrig related ones are involved in digging XMR tokens, with two groups of configurations.


These two share the same wallet address but with different mining pool address:


 * Mining Pool : pool.monero.hashvault.pro:5555 or pool.minexmr.com:7777
 * Wallet Address : 44XT4KvmobTQfeWa6PCQF5RDosr2MLWm43AsaE3o5iNRXXTfDbYk2VPHTVedTQHZyfXNzMn8YYF2466d3FSDT7gJS8gdHAr
 * Pool Pass : x


Till now, zero coins have been paid, as can be seen in below:





We will post any important update here to further illustrate this, stay tuned.

{"version":"0.3.1","markups":[],"atoms":[],"cards":[["markdown",{"cardName":"card-markdown","markdown":"Author：Hui Wang, RootKiter,\n[twitter/360Netlab](https://twitter.com/360Netlab)\n\nAbout 24 hours ago, around 2018-02-03 15:00(GMT +8), a set of malicious code began to spread rapidly, here are some quick facts:\n\n\n - **Timeline** : the earliest time of the infection can be traced back to January 31. And the current worm-like infection was detected by our system from around 2018-02-03 15:00\n - **Infected port** : 5555, which is the working port of adb debugging interface on Android device, this port should be normally closed\n - **Worm behavior** : The Malicious code looks for open 5555 adb debug interface after successful infection, which is worm like.\n - **Target equipment** : Most are android based devices. We will not publish details as of now.\n - **The number of infected equipment** : 2.75 ~ 5k, so far mainly in China (~ 40%) and South Korea (~ 30%)\n\nAlso, this malware borrows some of the mirai's scanning code, this is the first time we see the mirai code being used by Android bot\n\nOverall, we think there is a new and active worm targeting android system's adb debug interface spreading, and this worm has probably infected more than 5,000 devices in just 24 hours.\n\n#### Infection Trend on Port 5555\n\n![](__GHOST_URL__/content/images/2018/02/5555_scanning_trend.png)\n\nAs can be seen from the figure above, the scan traffic on port 5555 starts around 15:00 pm on 2018-02-03 , reaches 3 times the daily average number, and has a tenfold increase around 24:00. the number of IPs initiating scanning and the total scanning traffic are still growing as of now.\n\nAs it can be seen below, the current 5555 port scan traffic has been gone up to the top ten of all ports on our [scanmon](http://scan.netlab.360.com) system. The last time we saw a new port suddenly jumped to the top 10 list was the mirai botnet, which goes back to September 2016.\n\n![](__GHOST_URL__/content/images/2018/02/scanned_port_top10.png)\n\nThe number of unique scan sources is 2.75k on our scanmon system, and 5.5k on our botnet tracking system.\n\n\n![](__GHOST_URL__/content/images/2018/02/scanner_are_from_China_and_Korea.png)\n![](__GHOST_URL__/content/images/2018/02/scanner_from_botnetmon.png)\n\n#### Most of the Infected devices Are Android Smart Phones or TV Box with ADB Debugging Interface Opened\n\nThose infected devices are actively trying to spread malicious code. By analyzing the spreading source, we found that most of them are smart phones and smart TV (TV box) based on Android.\n\nWe will not publish detailed infected models here. Till now, we don't think it is a vendor level issue.\n\n#### Infected Devices are Used to Dig XMR Coins\n\nA set of malicious code are located till now. Among them, the xmrig related ones are involved in digging XMR tokens, with two groups of configurations.\n\nThese two share the same wallet address but with different mining pool address:\n\n -  **Mining Pool** : pool.monero.hashvault.pro:5555 or pool.minexmr.com:7777\n -  **Wallet Address** : 44XT4KvmobTQfeWa6PCQF5RDosr2MLWm43AsaE3o5iNRXXTfDbYk2VPHTVedTQHZyfXNzMn8YYF2466d3FSDT7gJS8gdHAr\n -  **Pool Pass** : x\n\nTill now, zero coins have been paid, as can be seen in below:\n\n![](__GHOST_URL__/content/images/2018/02/zero_incoming_till_now.png)\n\n\nWe will post any important update here to further illustrate this, stay tuned.\n\n"}]],"sections":[[10,0]],"ghostVersion":"3.0"}