Threat feed

Prince of Persia / Infy

Prince of Persia (Infy): Iranian APT reboots after war lull — Tornado second stage found on US shared hosting, Telegram-bot exfiltration, DGA domains with RSA-locked C2

Posted · Updated · Spectrum Delta Research Team

Summary

Semperis (Tomer Bar, AVP of Security Research, Oct 22, A/2) documents the current state of Prince of Persia (aka Infy), an Iranian nation-state-sponsored espionage group active for nearly two decades against Iranian dissidents and public and private organizations in the US, Europe and the Middle East. When the US–Iran conflict began on February 28, 2026, the group went dark for three months — the longest downtime in its history — then rebuilt: operations restarted May 27, 2026 with a new C2 bank. This research explicitly covers the group's actions since SafeBreach's February 4, 2026 report (same researcher, then at SafeBreach): the C2 server 45.80.148.249 was shut down within a week of that publication and victim GUIDs were purged from the long-standing updatelist.txt management file. The newly located Tornado second-stage C2 — missing from the public picture since September 2025 — runs on US Namecheap shared hosting managed with cPanel, which the primary describes as the group's first US-hosted server in a decade; a further server was rebuilt behind Cloudflare on August 24, 2026, which Semperis suspects followed the actor realizing its newest server had been discovered. The current families use DGA-generated domains alongside non-DGA domains (both appear in the published IOC sets), and incoming C2 requests are authenticated with RSA signature validation, which Semperis describes as locking out security researchers and automated scanners — Tonnerre's anti-takeover signatures are described as preventing sinkholing, the matured counter to Unit 42's 2016 sinkhole of the group's Infy-era C2 (documented in Unit 42's own follow-up research). Exfiltration runs through a Telegram bot: the Tornado second-stage C2 hosts a tga.adr file, obtainable by specific victims, containing the Telegram bot API key used to exfiltrate victim files to a Telegram group chat controlled by the actor — the API key and chat ID live in the C2 backend configuration rather than the malware (the file was unavailable at publication, and Semperis suspects the actor changed its filename). Tornado, the newest family (version 51), builds on the Foudre/Tonnerre codebase, can be delivered through one-day software vulnerabilities (WinRAR exploits cited), and can decode fields hidden in blockchain transactions to change C2 routing without updating malware on victims. Observed campaign activity: in the first week after the May 27 restart, Tonnerre exfiltrated more than 1,800 files from one victim; an August 2026 victim was still active; Semperis monitored the exfiltration for six months and describes a low victim count that could indicate either targeted attacks or difficulty infecting new victims.

Breakdown

Adversary

Prince of Persia

Procedures (3)

  1. First-stage C2 beacons resolve DGA-rotated family domains

    C2: first-stage beacons to DGA-rotated family domains

    • T1568.002Dynamic Resolution: Domain Generation Algorithms

    Logs

    • Microsoft DNS server query logs · resolver queries for published C2 domains; family-domain rotation over time
    • Enterprise web proxy · C2 IP connections; inspected-URL Telegram Bot API requests; tga.adr fetch

    Detectors

    No known detector

Click to expand remaining (2) procedures
  1. Foudre downloads and launches Tonnerre

    Staged escalation: Foudre downloads and launches Tonnerre

    • T1105Ingress Tool Transfer

    Logs

    • Enterprise web proxy · C2 IP connections; inspected-URL Telegram Bot API requests; tga.adr fetch
    • Endpoint process telemetry · Tonnerre binary execution after C2 fetch; Foudre capability context

    Detectors

    No known detector

  2. Malware issues Telegram Bot API requests

    Exfiltration channel: malware issues Telegram Bot API requests

    Logs

    • Enterprise web proxy · C2 IP connections; inspected-URL Telegram Bot API requests; tga.adr fetch

    Detectors

    No known detector

Indicators of compromise

Hunt only

(Semperis (https://www.semperis.com/blog/prince-of-persia-threat-group-hiding-in-plain-sight/), A/2) — recent C2 with source-reported dates: 185.244.129.70 (May–Aug 2026, HOSTGW SRL, Cyber Panel 8090), 185.244.129.123 (since Sept 1, 2026), 68.65.122.203 (Tornado second stage, July 2026, Namecheap US shared hosting, cPanel), 162.159.24.80 (Aug 24, 2026, Cloudflare-fronted — shared infrastructure). Restart exfil host: aa58862c.ddns.net. Representative exact domains (complete per-family lists in the primary): nnahinsmqs.site, xleergjemlwm.hbmc.net, jqkctsldgwkbw.privatedns.org, olbkdmwhacbfc.privatedns.org, f21.ddnsking.com, c0596f41.site, t21.ddnsking.com, roounvuq.space, mksrnosw.privatedns.org, aa58862c.ddns.net. Legacy ranges abandoned: 45.80.148.0/24, 45.80.149.0/24, 45.80.151.0/24. tga.adr artifact (Telegram bot API key; rename suspected). Exfil filename format L<YY><MM><DD><HH><MM><SS><VICTIM IP zeroed>. Assessed 2026-10-26, hunt-only — the C2 bank is perishable (the February-era server was replaced within a week of that publication and the newest was rebuilt behind Cloudflare after suspected discovery); the durable hunt keys are the published domain families in DNS and Telegram Bot API request shapes in inspected proxy URLs.

Detailed

Recent C2 (source-reported dates): 185.244.129.70 (May–August 2026, HOSTGW SRL, AS204641, Cyber Panel on 8090; Tornado first-stage, Tonnerre, Foudre); 185.244.129.123 (since September 1, 2026, same provider, same families); 68.65.122.203 (Tornado second stage, since July 2026, Namecheap shared hosting, AS22612, cPanel, US soil — the primary's first-US-hosting-in-a-decade finding); 162.159.24.80 (Tornado second stage, since August 24, 2026 — shared Cloudflare infrastructure, AS13335, not actor-exclusive). Restart exfil host: aa58862c.ddns.net. Representative exact current-family domains (complete per-family lists are in the primary): Tornado first stage — nnahinsmqs.site, xleergjemlwm.hbmc.net (on .70), ouqqdplfgurg.hbmc.net (on .123); Tornado second stage — jqkctsldgwkbw.privatedns.org, kxzsfydnivzmv.privatedns.org (on 68.65.122.203), olbkdmwhacbfc.privatedns.org (on 162.159.24.80); Tonnerre v17 — f21.ddnsking.com (non-DGA), c0596f41.site, oqunspyr.privatedns.org (on .70), mksrnosw.privatedns.org (on .123); Foudre v34+ — t21.ddnsking.com (non-DGA), roounvuq.space, kmrpopwt.space (on .70); legacy Tonnerre v12-/Foudre v33- — aa58862c.ddns.net, df1908e3.ddns.net, 417d9d40.ddns.net (complete legacy list in the primary). Abandoned historical ranges: 45.80.148.0/24, 45.80.149.0/24, 45.80.151.0/24; 45.80.148.249 (shut down within a week of the February 4 publication); 45.80.148.194 (active February 9, 2026). Second-stage artifact: tga.adr (Telegram bot API key file; unavailable at publication, filename change suspected). Exfil filename format: L<YY><MM><DD><HH><MM><SS><VICTIM IP zeroed>. DGA generation input example: 26623G3 (<YY><M><WEEK NUMBER><G><3>) — a date-derived seed, not domain text. All from the primary (Semperis (https://www.semperis.com/blog/prince-of-persia-threat-group-hiding-in-plain-sight/), A/2).

Sources

Questions, detections or sightings of Prince of Persia / Infy? Bring them to the community.

Discuss in the Tradecraft Slack