View source for HOIC - High Orbit Ion Canon (DoS/DDoS-Tool)

== Introduction ==

The High Orbit Ion Cannon (HOIC) is an open-source tool used for Distributed Denial of Service (DDoS) attacks. A DDoS attack aims to make a server or website inaccessible by overloading it with a large number of requests. HOIC was developed as a successor to the Low Orbit Ion Cannon (LOIC) and is characterized by its high efficiency in HTTP flooding attacks. The tool does not require in-depth technical knowledge and can also be used by inexperienced users.

'''Important:''' The use of HOIC for DDoS attacks is illegal in many countries and can have legal consequences.

== Functionality and Theory ==

A DDoS attack using HOIC relies on HTTP flooding, a type of Layer 7 (application layer) attack that sends a massive number of HTTP requests to a target server to exhaust its resources. HTTP flooding can quickly make the server unable to process legitimate requests, impacting its performance or causing it to crash.

''' Common DDoS Attack Types and HTTP Flooding '''
</br>
While there are various types of DDoS attacks, HOIC specifically uses HTTP flooding, which is effective against web servers because it mimics regular user traffic. Unlike attacks like SYN flooding or UDP flooding, which overwhelm the network layer, HTTP flooding targets the application layer, making it harder to filter and block because it looks similar to legitimate traffic.

''' Role of Booster Files in HOIC Attacks '''
</br>
Booster files in HOIC modify the HTTP headers in the outgoing requests, dynamically adding details like browser and operating system information. This customization makes the requests appear more legitimate, making it harder for network security systems to detect and block the DDoS traffic. Booster files essentially disguise the malicious traffic to evade detection by firewall or DDoS mitigation systems.

== Requirements for a HOIC Attack ==

'''Required hardware:'''

* '''Computer/laptop:''' A standard PC or laptop is sufficient to use HOIC as it does not have high hardware requirements.
* '''Internet connection:''' A stable connection to the target host is important to send the attack packets effectively.

'''Required software:'''
<ul>
  <li><b>Operating system:</b> HOIC works on Windows (XP, 7, 8, 10). However, it can also be used on Linux-based systems via Wine (a Windows compatibility layer program).</li>
  <li><b>HOIC Tool:</b> The HOIC tool itself. It can be downloaded from various sources on the internet, but be careful with the source so as not to download malware. HOIC is available as open-source software.</li>
  <li><b>Optional:</b>
    <ul style="list-style-type: none; margin-left: 20px;">
      <li><b>Wine (for Linux):</b> Allows Windows programs to run on Linux.</li>
      <li><b>Virtual Machine:</b> HOIC can be run in a VM so that the host OS is not affected in the event of a malware infection or error. Please keep in mind that a native installation on the Windows host may perform better.</li>
    </ul>
  </li>
</ul>

== Step-by-Step Guide to Carrying Out a DDoS Attack with HOIC ==

<ol>
 <li>'''Preparation:''' 
  <ul>
    <li>Download HOIC from a trustworthy source. Unfortunately, there is no official source for the tool.</li>
    <li>Unzip the downloaded archive and execute the HOIC.exe file.</li>
  </ul>
 </li>

<li>'''Start HOIC:''' 
  <ul>
    <li><b>User Interface:</b> Once you have started HOIC, a simple user interface will open with options to configure the attack.
      [[File:hoic_ui.png|thumb|none|600px|HOIC UI <ref name="Author"/>]]
    </li>

    <li><b>Insert Target:</b> Click on "+" under Targets to add a target. A new dialogue window then opens where you can enter the URL of the target server. Start with "http://" followed by the IP or domain name of the web server you want to attack. Under Power, you can use the slider to select the intensity of the attack (e.g., High). With the Booster, you can select booster files that strengthen the attack. By default, you can leave this blank; a good choice would be GenericBoost.hoic. You can add multiple targets at the same time (up to 256 targets).
     
     [[File:hoic_target_ui.png|thumb|none|600px|Target config options <ref name="Author"/>]]
 
    </li>
    <li><b>Select attack method:</b> HOIC offers only one attack method, HTTP flooding</li>
  </ul>
</li>

 <li>'''Set Attack Parameters:''' 
  <ul>
   <li><b>Number of attacks per second (threads):</b> Set how many requests per second should be sent to the target. The higher the number, the stronger the attack, as increasing the number of threads used increases the number of attacks per second.</li>
  <li><b>Important to note:</b> Start with a lower number of threads at the beginning and then increase slowly and not directly with 100 threads, as this can often lead to a programme crash.
    
     [[File:hoic_ui_thread_frame.png|thumb|none|600px|HOIC UI <ref name="Author"/>]]
    
  </li>

  </ul>
 </li>

 <li> <b>Add booster files (optional)</b>
  <ul>
    <li><b>Boosters:</b> These are small scripts that make the attack more efficient and harder to detect. Booster files modify the HTTP requests and hide the patterns of the attacks. These files can also be downloaded and added to the tool.</li>
  </ul>
 </li>

 <li> <b>Start attack</b>
  <ul>
    <li><b>Launch attack:</b> Click on ‘Fire Teh Lazer!’ (the launch button) to start the DDoS attack. HOIC will now send large amounts of HTTP requests to the target.</li>
    <li><b>Monitor attack:</b> You can monitor the sent packets, threads, and targets during the attack.</li>
    <li>Now you can see that the status has changed to Engaging, which means that the attack is currently active. At the OUTPUT below, you can see the number of packets sent, which is constantly counting up during the active attack.
     [[File:hoic_ui_engaging.jpg|thumb|none|600px|HOIC UI <ref name="Author"/>]]
