Is Hajime botnet dead?
<!--kg-card-begin: markdown--><h1 id="overview">Overview</h1>
<p>The mysterious Hajime botnet was first discovered by Rapiditynetworks in Oct 2016, and it was all over the news earlier this year, but it seems that nobody talks about it any more now, is this botnet gone?</p>
<p>The answer is no, our team has been tracking this botnet for quite some time, and we have recently noticed the number of infections has been going up, and a very interesting feature, an x64 config has been added in the code(is the botnet author eying PC platform as the next target? Or key leaked?).</p>
<p>Unlike the traditional Hajime-runs-in-sandbox solution, which really has no control over the bot besides merely observing it(a good example, researcher cannot ask the bot in sandbox to go over all the peering nodes and pull all the files).</p>
<p>Our team was able to figure out the key exchange scheme of this botnet so we are able to participate in the Hajime network with full control of the bot behaviors, with that, we have been able to gain more insights. The visibility of this botnet is fairly poor in security research field, with the two observations above, we decide to talk about this botnet a little bit and also start a public accessible Hajime tracking project <a href="http://data.netlab.360.com/hajime/">here</a></p>
<h1 id="howhajimeworks">How Hajime works</h1>
<p>For some basic concepts of Hajime botnet, we suggest readers to take a good look at the Rapiditynetworks paper <a href="https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf">here</a> so we don’t need to repeat known facts here.</p>
<h2 id="overallframework">Overall framework</h2>
<p>Hajime’s implementation follows the modular programming paradigm. There are two common executable modules: &quot;execution module” (also known as stage2 or .i module) and “propagation module&quot; (also known as atk module).</p>
<p><img src="__GHOST_URL__/content/images/2017/09/6.Hajime_sync_files-en.jpg" alt="" loading="lazy"></p>
<p>In the propagation module (.i module), the Hajime nodes will establish a P2P network based on the DHT protocol. On top of this P2P network, Hajime nodes can perform inter-node negotiation, control command transmission and file synchronization. Any node can obtain the control instructions from the administrator without direct communication to the administrator. This not only provides protection for the administrator, but also maintains the stability of the botnet itself. Once the network is set up, it is extremely difficult to take it down.</p>
<p><img src="__GHOST_URL__/content/images/2017/09/5.How_Hajime_work-1.jpg" alt="" loading="lazy"></p>
<p>In the DHT network, Hajime encodes the config file as a special infohash value. This is a 160 bit binary number, changed daily. By indexing the infohash value, Hajime can get the latest config file.</p>
<p><img src="__GHOST_URL__/content/images/2017/09/7.Hajime_config.png" alt="" loading="lazy"></p>
<p>The above figure shows a config file in August 12, 2017. You can see it is a text file. The modules field contains the module file name for different CPU architectures. The peers field specifies the entry domain name for the DHT network. The two domain names are both valid and publicly accessible. The configuration file will direct Hajime to synchronize to the latest &quot;propagation module (atk module)&quot; or “execution module (.i module)&quot;.</p>
<h2 id="filesynchronization">File synchronization</h2>
<p>In a DHT network, each Hajime node can correspond to a peer. By searching in the DHT network, the Hajime node can easily get the address information of other Hajime nodes. During file synchronization, it will traverse other nodes sequentially and perform synchronization on each node. The inter-node communication relies on the uTP protocol. This protocol implements mechanisms such as three-way handshake, session retransmission and session interruption based on UDP to ensure trusted communication between Hajime nodes.</p>
<h2 id="keyexchange">Key exchange</h2>
<p>On the channel provided by uTP, Hajime made the RC4 communication encryption for each session to ensure that others could not restore the content by packet capture. Besides, Hajime uses a key negotiation algorithm to ensure that the RC4 key is not stealable.</p>
<p><img src="__GHOST_URL__/content/images/2017/09/8.DH25519_For_Hajime.png" alt="" loading="lazy"></p>
<p>Hajime uses ECDH as the key exchange protocol and selects a key exchange algorithm based on Curve25519 elliptic curve. Although there are many open ECDH implementations on the Internet, the author of Hajime did not use the existing code directly. He has implemented a more efficient key exchange process. This implementation features on projecting points from the original elliptical space to the new one-dimensional series. Besides, in the &quot;double point&quot; calculation process, it only calculates the X coordinates, without considering the Y coordinates. Therefore he can improve the computational efficiency.</p>
<p><em>Reference for Curve25519 can be found at: <a href="https://cr.yp.to/ecdh.html">https://cr.yp.to/ecdh.html</a></em><br>
<em>The fundamentals for the new key exchange algorithm can be found at <a href="https://cr.yp.to/ecdh/curvezero-20060726.pdf">https://cr.yp.to/ecdh/curvezero-20060726.pdf</a></em></p>
<h2 id="documentsignature">Document Signature</h2>
<p>In P2P networks, nodes are untrustworthy, and anyone can fake a Hajime node at a very low cost. To ensure that the Hajime network is completely controllable and not stolen by others, Hajime nodes need to verify the signature of each synchronized file before acceptance and execution. Hajime adopts a public digital signature algorithm called ED25519 and uses <code>A55CEED41FECB3AC66B6515AB5D383791B00FEC166A590D7626A04C2466B3F54</code> as public key, which is integrated into each Hajime's execution module. Thus every Hajime nodes can verify the integrity of an new synchronized file.</p>
<h1 id="currentstatus">Current status</h1>
<p>The following diagram shows daily active hijime nodes since the beginning of July.</p>
<h2 id="dailyactivenodes">Daily active nodes</h2>
<p>Below shows the number of daily active IPs:</p>
<p><img src="__GHOST_URL__/content/images/2017/09/Hajime_BotTrends-1.jpg" alt="" loading="lazy"></p>
<p>It is not difficult to spot that in the second half of July, Hajime infection went down. Correspondently there were no botnet file update during that period(did the author go for vacation?) Starting from August, the author started to update the Hajime files, and the bot numbers started to going up, noticeably on 2017-08-06 and 2017-08-12, with the author pushing update, the botnet climbed up really quickly. Subsequently, Hajime completed several updates on 2017-08-18, 2017-08-19, 2017-08-22 and 2017-09-04. This opened the new normality of frequent updates.</p>
<h2 id="geographicaldistribution">Geographical distribution</h2>
<p>The following figure shows the geographical activity of Hajime in the past two months:</p>
<p><img src="__GHOST_URL__/content/images/2017/09/Hajime_Bot_Distribution-1.jpg" alt="" loading="lazy"></p>
<p>The deeper the color, the more serious the affected area.</p>
<h2 id="updatefrequency">Update frequency</h2>
<p>Hajime was not updated frequently in July, and there was a two-week break. However, after August 5, Hajime began to regain activity:</p>
<p><img src="__GHOST_URL__/content/images/2017/09/3_Hajime_update_config.png" alt="" loading="lazy"></p>
<p>In fact, all updates in the past month are patches on the existing code. There’s no dramatic change.</p>
<h2 id="updateonbotpropagation">Update on bot propagation</h2>
<p>Originally,Hajime propagated mainly thought TR_069 vulnerability and weak telnet account, as time goes by, more vulnerabilities have been added, and the following is the newest vulnerability breakdown.</p>
<p><img src="__GHOST_URL__/content/images/2017/09/4.-Hajime_spread_way_en-1.jpg" alt="" loading="lazy"></p>
<ul>
<li><code>2017-01-17 atk.arm5.1481380646 2487b4ed4a2f55bfd743b2e6b98f8121</code></li>
<li><code>2017-05-29 atk.arm5.1496096402 a238462e1e758792c5d1f04b82f4a6a0</code></li>
<li><code>http://console-cowboys.blogspot.com/2013/01/swann-song-dvr-insecurity.html</code></li>
<li><code>https://gist.github.com/ylluminate/fcee91965b58695460ce849c424488f7</code></li>
<li><code>https://twitter.com/masafuminegishi/status/870182653797871617</code></li>
</ul>
<h2 id="cpuarchitecturedistributionofhajimenode">CPU Architecture Distribution of Hajime Node</h2>
<p>The propagation of Hajime is limited among a small number of different CPUs. Our analysis on 18433 Hajime nodes shows that the Mipseb CPU is affected the most.</p>
<p><img src="__GHOST_URL__/content/images/2017/09/11_Hajime_CPU_count-1.jpg" alt="" loading="lazy"></p>
<h1 id="moreobservationsonhajime">More Observations on Hajime</h1>
<h2 id="supportforx64platform">Support for x64 platform?</h2>
<p>Our tracking system captured a special config file <code>b8a5082689606ea20a557883dbff7d10</code> on 2017-08-29.<br>
This config file can be verified successfully and contained settings for X64 CPU, which indicated that Hajime author is planning to support PC platforms.</p>
<p>The config file is shown as followed:</p>
<p><img src="__GHOST_URL__/content/images/2017/09/9.Hajime_config_with_x64.png" alt="" loading="lazy"></p>
<p>However there are some doubts in this config file:</p>
<ul>
<li>We can only get two modules (atk.mipseb/.i.mipseb) listed in the config file while other CPU architecture's modules are unavailable in Hajime network.</li>
<li>The &quot;info&quot; field, which contains the author's whitehat declaration, is missing in this config file. This is quite abnormal according to author's previous habit.</li>
</ul>
<p><img src="__GHOST_URL__/content/images/2017/09/12.Hajime_Verify_Confirm.jpg" alt="" loading="lazy"></p>
<p>So we have two possibilities here:</p>
<ul>
<li>
<p>The author has intention to support x64 platform. As mentioned before, all Hajime files are signed by the private key and need to be verified before any Hajime node takes the update.</p>
</li>
<li>
<p>The private key has been leaked, someone else is trying to poison the Hajime network.</p>
</li>
</ul>
<p>We prefer the first scenario at this point, and it will be big change for Hajime itself if it is moving to the pc battleground. We will keep a close eye on what will unfold in the future.</p>
<p>1: <a href="https://x86.re/blog/hajime-a-follow-up/">https://x86.re/blog/hajime-a-follow-up/</a><br>
2: <a href="https://github.com/Psychotropos/hajime_hashes">https://github.com/Psychotropos/hajime_hashes</a><br>
3: <a href="https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf">https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf</a><br>
4: <a href="https://securelist.com/hajime-the-mysterious-evolving-botnet/78160/">https://securelist.com/hajime-the-mysterious-evolving-botnet/78160/</a></p>
<!--kg-card-end: markdown-->
Overview


