Skip to main content
Mallory
Malware

IoT Reaper

Tracked since Aug 14, 2026 · Updated 3 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns0Associated
Actors0Associated
ATT&CK10Techniques
IOCs49Tracked
Type
Botnet
Capabilities
ScanningInitial accessDDOS
Delivery
Exploit kit
Platforms
IOT

IoT Reaper is an IoT botnet first observed in September 2017. It reuses elements of Mirai code but propagates by scanning for and exploiting vulnerabilities in internet-exposed embedded devices rather than by brute-forcing weak credentials. It targeted vulnerable routers, network video recorders, IP cameras, and related IoT products, including devices using D-Link, Netgear, Linksys, AVTECH, Vacron NVR, GoAhead, and JAWS components. The botnet used separated controller, downloader, reporting, and loader functions; infected devices reported potentially vulnerable systems, and loader infrastructure deployed bot payloads to them. IoT Reaper incorporated a Lua execution environment, enabling flexible operator-supplied scripting. Its Lua functionality included support for DDoS activity and embedded DNS resolvers that could facilitate DNS-amplification attacks, although observed operator commands during its early expansion focused on downloading malware and increasing botnet size rather than launching DDoS attacks. Operators rapidly added newly disclosed IoT exploits, and the botnet grew to thousands of simultaneously active compromised devices.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
MITRE ATT&CK

Techniques & procedures

10 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

1 technique
T1190Exploit Public-Facing ApplicationEvidence1

“IoT_reaper infects IoT devices by exploiting multiple IoT device vulnerabilities” and “9 IoT vulnerability exploits have been integrated into current samples.”

Execution

2 techniques
T1059Command and Scripting InterpreterEvidence2

“A LUA execution environment integrated, so more complex attacks can be supported and carried out” and “author will be able to write very complex and efficient attack scripts.”

T1203Exploitation for Client ExecutionEvidence1

IoT_reaper infects IoT devices by exploiting multiple IoT device vulnerabilities. We noticed 9 IoT vulnerability exploits have been integrated into current samples

Stealth

1 technique
T1620Reflective Code LoadingEvidence1

loader : 119.82.26.157, implants bot program through vulnerabilities into devices collected by reporter

Discovery

1 technique
T1046Network Service DiscoveryEvidence1

“Scan behavior is not very aggressive, so it can stay under the radar” and bots collect “potentially vulnerable device info” for the reporter and loader infrastructure.

Command and Control

3 techniques
T1071Application Layer ProtocolEvidence1

downloader : 162.211.183.192, samples can be downloaded from this server... controller : 27.102.101.121, which can control bots, send commands

T1071.001Web ProtocolsEvidence1

The infrastructure includes a “controller” that “can control bots, send commands,” plus HTTP URLs used for sample delivery and Lua-script retrieval.

T1105Ingress Tool TransferEvidence2

“samples can be downloaded from this server” and “The only instructions we saw are to download samples.”

Impact

2 techniques
T1498Network Denial of ServiceEvidence1

The botnet has embedded more than 100 DNS open resolvers in its lua sample, so dns amplification attack can be easily carried out.

T1498.002Reflection AmplificationEvidence1

“The botnet has embedded more than 100 DNS open resolvers in its lua sample, so dns amplification attack can be easily carried out.”

Indicators of compromise

Observables

49 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching49Match every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping10Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.