</li>
  </ul>
 </li>

</ol>

== End Attack and Responsible Usage ==

<b>End attack:</b>
</br>
If you want to stop the attack, click on ‘Fire Teh Lazer!’ again. It is recommended that you do not leave the attack running for too long, as it can place a heavy load on the bandwidth of your own system and network.

<b>Responsible behaviour:</b>
</br>
DDoS attacks are illegal in many countries and can result in criminal prosecution. Only use HOIC for testing purposes or in a controlled environment where you have permission to attack the target.

== Test of a HOIC attack on an NGINX web server ==

To demonstrate the effects of a DDoS attack with HOIC, an NGINX web server was set up on an Ubuntu server for test purposes. A HOIC attack was then launched on this machine. The following image shows the TCP dump and the NGINX access logs, which document the incoming data traffic during the attack.
<ul>
 <li><b>TCP dump:</b> Here you can see how a large number of TCP packets, especially HTTP requests, are received on port 80 of the web server. This clearly shows how HOIC generates a flood of requests in a short time, which overloads the server.
 </li>
 <li><b>NGINX Access Logs:</b> These log every incoming request to the server. As can be seen, the HTTP GET requests arrive in very short succession, which simulates the overloading of the web server. This type of attack often results in the server no longer being able to process legitimate requests.
 </li>
</ul>
This test illustrates how a server can be quickly overloaded by a DDoS attack with HOIC by bombarding it with an excessive number of requests.
[[File:nginx_traffic_dump.png|thumb|none|600px|tcpdump & access-log on attacked Webserver <ref name="Author"/>]]
   
In this test, only a single web server was attacked to demonstrate the effects of the HOIC tool. In a real-world scenario, however, a DDoS attack is often carried out by hundreds or even thousands of machines simultaneously. Hacking groups configure the tool on many machines and launch the attack simultaneously on the target, for example a website or server. The enormous number of simultaneous requests results in the target's resources being fully utilized so that it can no longer respond to legitimate user requests or loses packets. The more attackers involved, the more serious the impact on the target system.

== Effect of booster files on the HTTP header ==

A decisive difference between an attack with and without booster files can be clearly seen in the HTTP headers of the requests that are recorded in the server's access log. Here in the picture you can see the requests without the use of a booster file. These requests do not contain any details about the user agent, browser or operating system, which are normally specified in the HTTP header. Such requests look very generic and are easy to recognize as part of an attack.

[[File:nginx_traffix_dump_without_booster.png|thumb|none|600px|access-log without booster file <ref name="Author"/>]]

With a booster file, however, as you can see in the images below, the HTTP header is changed dynamically. The booster file adds various information, such as the name of the browser (e.g. Firefox, Opera), the operating system used (Windows, MacOS) and other details that resemble legitimate user requests. This makes it more difficult to detect the attack, as the requests look more realistic and appear to come from different devices. However, the IP address is not changed and is always the same.

[[File:nginx_traffic_with_booster_1.png|thumb|none|1000px|access-log with booster file<ref name="Author"/>]]


[[File:nginx_traffix_dump_with_booster_2.png|thumb|none|1000px|access-log with booster file <ref name="Author"/>]]

<ul>
 <li><b>Without booster file:</b> The HTTP header is empty or incomplete, which makes the attack easily recognizable.
 </li>
 <li><b>With booster file:</b> The HTTP header contains complete and dynamically changing information, such as browser and operating system, which makes the traffic appear more legitimate. The aim is to disguise the requests so that they are harder to identify as malicious.
 </li>
</ul>

<b>Warning:</b> Using HOIC for illegal DDoS attacks can lead to criminal prosecution. Use the tool only for testing and learning purposes in a controlled isolated environment.

== References ==
<references>
<ref name="Author">Westreicher, Tristan. (2024). Own screenshots created for the article and author of the article</ref>

</references>
* Step by Step Guide inspiration: https://github.com/Samsar4/Ethical-Hacking-Labs/blob/master/9-Denial-of-Service/2-DDoS-using-HOIC.md
* Steve Mansfield-Devine. The evolution of ddos. Computer Fraud Security, 2014(10):15–20, 2014.

[[Category:Documentation]]