Fbot is now riding the traffic and transportation smart devices
<!--kg-card-begin: markdown--><h3 id="background">Background</h3>
<p>Fbot, a botnet based on Mirai, has been very active ever sine we first blogged about it here<a href="__GHOST_URL__/threat-alert-a-new-worm-fbot-cleaning-adbminer-is-using-a-blockchain-based-dns-en/">[1]</a><a href="__GHOST_URL__/the-new-developments-of-the-fbot-en/">[2]</a>, we have seen this botnet using multiple 0 days before(some of them we have not disclosed yet) and it has been targeting various IoT devices, now, it is aiming a new category, traffic and transportation smart devices.</p>
<p>On February 20, 2021, the 360Netlab Threat Detection System captured attackers were using a remote command execution vulnerability (CVE-2020-9020)<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9023">[3]</a><a href="https://sku11army.blogspot.com/2020/01/iteris-vantage-velocity-field-unit-no.html">[4]</a> in the Vantage Velocity product from Iteris to spread Fbot botnet samples.</p>
<p>According to Wikipedia<a href="https://en.wikipedia.org/wiki/Iteris">[5]</a>, Iteris, Inc. provides intelligent mobile infrastructure management services and produces sensors and other devices that record and predict traffic conditions.</p>
<p>Based on the AIrLink GX450 Mobile Gateway production information found on the affected devices, we speculate that the affected devices are roadside monitoring device.</p>
<h3 id="cve20209020vulnerabilityanalysis">CVE-2020-9020 Vulnerability Analysis</h3>
<p>Through the 360 FirmwareTotal system, we verified and analyzed the CVE-2020-9020 vulnerability, here is the brief.</p>
<ol>
<li>
<p>Vantage Velocity product synchronizes With NTP Server, where user can set the specified ntp server address.</p>
</li>
<li>
<p>The <code>timeconfig.py</code> script does not filter the <code>htmlNtpServer</code> variable after accepting a user Web request, i.e., it is spliced into the shell variable format <code>&quot;ntpserver=&quot; + form[&quot;htmlNtpServer&quot;].value.strip()</code> and written to the <code>/root/timeparam</code> file.</p>
</li>
<li>
<p>The command execution vulnerability is triggered when the <code>timeconfig.py</code> script calls the shell script <code>/root/ntpconfig</code>, which reads the <code>/root/timeparam</code> file to initialize the variable ntpserver.</p>
</li>
</ol>
<h3 id="vulnerabilityimpactscope">Vulnerability impact scope</h3>
<p>The 360 Quake cyberspace mapping system found the specific distribution of Vantage Velocity devices by mapping assets across the network as shown in the figure below.<br>
<a href="__GHOST_URL__/content/images/2021/03/CVE_2020_9020_stats_en.png"><img src="__GHOST_URL__/content/images/2021/03/CVE_2020_9020_stats_en.png" class="kg-image"/></a></p>
<h3 id="fbotbotnet">Fbot botnet</h3>
<p>Fbot is a botnet based on Mirai, with 2 main changes</p>
<ul>
<li>Encryption algorithm</li>
<li>Registration packets, heartbeat packets</li>
</ul>
<p>The basic information of this sample is shown below:</p>
<blockquote>
<p>MD5:deaee7ada44bf1c6af826d2d170c8698</p>
<p>ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped</p>
<p>Packer:None</p>
</blockquote>
<p>It has no added features in itself, the main function is</p>
<ul>
<li>DDoS attack</li>
<li>Telnet scanning</li>
</ul>
<p>The following section will briefly analyze around the above functions.</p>
<h3 id="ddosattack">DDoS attack</h3>
<p>First Fbot establishes a connection with the hardcoded C2 (198.23.238.203:5684) via the following code snippet.</p>
<p><a href="__GHOST_URL__/content/images/2021/02/velo_fbot_c2.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_c2.png" class="kg-image"/></a></p>
<p>Then it sends a 78-byte long registration message to C2<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_reg-1.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_reg-1.png" class="kg-image"/></a></p>
<p>The network traffic generated in practice is shown below.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_regpkg.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_regpkg.png" class="kg-image"/></a></p>
<p>The information in the registration packet is used to verify the legal identity of the BOT, and the format of the registration packet is parsed as shown below.</p>
<pre><code>Main field parsing，others can be 0
——————————————————————————————————————————
02    ---&gt;type，register package
00 42 00 33 00 63  01 c8 02 fc 00 49   ---&gt;hardcoded，authentication
00 07   ---&gt;length of group string
75 6e 6b 6e 6f 77 6e ----&gt;group string，&quot;unknown&quot;
——————————————————————————————————————————
</code></pre>
<p>After sending the registration packet the Bot starts to wait for C2 to issue commands, the first byte of the command packet specifies the command type.</p>
<h4 id="0x00heartbeatcommandcode">0x00， heartbeat command code</h4>
<p>Take the following heartbeat as an example<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_beat.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_beat.png" class="kg-image"/></a></p>
<p>The format of the heartbeat packet is parsed as follows</p>
<pre><code>Main field parsing，others can be 0
——————————————————————————————————————————
00  ---&gt;type，heartbeat package
1b 37 03 f3 25 e3  19 40 1e 68 1a d2   ---&gt;hardcoded
——————————————————————————————————————————
</code></pre>
<h4 id="0x01ddosattackcommandcode">0x01，DDoS attack command code</h4>
<p>Take the following attack instruction as an example<br>
<a href="__GHOST_URL__/content/images/2021/02/ping_fbot_atk.png"><img src="__GHOST_URL__/content/images/2021/02/ping_fbot_atk.png" class="kg-image"/></a></p>
<p>The format of the attack packet is parsed as follows</p>
<pre><code>Main field parsing，others can be 0
——————————————————————————————————————————
01 　						---&gt;type，attack package 
01							---&gt;attack type
00 3c 						---&gt;time (sec)
01							---&gt;number of target
67 5f dd bc 00 20			---&gt;target/mask,103.95.221.188/32
02							---&gt;number of flag
	02							---&gt;flag type, attack package length
	00 04						---&gt;flag length
	31 34 36 30					---&gt;flag data，1460
	
	
	01							---&gt;flag type, port
	00 02						---&gt;flag length
	35 33						---&gt;flag data，53
