Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
🇳🇿 NZ

Rondo

Also known asrondo

rondo, also referred to in the provided content as the RondoDox botnet, is a threat actor/botnet observed conducting multi-phase exploitation activity. The content describes it as more sophisticated than typical commodity botnet noise, using fileless exploitation, rotating command-and-control or staging infrastructure, and appearing to operate through compromised residential routers. Activity was observed as early as May 2 and unfolded in three phases. In Phase 1, RondoDox used source IP 124.198.131.185 and staging server 45.92.1.50 while targeting enterprise and AI-related services. The content states it attempted exploitation of Log4Shell (CVE-2021-44228) and used obfuscated payloads in the User-Agent and multiple HTTP headers as a header-spray technique. It also targeted the /api/jobs/ endpoint in attacks associated with ShadowRay, identified in the content as CVE-2023-48022. In Phase 2, it retained the same source IP but shifted staging infrastructure to 204.10.194.134 between May 16 and May 17. During this phase, it targeted consumer-router vulnerabilities including LB-LINK command injection at /goform/set_LimitClient_cfg (CVE-2023-26801) and ASUS AsusWRT NVRAM manipulation via /vpnupload.cgi (CVE-2018-6000). In Phase 3, the source IP changed from 124.198.131.185 to 124.198.131.22, which the source assessed as a DHCP lease change within the same residential IP pool in Auckland, New Zealand. Separately, VulnCheck observed CVE-2023-7305, a SmartBI RMIServlet unrestricted file upload vulnerability that can lead to RCE, being targeted by the Rondo botnet. Based strictly on the provided content, known alias: RondoDox.

Share:
Are they targeting you?

Know when an actor pivots toward your sector

Mallory correlates actor tradecraft and target patterns against your stack, your sector, and your geography. See overlap before they land.

OPERATIONAL PROFILE

Targeting

Who, where, and (when attributed) which flag flies behind the operation. Pulled from open-source reporting and Mallory's analyst review.

Who they target

Sectors the actor has been observed targeting.

  • Software & Services

Where they're from

Attributed origin per open-source reporting.

  • NZ
MITRE ATT&CK

Tradecraft

7 distinct techniques observed across reporting, grouped by tactic. Hover any cell for the evidence excerpt; click through for MITRE's full description.

5 of 15 tactics8 techniques×N= number of intelligence reports citing this technique
MITRE ATT&CK
TA0001
Initial Access
1 technique
T1190
Exploit Public-Facing Application
TA0002
Execution
2 techniques
T1059
Command and Scripting Interpreter
T1059.004
Unix Shell
T1203
Exploitation for Client Execution
TA0005
Stealth
2 techniques
T1036
Masquerading
T1620
Reflective Code Loading
TA0007
Discovery
1 technique
T1046
Network Service Discovery
TA0011
Command and Control
1 technique
T1105
Ingress Tool Transfer
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: sector and geo overlap with your footprint, the IOCs they’re burning right now, detection coverage, and what to do next.
Target overlap

Match sector + geo + tech-stack targeting against your real footprint.

Tradecraft mapping7

Every observed MITRE ATT&CK technique, grouped by tactic.

Malware arsenal

Families this actor is known to deploy, with IOCs and behavior.

Exploited CVEs

CVEs this actor has used in known campaigns.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Observables

Domains, IPs, and hashes tied to this actor, refreshed continuously.