Satori IoT Worm

A new variant of the Mirai botnet malware, known as Satori, has been observed using hard-coded exploits to target Internet of Things (IoT) devices.

Threat ID:: CC-1846
Category:: Botnet, Worm
Threat Severity:: Low
Threat Vector:: Exploit
Published:: 12 December 2017 12:00 AM

Report a cyber attack: call 0300 303 5222 or email [email protected]

This content has been archived

This article no longer conforms to NHS Digital's standards for cyber alerts, and may contain outdated or inaccurate information. Use of this information contained in this page is at your own risk

Summary

A new variant of the Mirai botnet malware, known as Satori, has been observed using hard-coded exploits to target Internet of Things (IoT) devices.

Threat details

Despite using large portions of Mirai's source-code and the same file names, Satori uses distinct new propagation methods. Two different exploits embedded within it carry out new infections, and compromised devices download the Satori binary through the original location from which they were first downloaded. This capability means Satori can technically be defined as a worm.

The first exploit targets a zero-day vulnerability in Huawei HG352 routers over port 37215. At present, little is known about this vulnerability but it is believed to allow a remote attacker to execute arbitrary code via HTTP POST requests. The second vector uses an operating system (OS) injection vulnerability in the Realtek software development kit (SDK) miniigd daemon which allows full system access to an unauthorised user. Both methods could potentially open up further, more severe threat vectors.

The speed with which Satori infects new devices makes it highly effective at generating new zombie devices to add to it's botnet, a single compromised device can quickly lead to a fully infected network.

Threat updates

Date	Update
9 Jan 2018	The source code for the Satori botnet has been released on Pastebin. It is expected that new variants of Satori will begin appearing in the next few months.

Remediation advice

To prevent and detect an infection, ensure that:

Remediation steps

Type	Step
	A robust program of education and awareness training is delivered to users to ensure they don’t open attachments or follow links within unsolicited emails. All operating systems, antivirus and other security products are kept up to date. All day to day computer activities such as email and internet are performed using non-administrative accounts. Strong password policies are in place and password reuse is discouraged. Network, proxy and firewall logs should be monitored for suspicious activity. User accounts accessed from infected machines should be reset on a clean computer. Additionally, ports 37125 and 52869 should be monitored and, if not in use, be disabled. Default credentials and security settings on IoT devices (IP cameras, door sensors, etc) should be altered.

Type

Step

A robust program of education and awareness training is delivered to users to ensure they don’t open attachments or follow links within unsolicited emails.
All operating systems, antivirus and other security products are kept up to date.
All day to day computer activities such as email and internet are performed using non-administrative accounts.
Strong password policies are in place and password reuse is discouraged.
Network, proxy and firewall logs should be monitored for suspicious activity.
User accounts accessed from infected machines should be reset on a clean computer.

Additionally, ports 37125 and 52869 should be monitored and, if not in use, be disabled. Default credentials and security settings on IoT devices (IP cameras, door sensors, etc) should be altered.

Last edited: 17 February 2020 11:38 am