Kaiji IoT Botnet
First observed in April 2020, Kaiji is a Go-based worm and botnet associated with an ongoing campaign targeting exposed Linux servers and Internet-of-Things (IoT) devices. Unusually for IoT malware, Kaiji appears to be entirely bespoke and does not contain any code from more well-known botnets such as Mirai.
Summary
First observed in April 2020, Kaiji is a Go-based worm and botnet associated with an ongoing campaign targeting exposed Linux servers and Internet-of-Things (IoT) devices. Unusually for IoT malware, Kaiji appears to be entirely bespoke and does not contain any code from more well-known botnets such as Mirai.
Affected platforms
The following platforms are known to be affected:
- Linux web servers
- Linux-based IoT devices
Threat details
Kaiji is distributed via SSH brute-force attacks against exposed root user accounts. If an SSH session is successfully created, a bash script is then executed to install Kaiji on the affected system.
Once installed, Kaiji will connect to a command and control server to retrieve a list of IP ranges to attempt further brute-force attacks against and a second list of target IP addresses, which Kaiji will perform a number of distributed denial-of-service attacks against. At the time of publication, Kaiji is able to perform ACK, IPSpoof, SYN, SYNACK, TCP, and UDP flood attacks.
Threat updates
| Date | Update |
|---|---|
| 25 Jun 2020 | p>Kaiji is now targeting vulnerable Docker systems. After identifying Docker hosts exposed over port 2375, the group operating Kaiji deliver an ARM container containing a copy of the malware and a startup script, before executing it. The script will then launch Kaiji before deleting all Docker components that aren't required for Kaiji to perform DDoS attacks. |
Remediation steps
| Type | Step |
|---|---|
|
To prevent and detect an infection, NHS Digital advises that:
Please note that NCSC maintains guidance for securely configuring a wide range of end user device (EUD) platforms. For further details refer to their end user device security guidance pages. Additionally, to protect against a distributed denial-of-service (DDoS) attack, organisations should ensure:
Should an organisation suspect it is subject to an active DDoS attack, they should ensure that every effort is made to stop the attack and restore service. However, care should be taken to ensure that the attackers are not using the DDoS attack as a distraction whilst other, potentially more sensitive, systems are exploited. Monitoring of critical systems is recommended, including the use of host-based intrusion prevention and detection systems (HIPS/HIDS) where appropriate. |
Indicators of compromise
Last edited: 29 June 2021 12:01 pm