The mysterious Hajime botnet was first discovered by Rapiditynetworks in Oct 2016, and it was all over the news earlier this year, but it seems that nobody talks about it any more now, is this botnet gone?


The answer is no, our team has been tracking this botnet for quite some time, and we have recently noticed the number of infections has been going up, and a very interesting feature, an x64 config has been added in the code(is the botnet author eying PC platform as the next target? Or key leaked?).


Unlike the traditional Hajime-runs-in-sandbox solution, which really has no control over the bot besides merely observing it(a good example, researcher cannot ask the bot in sandbox to go over all the peering nodes and pull all the files).


Our team was able to figure out the key exchange scheme of this botnet so we are able to participate in the Hajime network with full control of the bot behaviors, with that, we have been able to gain more insights. The visibility of this botnet is fairly poor in security research field, with the two observations above, we decide to talk about this botnet a little bit and also start a public accessible Hajime tracking project here



How Hajime works


For some basic concepts of Hajime botnet, we suggest readers to take a good look at the Rapiditynetworks paper here so we don’t need to repeat known facts here.



Overall framework


Hajime’s implementation follows the modular programming paradigm. There are two common executable modules: "execution module” (also known as stage2 or .i module) and “propagation module" (also known as atk module).





In the propagation module (.i module), the Hajime nodes will establish a P2P network based on the DHT protocol. On top of this P2P network, Hajime nodes can perform inter-node negotiation, control command transmission and file synchronization. Any node can obtain the control instructions from the administrator without direct communication to the administrator. This not only provides protection for the administrator, but also maintains the stability of the botnet itself. Once the network is set up, it is extremely difficult to take it down.