——————————————————————————————————————————
</code></pre>
<h4 id="0x03exit">0x03，exit</h4>
<p><a href="__GHOST_URL__/content/images/2021/02/velo_fbot_exit.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_exit.png" class="kg-image"/></a></p>
<h3 id="telnetscanpropagation">Telnet scan &amp; propagation</h3>
<p>Fbot uses the technique of SYN port detection in the propagation process to improve the efficiency of propagation.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_scan.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_scan.png" class="kg-image"/></a></p>
<p>From the above code snippet, it can be seen that its scanning traffic has 2 characteristics</p>
<ol>
<li>The number of scanned 23 ports is about twice as many as 26 ports</li>
<li>The sequence number in the tcp header is equal to the target address in the ip header</li>
</ol>
<p>When a port is detected as open, login is attempted using a hard-coded credential list. Once successful, the IP, port, account, password, etc. are sent back to Reporter (198.23.238.203:774) via the following code snippet.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_report.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_report.png" class="kg-image"/></a></p>
<p>The actual network traffic generated is shown in the following figure.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_reportpkg.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_reportpkg.png" class="kg-image"/></a></p>
<p>Finally, the Fbot sample is implanted to the device either with network download(see below) or ECHO, and the successful implantation information is sent back to Reporter.</p>
<h4 id="1networkdownload">1：Network download</h4>
<p>If the device has wget or tftp, the Fbot sample of the corresponding CPU architecture on the device will be downloaded.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_dow_method.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_dow_method.png" class="kg-image"/></a></p>
<h4 id="2echo">2：ECHO</h4>
<p>If the device does not have a network download tool, the Fbot downloader of the corresponding CPU architecture is uploaded to the device via ECHO to download the Fbot samples.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_echo_method.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_echo_method.png" class="kg-image"/></a></p>
<p>The information of the Fbot downloader built into the sample is shown as follows.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_emelf.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_emelf.png" class="kg-image"/></a></p>
<p>In the above figure, the downloader with file offset 0x1D794 is used as an example.</p>
<blockquote>
<p>MD5:9b49507d1876c3a550f7b7a6e4ec696d</p>
<p>ELF 32-bit LSB executable, ARM, version 1 (ARM), statically linked, stripped</p>
<p>Packer:None</p>
</blockquote>
<p>Its function is to request the Fbot sample from the download server (198.23.238.203:80) and execute it.<br>
<a href="__GHOST_URL__/content/images/2021/02/velo_fbot_loader-1.png"><img src="__GHOST_URL__/content/images/2021/02/velo_fbot_loader-1.png" class="kg-image"/></a></p>
<h3 id="suggestions">Suggestions</h3>
<p>We recommend Vantage Velocity users to check and update the firmware system in a timely manner.</p>
<p>We recommend that Vantage Velocity users set complex login passwords for management interfaces such as Web and SSH.</p>
<p>We recommend that readers monitor and block relevant IPs and URLs mentioned in this blog.</p>
<h3 id="contactus">Contact us</h3>
<p>Readers are always welcomed to reach us on <a href="https://twitter.com/360Netlab"><strong>twitter</strong></a>, or email to netlab at 360<br>
dot cn.</p>
<h3 id="ioc">IoC</h3>
<p>IP:</p>
<pre><code>198.23.238.203      	United States       	ASN36352            	AS-COLOCROSSING
</code></pre>
<p>C2:</p>
<pre><code>198.23.238.203:5684
</code></pre>
<p>URL:</p>
<pre><code>http://198.23.238.203/arm7
</code></pre>
<p>MD5:</p>
<pre><code>deaee7ada44bf1c6af826d2d170c8698
</code></pre>
<!--kg-card-end: markdown-->
Background