In the DHT network, Hajime encodes the config file as a special infohash value. This is a 160 bit binary number, changed daily. By indexing the infohash value, Hajime can get the latest config file.





The above figure shows a config file in August 12, 2017. You can see it is a text file. The modules field contains the module file name for different CPU architectures. The peers field specifies the entry domain name for the DHT network. The two domain names are both valid and publicly accessible. The configuration file will direct Hajime to synchronize to the latest "propagation module (atk module)" or “execution module (.i module)".



File synchronization


In a DHT network, each Hajime node can correspond to a peer. By searching in the DHT network, the Hajime node can easily get the address information of other Hajime nodes. During file synchronization, it will traverse other nodes sequentially and perform synchronization on each node. The inter-node communication relies on the uTP protocol. This protocol implements mechanisms such as three-way handshake, session retransmission and session interruption based on UDP to ensure trusted communication between Hajime nodes.



Key exchange


On the channel provided by uTP, Hajime made the RC4 communication encryption for each session to ensure that others could not restore the content by packet capture. Besides, Hajime uses a key negotiation algorithm to ensure that the RC4 key is not stealable.





Hajime uses ECDH as the key exchange protocol and selects a key exchange algorithm based on Curve25519 elliptic curve. Although there are many open ECDH implementations on the Internet, the author of Hajime did not use the existing code directly. He has implemented a more efficient key exchange process. This implementation features on projecting points from the original elliptical space to the new one-dimensional series. Besides, in the "double point" calculation process, it only calculates the X coordinates, without considering the Y coordinates. Therefore he can improve the computational efficiency.