Fbot, a botnet based on Mirai, has been very active ever sine we first blogged about it here[1][2], we have seen this botnet using multiple 0 days before(some of them we have not disclosed yet) and it has been targeting various IoT devices, now, it is aiming a new category, traffic and transportation smart devices.


On February 20, 2021, the 360Netlab Threat Detection System captured attackers were using a remote command execution vulnerability (CVE-2020-9020)[3][4] in the Vantage Velocity product from Iteris to spread Fbot botnet samples.


According to Wikipedia[5], Iteris, Inc. provides intelligent mobile infrastructure management services and produces sensors and other devices that record and predict traffic conditions.


Based on the AIrLink GX450 Mobile Gateway production information found on the affected devices, we speculate that the affected devices are roadside monitoring device.



CVE-2020-9020 Vulnerability Analysis


Through the 360 FirmwareTotal system, we verified and analyzed the CVE-2020-9020 vulnerability, here is the brief.


 1. 
    
    
    Vantage Velocity product synchronizes With NTP Server, where user can set the specified ntp server address.
    

 2. 
    
    
    The timeconfig.py script does not filter the htmlNtpServer variable after accepting a user Web request, i.e., it is spliced into the shell variable format "ntpserver=" + form["htmlNtpServer"].value.strip() and written to the /root/timeparam file.
    

 3. 
    
    
    The command execution vulnerability is triggered when the timeconfig.py script calls the shell script /root/ntpconfig, which reads the /root/timeparam file to initialize the variable ntpserver.
    



Vulnerability impact scope


The 360 Quake cyberspace mapping system found the specific distribution of Vantage Velocity devices by mapping assets across the network as shown in the figure below.





Fbot botnet


Fbot is a botnet based on Mirai, with 2 main changes


 * Encryption algorithm
 * Registration packets, heartbeat packets


The basic information of this sample is shown below:





MD5:deaee7ada44bf1c6af826d2d170c8698


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


Packer:None



It has no added features in itself, the main function is


 * DDoS attack
 * Telnet scanning


The following section will briefly analyze around the above functions.



DDoS attack


First Fbot establishes a connection with the hardcoded C2 (198.23.238.203:5684) via the following code snippet.





Then it sends a 78-byte long registration message to C2




The network traffic generated in practice is shown below.




The information in the registration packet is used to verify the legal identity of the BOT, and the format of the registration packet is parsed as shown below.