Reference for Curve25519 can be found at: https://cr.yp.to/ecdh.html

The fundamentals for the new key exchange algorithm can be found at https://cr.yp.to/ecdh/curvezero-20060726.pdf



Document Signature


In P2P networks, nodes are untrustworthy, and anyone can fake a Hajime node at a very low cost. To ensure that the Hajime network is completely controllable and not stolen by others, Hajime nodes need to verify the signature of each synchronized file before acceptance and execution. Hajime adopts a public digital signature algorithm called ED25519 and uses A55CEED41FECB3AC66B6515AB5D383791B00FEC166A590D7626A04C2466B3F54 as public key, which is integrated into each Hajime's execution module. Thus every Hajime nodes can verify the integrity of an new synchronized file.



Current status


The following diagram shows daily active hijime nodes since the beginning of July.



Daily active nodes


Below shows the number of daily active IPs:





It is not difficult to spot that in the second half of July, Hajime infection went down. Correspondently there were no botnet file update during that period(did the author go for vacation?) Starting from August, the author started to update the Hajime files, and the bot numbers started to going up, noticeably on 2017-08-06 and 2017-08-12, with the author pushing update, the botnet climbed up really quickly. Subsequently, Hajime completed several updates on 2017-08-18, 2017-08-19, 2017-08-22 and 2017-09-04. This opened the new normality of frequent updates.



Geographical distribution


The following figure shows the geographical activity of Hajime in the past two months:





The deeper the color, the more serious the affected area.



Update frequency


Hajime was not updated frequently in July, and there was a two-week break. However, after August 5, Hajime began to regain activity:





In fact, all updates in the past month are patches on the existing code. There’s no dramatic change.



Update on bot propagation


Originally,Hajime propagated mainly thought TR_069 vulnerability and weak telnet account, as time goes by, more vulnerabilities have been added, and the following is the newest vulnerability breakdown.





 * 2017-01-17 atk.arm5.1481380646 2487b4ed4a2f55bfd743b2e6b98f8121
 * 2017-05-29 atk.arm5.1496096402 a238462e1e758792c5d1f04b82f4a6a0
 * http://console-cowboys.blogspot.com/2013/01/swann-song-dvr-insecurity.html
 * https://gist.github.com/ylluminate/fcee91965b58695460ce849c424488f7
 * https://twitter.com/masafuminegishi/status/870182653797871617



CPU Architecture Distribution of Hajime Node


The propagation of Hajime is limited among a small number of different CPUs. Our analysis on 18433 Hajime nodes shows that the Mipseb CPU is affected the most.






More Observations on Hajime



Support for x64 platform?


Our tracking system captured a special config file b8a5082689606ea20a557883dbff7d10 on 2017-08-29.

This config file can be verified successfully and contained settings for X64 CPU, which indicated that Hajime author is planning to support PC platforms.


The config file is shown as followed:





However there are some doubts in this config file:


 * We can only get two modules (atk.mipseb/.i.mipseb) listed in the config file while other CPU architecture's modules are unavailable in Hajime network.
 * The "info" field, which contains the author's whitehat declaration, is missing in this config file. This is quite abnormal according to author's previous habit.





So we have two possibilities here:


 * 
   
   
   The author has intention to support x64 platform. As mentioned before, all Hajime files are signed by the private key and need to be verified before any Hajime node takes the update.
   

 * 
   
   
   The private key has been leaked, someone else is trying to poison the Hajime network.
   


We prefer the first scenario at this point, and it will be big change for Hajime itself if it is moving to the pc battleground. We will keep a close eye on what will unfold in the future.


1: https://x86.re/blog/hajime-a-follow-up/

2: https://github.com/Psychotropos/hajime_hashes

3: https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf

4: https://securelist.com/hajime-the-mysterious-evolving-botnet/78160/

{"version":"0.3.1","markups":[],"atoms":[],"cards":[["markdown",{"cardName":"card-markdown","markdown":"# Overview \n\nThe mysterious Hajime botnet was first discovered by Rapiditynetworks in Oct 2016, and it was all over the news earlier this year, but it seems that nobody talks about it any more now, is this botnet gone?\n\nThe answer is no, our team has been tracking this botnet for quite some time, and we have recently noticed the number of infections has been going up, and a very interesting feature, an x64 config has been added in the code(is the botnet author eying PC platform as the next target? Or key leaked?). \n\nUnlike the traditional Hajime-runs-in-sandbox solution, which really has no control over the bot besides merely observing it(a good example, researcher cannot ask the bot in sandbox to go over all the peering nodes and pull all the files). \n\nOur team was able to figure out the key exchange scheme of this botnet so we are able to participate in the Hajime network with full control of the bot behaviors, with that, we have been able to gain more insights. The visibility of this botnet is fairly poor in security research field, with the two observations above, we decide to talk about this botnet a little bit and also start a public accessible Hajime tracking project [here](http://data.netlab.360.com/hajime/)\n\n# How Hajime works\n\nFor some basic concepts of Hajime botnet, we suggest readers to take a good look at the Rapiditynetworks paper [here](https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf) so we don’t need to repeat known facts here.\n\n## Overall framework\n\nHajime’s implementation follows the modular programming paradigm. There are two common executable modules: \"execution module” (also known as stage2 or .i module) and “propagation module\" (also known as atk module).\n\n![](__GHOST_URL__/content/images/2017/09/6.Hajime_sync_files-en.jpg)\n\nIn the propagation module (.i module), the Hajime nodes will establish a P2P network based on the DHT protocol. On top of this P2P network, Hajime nodes can perform inter-node negotiation, control command transmission and file synchronization. Any node can obtain the control instructions from the administrator without direct communication to the administrator. This not only provides protection for the administrator, but also maintains the stability of the botnet itself. Once the network is set up, it is extremely difficult to take it down.\n\n\n![](__GHOST_URL__/content/images/2017/09/5.How_Hajime_work-1.jpg)\n\nIn the DHT network, Hajime encodes the config file as a special infohash value. This is a 160 bit binary number, changed daily. By indexing the infohash value, Hajime can get the latest config file.\n\n\n![](__GHOST_URL__/content/images/2017/09/7.Hajime_config.png)\n\n\nThe above figure shows a config file in August 12, 2017. You can see it is a text file. The modules field contains the module file name for different CPU architectures. The peers field specifies the entry domain name for the DHT network. The two domain names are both valid and publicly accessible. The configuration file will direct Hajime to synchronize to the latest \"propagation module (atk module)\" or “execution module (.i module)\".\n\n\n## File synchronization\n\nIn a DHT network, each Hajime node can correspond to a peer. By searching in the DHT network, the Hajime node can easily get the address information of other Hajime nodes. During file synchronization, it will traverse other nodes sequentially and perform synchronization on each node. The inter-node communication relies on the uTP protocol. This protocol implements mechanisms such as three-way handshake, session retransmission and session interruption based on UDP to ensure trusted communication between Hajime nodes.\n\n## Key exchange\n\nOn the channel provided by uTP, Hajime made the RC4 communication encryption for each session to ensure that others could not restore the content by packet capture. Besides, Hajime uses a key negotiation algorithm to ensure that the RC4 key is not stealable.\n\n![](__GHOST_URL__/content/images/2017/09/8.DH25519_For_Hajime.png)\n\nHajime uses ECDH as the key exchange protocol and selects a key exchange algorithm based on Curve25519 elliptic curve. Although there are many open ECDH implementations on the Internet, the author of Hajime did not use the existing code directly. He has implemented a more efficient key exchange process. This implementation features on projecting points from the original elliptical space to the new one-dimensional series. Besides, in the \"double point\" calculation process, it only calculates the X coordinates, without considering the Y coordinates. Therefore he can improve the computational efficiency.\n\n*Reference for Curve25519 can be found at: https://cr.yp.to/ecdh.html*  \n*The fundamentals for the new key exchange algorithm can be found at https://cr.yp.to/ecdh/curvezero-20060726.pdf*\n\n## Document Signature\n\nIn P2P networks, nodes are untrustworthy, and anyone can fake a Hajime node at a very low cost. To ensure that the Hajime network is completely controllable and not stolen by others, Hajime nodes need to verify the signature of each synchronized file before acceptance and execution. Hajime adopts a public digital signature algorithm called ED25519 and uses `A55CEED41FECB3AC66B6515AB5D383791B00FEC166A590D7626A04C2466B3F54` as public key, which is integrated into each Hajime's execution module. Thus every Hajime nodes can verify the integrity of an new synchronized file.\n\n# Current status\n\nThe following diagram shows daily active hijime nodes since the beginning of July.\n\n\n\n## Daily active nodes\nBelow shows the number of daily active IPs:\n\n![](__GHOST_URL__/content/images/2017/09/Hajime_BotTrends-1.jpg)\n\n\nIt is not difficult to spot that in the second half of July, Hajime infection went down. Correspondently there were no botnet file update during that period(did the author go for vacation?) Starting from August, the author started to update the Hajime files, and the bot numbers started to going up, noticeably on 2017-08-06 and 2017-08-12, with the author pushing update, the botnet climbed up really quickly. Subsequently, Hajime completed several updates on 2017-08-18, 2017-08-19, 2017-08-22 and 2017-09-04. This opened the new normality of frequent updates.\n\n## Geographical distribution\n\nThe following figure shows the geographical activity of Hajime in the past two months:\n\n![](__GHOST_URL__/content/images/2017/09/Hajime_Bot_Distribution-1.jpg)\n\nThe deeper the color, the more serious the affected area. \n\n## Update frequency\n\nHajime was not updated frequently in July, and there was a two-week break. However, after August 5, Hajime began to regain activity:\n\n![](__GHOST_URL__/content/images/2017/09/3_Hajime_update_config.png)\n\nIn fact, all updates in the past month are patches on the existing code. There’s no dramatic change.\n\n## Update on bot propagation\n\nOriginally,Hajime propagated mainly thought TR_069 vulnerability and weak telnet account, as time goes by, more vulnerabilities have been added, and the following is the newest vulnerability breakdown.\n\n![](__GHOST_URL__/content/images/2017/09/4.-Hajime_spread_way_en-1.jpg)\n\n* `2017-01-17 atk.arm5.1481380646 2487b4ed4a2f55bfd743b2e6b98f8121`\n* `2017-05-29 atk.arm5.1496096402 a238462e1e758792c5d1f04b82f4a6a0`\n* `http://console-cowboys.blogspot.com/2013/01/swann-song-dvr-insecurity.html`\n* `https://gist.github.com/ylluminate/fcee91965b58695460ce849c424488f7`\n* `https://twitter.com/masafuminegishi/status/870182653797871617`\n\n## CPU Architecture Distribution of Hajime Node\n\nThe propagation of Hajime is limited among a small number of different CPUs. Our analysis on 18433 Hajime nodes shows that the Mipseb CPU is affected the most.\n\n![](__GHOST_URL__/content/images/2017/09/11_Hajime_CPU_count-1.jpg)\n\n\n\n# More Observations on Hajime\n\n## Support for x64 platform?\n\nOur tracking system captured a special config file `b8a5082689606ea20a557883dbff7d10` on 2017-08-29.\nThis config file can be verified successfully and contained settings for X64 CPU, which indicated that Hajime author is planning to support PC platforms.\n\nThe config file is shown as followed:\n\n![](__GHOST_URL__/content/images/2017/09/9.Hajime_config_with_x64.png)\n\nHowever there are some doubts in this config file:\n\n* We can only get two modules (atk.mipseb/.i.mipseb) listed in the config file while other CPU architecture's modules are unavailable in Hajime network.\n* The \"info\" field, which contains the author's whitehat declaration, is missing in this config file. This is quite abnormal according to author's previous habit.\n\n\n![](__GHOST_URL__/content/images/2017/09/12.Hajime_Verify_Confirm.jpg)\n\n\nSo we have two possibilities here:\n\n* The author has intention to support x64 platform. As mentioned before, all Hajime files are signed by the private key and need to be verified before any Hajime node takes the update.\n\n\n* The private key has been leaked, someone else is trying to poison the Hajime network.\n\n\nWe prefer the first scenario at this point, and it will be big change for Hajime itself if it is moving to the pc battleground. We will keep a close eye on what will unfold in the future.\n\n\n\n1: https://x86.re/blog/hajime-a-follow-up/\n2: https://github.com/Psychotropos/hajime_hashes\n3: https://security.rapiditynetworks.com/publications/2016-10-16/hajime.pdf \n4: https://securelist.com/hajime-the-mysterious-evolving-botnet/78160/"}]],"sections":[[10,0]],"ghostVersion":"3.0"}