Main field parsing，others can be 0
——————————————————————————————————————————
02    --->type，register package
00 42 00 33 00 63  01 c8 02 fc 00 49   --->hardcoded，authentication
00 07   --->length of group string
75 6e 6b 6e 6f 77 6e ---->group string，"unknown"
——————————————————————————————————————————



After sending the registration packet the Bot starts to wait for C2 to issue commands, the first byte of the command packet specifies the command type.


0x00， heartbeat command code


Take the following heartbeat as an example




The format of the heartbeat packet is parsed as follows


Main field parsing，others can be 0
——————————————————————————————————————————
00  --->type，heartbeat package
1b 37 03 f3 25 e3  19 40 1e 68 1a d2   --->hardcoded
——————————————————————————————————————————



0x01，DDoS attack command code


Take the following attack instruction as an example




The format of the attack packet is parsed as follows


Main field parsing，others can be 0
——————————————————————————————————————————
01 　						--->type，attack package 
01							--->attack type
00 3c 						--->time (sec)
01							--->number of target
67 5f dd bc 00 20			--->target/mask,103.95.221.188/32
02							--->number of flag
	02							--->flag type, attack package length
	00 04						--->flag length
	31 34 36 30					--->flag data，1460
	
	
	01							--->flag type, port
	00 02						--->flag length
	35 33						--->flag data，53
——————————————————————————————————————————



0x03，exit






Telnet scan & propagation


Fbot uses the technique of SYN port detection in the propagation process to improve the efficiency of propagation.




From the above code snippet, it can be seen that its scanning traffic has 2 characteristics


 1. The number of scanned 23 ports is about twice as many as 26 ports
 2. The sequence number in the tcp header is equal to the target address in the ip header


When a port is detected as open, login is attempted using a hard-coded credential list. Once successful, the IP, port, account, password, etc. are sent back to Reporter (198.23.238.203:774) via the following code snippet.




The actual network traffic generated is shown in the following figure.




Finally, the Fbot sample is implanted to the device either with network download(see below) or ECHO, and the successful implantation information is sent back to Reporter.


1：Network download


If the device has wget or tftp, the Fbot sample of the corresponding CPU architecture on the device will be downloaded.




2：ECHO


If the device does not have a network download tool, the Fbot downloader of the corresponding CPU architecture is uploaded to the device via ECHO to download the Fbot samples.




The information of the Fbot downloader built into the sample is shown as follows.




In the above figure, the downloader with file offset 0x1D794 is used as an example.





MD5:9b49507d1876c3a550f7b7a6e4ec696d


ELF 32-bit LSB executable, ARM, version 1 (ARM), statically linked, stripped


Packer:None



Its function is to request the Fbot sample from the download server (198.23.238.203:80) and execute it.





Suggestions


We recommend Vantage Velocity users to check and update the firmware system in a timely manner.


We recommend that Vantage Velocity users set complex login passwords for management interfaces such as Web and SSH.


We recommend that readers monitor and block relevant IPs and URLs mentioned in this blog.



Contact us


Readers are always welcomed to reach us on twitter, or email to netlab at 360

dot cn.



IoC


IP:


198.23.238.203      	United States       	ASN36352            	AS-COLOCROSSING



C2:


198.23.238.203:5684



URL:


http://198.23.238.203/arm7



MD5:


deaee7ada44bf1c6af826d2d170c8698


{"version":"0.3.1","atoms":[],"cards":[["markdown",{"markdown":"### Background\nFbot, a botnet based on Mirai, has been very active ever sine we first blogged about it here[[1]](__GHOST_URL__/threat-alert-a-new-worm-fbot-cleaning-adbminer-is-using-a-blockchain-based-dns-en/)[[2]](__GHOST_URL__/the-new-developments-of-the-fbot-en/), we have seen this botnet using multiple 0 days before(some of them we have not disclosed yet) and it has been targeting various IoT devices, now, it is aiming a new category, traffic and transportation smart devices.\n\nOn February 20, 2021, the 360Netlab Threat Detection System captured attackers were using a remote command execution vulnerability (CVE-2020-9020)[[3]](https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-9023)[[4]](https://sku11army.blogspot.com/2020/01/iteris-vantage-velocity-field-unit-no.html) in the Vantage Velocity product from Iteris to spread Fbot botnet samples.\n\nAccording to Wikipedia[[5]](https://en.wikipedia.org/wiki/Iteris), Iteris, Inc. provides intelligent mobile infrastructure management services and produces sensors and other devices that record and predict traffic conditions.\n\nBased on the AIrLink GX450 Mobile Gateway production information found on the affected devices, we speculate that the affected devices are roadside monitoring device.\n\n### CVE-2020-9020 Vulnerability Analysis\nThrough the 360 FirmwareTotal system, we verified and analyzed the CVE-2020-9020 vulnerability, here is the brief.\n\n1. Vantage Velocity product synchronizes With NTP Server, where user can set the specified ntp server address.\n\n3. The `timeconfig.py` script does not filter the `htmlNtpServer` variable after accepting a user Web request, i.e., it is spliced into the shell variable format `\"ntpserver=\" + form[\"htmlNtpServer\"].value.strip()` and written to the `/root/timeparam` file.\n\n3. The command execution vulnerability is triggered when the `timeconfig.py` script calls the shell script `/root/ntpconfig`, which reads the `/root/timeparam` file to initialize the variable ntpserver.\n\n### Vulnerability impact scope\nThe 360 Quake cyberspace mapping system found the specific distribution of Vantage Velocity devices by mapping assets across the network as shown in the figure below.\n<a href=\"__GHOST_URL__/content/images/2021/03/CVE_2020_9020_stats_en.png\"><img src=\"__GHOST_URL__/content/images/2021/03/CVE_2020_9020_stats_en.png\" class=\"kg-image\"/></a>\n\n### Fbot botnet\nFbot is a botnet based on Mirai, with 2 main changes\n\n- Encryption algorithm\n- Registration packets, heartbeat packets\n\nThe basic information of this sample is shown below:\n\n> MD5:deaee7ada44bf1c6af826d2d170c8698\n>\n> ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped\n>\n> Packer:None\n\nIt has no added features in itself, the main function is\n\n- DDoS attack\n- Telnet scanning\n\nThe following section will briefly analyze around the above functions.\n\n\n### DDoS attack\nFirst Fbot establishes a connection with the hardcoded C2 (198.23.238.203:5684) via the following code snippet.\n\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_c2.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_c2.png\" class=\"kg-image\"/></a>\n\n\nThen it sends a 78-byte long registration message to C2\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_reg-1.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_reg-1.png\" class=\"kg-image\"/></a>\n\nThe network traffic generated in practice is shown below.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_regpkg.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_regpkg.png\" class=\"kg-image\"/></a>\n\n\nThe information in the registration packet is used to verify the legal identity of the BOT, and the format of the registration packet is parsed as shown below.\n\n```\nMain field parsing，others can be 0\n——————————————————————————————————————————\n02    --->type，register package\n00 42 00 33 00 63  01 c8 02 fc 00 49   --->hardcoded，authentication\n00 07   --->length of group string\n75 6e 6b 6e 6f 77 6e ---->group string，\"unknown\"\n——————————————————————————————————————————\n```\n\nAfter sending the registration packet the Bot starts to wait for C2 to issue commands, the first byte of the command packet specifies the command type.\n\n#### 0x00， heartbeat command code\nTake the following heartbeat as an example\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_beat.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_beat.png\" class=\"kg-image\"/></a>\n\n\nThe format of the heartbeat packet is parsed as follows\n\n```\nMain field parsing，others can be 0\n——————————————————————————————————————————\n00  --->type，heartbeat package\n1b 37 03 f3 25 e3  19 40 1e 68 1a d2   --->hardcoded\n——————————————————————————————————————————\n```\n\n#### 0x01，DDoS attack command code\nTake the following attack instruction as an example\n<a href=\"__GHOST_URL__/content/images/2021/02/ping_fbot_atk.png\"><img src=\"__GHOST_URL__/content/images/2021/02/ping_fbot_atk.png\" class=\"kg-image\"/></a>\n\n\nThe format of the attack packet is parsed as follows\n```\nMain field parsing，others can be 0\n——————————————————————————————————————————\n01 　\t\t\t\t\t\t--->type，attack package \n01\t\t\t\t\t\t\t--->attack type\n00 3c \t\t\t\t\t\t--->time (sec)\n01\t\t\t\t\t\t\t--->number of target\n67 5f dd bc 00 20\t\t\t--->target/mask,103.95.221.188/32\n02\t\t\t\t\t\t\t--->number of flag\n\t02\t\t\t\t\t\t\t--->flag type, attack package length\n\t00 04\t\t\t\t\t\t--->flag length\n\t31 34 36 30\t\t\t\t\t--->flag data，1460\n\t\n\t\n\t01\t\t\t\t\t\t\t--->flag type, port\n\t00 02\t\t\t\t\t\t--->flag length\n\t35 33\t\t\t\t\t\t--->flag data，53\n——————————————————————————————————————————\n```\n#### 0x03，exit\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_exit.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_exit.png\" class=\"kg-image\"/></a>\n\n### Telnet scan & propagation\nFbot uses the technique of SYN port detection in the propagation process to improve the efficiency of propagation.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_scan.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_scan.png\" class=\"kg-image\"/></a>\n\nFrom the above code snippet, it can be seen that its scanning traffic has 2 characteristics\n\n1. The number of scanned 23 ports is about twice as many as 26 ports\n2. The sequence number in the tcp header is equal to the target address in the ip header\n\nWhen a port is detected as open, login is attempted using a hard-coded credential list. Once successful, the IP, port, account, password, etc. are sent back to Reporter (198.23.238.203:774) via the following code snippet.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_report.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_report.png\" class=\"kg-image\"/></a>\n\nThe actual network traffic generated is shown in the following figure.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_reportpkg.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_reportpkg.png\" class=\"kg-image\"/></a>\n\nFinally, the Fbot sample is implanted to the device either with network download(see below) or ECHO, and the successful implantation information is sent back to Reporter.\n\n\n#### 1：Network download\nIf the device has wget or tftp, the Fbot sample of the corresponding CPU architecture on the device will be downloaded.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_dow_method.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_dow_method.png\" class=\"kg-image\"/></a>\n\n#### 2：ECHO\nIf the device does not have a network download tool, the Fbot downloader of the corresponding CPU architecture is uploaded to the device via ECHO to download the Fbot samples.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_echo_method.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_echo_method.png\" class=\"kg-image\"/></a>\n\nThe information of the Fbot downloader built into the sample is shown as follows.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_emelf.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_emelf.png\" class=\"kg-image\"/></a>\n\nIn the above figure, the downloader with file offset 0x1D794 is used as an example.\n>MD5:9b49507d1876c3a550f7b7a6e4ec696d\n>\n>ELF 32-bit LSB executable, ARM, version 1 (ARM), statically linked, stripped\n>\n>Packer:None\n\nIts function is to request the Fbot sample from the download server (198.23.238.203:80) and execute it.\n<a href=\"__GHOST_URL__/content/images/2021/02/velo_fbot_loader-1.png\"><img src=\"__GHOST_URL__/content/images/2021/02/velo_fbot_loader-1.png\" class=\"kg-image\"/></a>\n\n### Suggestions\nWe recommend Vantage Velocity users to check and update the firmware system in a timely manner.\n\nWe recommend that Vantage Velocity users set complex login passwords for management interfaces such as Web and SSH.\n\nWe recommend that readers monitor and block relevant IPs and URLs mentioned in this blog.\n\n### Contact us\nReaders are always welcomed to reach us on [**twitter**](https://twitter.com/360Netlab), or email to netlab at 360\ndot cn.\n\n\n\n### IoC\nIP:\n```\n198.23.238.203      \tUnited States       \tASN36352            \tAS-COLOCROSSING\n```\n\nC2:\n```\n198.23.238.203:5684\n```\n\nURL:\n```\nhttp://198.23.238.203/arm7\n```\n\nMD5:\n```\ndeaee7ada44bf1c6af826d2d170c8698\n```\n"}]],"markups":[],"sections":[[10,0],[1,"p",[]]],"ghostVersion":"3.0"}