Threat reportThreat IntelligenceTL-2026-1309
Pro-Iran Hacktivist Ecosystem Uses Telegram to Coordinate DDoS, Hack-and-Leak, and Credential-Theft Campaigns (Handala, 313 Team, Cyber Fattah, Dark Storm, Keymous+, and Affiliated Personas)
DomainTools Investigations documents a decentralized pro-Iran hacktivist ecosystem — including Handala, 313 Team, Cyber Fattah, Fatimiyoun/FAD Team, Dark Storm, CJM, Keymous+, DieNet, and supporting reconnaissance/doxxing cells — coordinating via Telegram channels, shared target lists, and the Beamed DDoS-for-hire platform to conduct high-volume DDoS, hack-and-leak, and credential-theft campaigns against government, critical-infrastructure, finance, and media organizations.
Key facts
| Identifiers | TL-2026-1309 |
|---|---|
| Also known as | Pro-Iran Hacktivist Ecosystem, Axis of Resistance Cyber Ecosystem, Iranian Wartime Hacktivist Coalition |
| Severity | MEDIUM |
| Affected products | Canonical Ubuntu.com / Launchpad / security update APIs; Multiple Government, critical infrastructure, financial services, telecommunications, healthcare, and media sector internet-facing services; Meta/WhatsApp, Telegram FZ-LLC Trojanized/impersonated Telegram and WhatsApp application builds |
| Weaknesses (CWE) | CWE-400, CWE-770, CWE-451 |
| Attribution | VOID MANTICORE - G1055 (medium confidence) |
| Nation-state nexus | Iran |
| Malware | HamsaUpdate |
| Tools | Beamed DDoS-for-hire platform, Telegram Bot API |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1027 Obfuscated Files or Information, T1036.005 Match Legitimate Resource Name or Location, T1041 Exfiltration Over C2 Channel, T1046 Network Service Discovery, T1056.004 Credential API Hooking, T1059 Command and Scripting Interpreter, T1071.001 Web Protocols, T1090.003 Multi-hop Proxy, T1102.002 Bidirectional Communication, T1113 Screen Capture, T1125 Video Capture and 18 more in the attack flow |
| Motivation | HACKTIVISM |
| Target sectors | government administration, critical-infrastructure, financial-services, telecoms, health, news - media, software-supply-chain, open-source-infrastructure |
| Target regions | Middle East, kuwait, israel, jordan, Europe, North America, iraq |
| Detection rules | 9 (1 shown free) |
| Sources | 20 cited sources |
Detection coverage
As of 2026-07-14, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1309 across Splunk SPL, Microsoft KQL and Sigma, covering 16 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: Booter/Stresser DDoS Client Command-Line Invocation (Beamed-style)
Detects local process command-line patterns consistent with a booter/stresser DDoS client launch, matching 313 Team's Beamed-powered campaign against Canonical/Ubuntu infrastructure (--target/--method reflect-amp flags). Fires on process creation telemetry with flood-tool argument signatures.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1583.005, T1498.001, T1498.002
- Data sources: sysmon, windows_security, edr_process_telemetry
- Severity: high
- Confidence: high
Splunk SPL
index=endpoint sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
| where match(CommandLine, "(?i)--target\s+\S+") AND match(CommandLine, "(?i)--method\s+(reflect-amp|flood|udp-flood|syn-flood)")
| eval flood_indicator=if(match(CommandLine, "(?i)--threads\s+\d+"), "high_thread_count", "unknown")
| stats count min(_time) as first_seen max(_time) as last_seen values(CommandLine) as commandlines by Computer, User, Image
| where count > 0
| table Computer, User, Image, commandlines, first_seen, last_seen, flood_indicatorMicrosoft KQL
DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has "--target" and ProcessCommandLine has_any ("reflect-amp", "flood", "udp-flood", "syn-flood")
| where ProcessCommandLine has "--method"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName
| summarize FirstSeen=min(Timestamp), LastSeen=max(Timestamp), Commands=make_set(ProcessCommandLine) by DeviceName, AccountNameSigma
title: Booter/Stresser DDoS Client Command-Line Pattern
id: 7a1e2c44-3b5a-4f7d-9e2a-1c8f6d0b4a11
status: experimental
description: Detects command-line arguments consistent with booter/stresser DDoS client tooling (e.g. Beamed-style flood clients) used by pro-Iran hacktivist ecosystem actors (313 Team, Conquerors Electronic Army).
references:
- https://www.hendryadrian.com/threat-intelligence-report-the-pro-iran-hacktivist-ecosystem-2026/
- https://thehackernews.com/2026/03/149-hacktivist-ddos-attacks-hit-110.html
author: Threadlinqs Team
date: 2026-07-14
tags:
- attack.resource-development
- attack.t1583.005
- attack.impact
- attack.t1498.001
- attack.t1498.002
- attack.tool.beamed_booter
logsource:
product: windows
category: process_creation
detection:
selection:
CommandLine|contains|all:
- '--target'
- '--method'
- 'reflect-amp'
condition: selection
falsepositives:
- Authorized internal load-testing or DDoS-simulation tooling using similar CLI flag naming
level: highKnown false positives:
- Authorized internal DDoS/load-testing tools using similarly-named CLI flags (--target/--method)
Tuning notes: Tune the --method value list to the specific booter families observed in your telemetry (reflect-amp, udp-flood, syn-flood); allowlist known load-testing hosts/service accounts by Computer/DeviceName.
- Masqueraded Telegram/WhatsApp Installer From Non-Official Source · unlock with TL Creds
- External Remote Services Check-In Following Masqueraded Installer Execution · unlock with TL Creds
- Recycled Breach-Data Leak Claim Re-Publication Pattern · unlock with TL Creds
- Telegram Bot API Long-Poll C2 Beaconing from Non-Telegram Process · unlock with TL Creds
- Screen/Video Capture Process Activity Immediately Following Masqueraded Installer · unlock with TL Creds
- Cloud-Storage Exfiltration Following Bot-API C2 Beacon Activity · unlock with TL Creds
- High-Rate Outbound Connection Flood to Single External Destination · unlock with TL Creds
- Unverified 'Proof of Impact' Claim Artifact Pattern ([indicator]-style) · unlock with TL Creds
Indicators of compromise
As of 2026-07-14, Threadlinqs Intelligence tracks 16 indicators of compromise for TL-2026-1309.
Sample indicators (3 of 16)
- Domain:
beamed[.]cc - Domain:
handala-hack[.]tw - Domain:
ubuntu[.]com
Defanged, TLP:CLEAR. Full set of 16 indicators: unlock with TL Creds.
Technical analysis
Researchers assess several of these personas are interchangeable 'skins' operated by Iran's MOIS over shared technical infrastructure.
DomainTools Investigations (DTI) analysts assess that a broad set of pro-Iran and 'Axis of Resistance' hacktivist identities operating on Telegram — Homeland Justice, Karma/KarmaBelow80, and Handala Hack among them — function as a single coordinated cyber-influence ecosystem aligned with Iran's Ministry of Intelligence and Security (MOIS), rather than as distinct grassroots hacktivist groups. These personas are described as interchangeable 'skins' layered over the same technical team, shared infrastructure, and common playbook, allowing Tehran to segment messaging and target sets across audiences while retaining centralized operational control.
The ecosystem's coordination and attack-tooling infrastructure spans Telegram (primary command, claim, and amplification channel), GitHub (tooling/target-list distribution), leak sites, and the commercially available 'Beamed' DDoS-for-hire/booter platform (marketed capability exceeding 3.5 Tbps, aliased in some claims as beamed.cc). Check-host[.]net is used across the ecosystem as a third-party 'proof-of-impact' validation service to lend credibility to DDoS claims.
Named collectives observed operating within this ecosystem include primary disruptors Handala (aka Homeland Justice, Karma/KarmaBelow80, linked to MOIS-attributed cluster Banished Kitten/Storm-0842/Void Manticore/Dune/Red Sandstorm), 313 Team (aka Islamic Cyber Resistance in Iraq), Cyber Fattah, Fatimiyoun/FAD Team, and Dark Storm (Dark Storm Team); secondary/opportunistic operators Keymous+, DieNet, NoName057(16), Killnet, and MONARCH; and enabling-function cells Evil Markhors (reconnaissance and credential harvesting) and Cyber Isnaad Front (doxxing and intimidation). Additional groups observed claiming activity in the same wartime wave include Nation of Saviors, Conquerors Electronic Army (operating under the Cyber Islamic Resistance/CIR umbrella), Sylhet Gang, APT Iran, PalachPro, and Hider Nex/Tunisian Maskers Cyber Force.
The ecosystem is low-sophistication by design: rather than novel intrusion tradecraft, it leans on high-volume/high-visibility DDoS floods, recycled or exaggerated breach data repackaged as new 'leaks,' website defacements, doxxing/identity-exposure campaigns, and propaganda amplification timed to kinetic events (e.g., the 2025-2026 Iran-Israel-US conflict). A representative high-profile action attributed to this ecosystem is the May 2026 DDoS campaign by 313 Team against Canonical/Ubuntu infrastructure: beginning around May 1, 2026, the group used the Beamed booter service against roughly 14 Ubuntu-related domains (ubuntu.com, Launchpad package repositories, and security-update API endpoints), disrupting site availability and package-update functionality. The action was accompanied by a Telegram-posted extortion/ceasefire demand and coincided with Canonical's disclosure of the high-severity 'Copyfail' Linux vulnerability, amplifying reputational impact; X/Twitter subsequently suspended the group's account.
Separately, the FBI (IC3 alert, ref. 260320, published March 23, 2026) documented Iranian state-linked actors — assessed as connected to the Handala persona and broader MOIS-run operations — using Telegram bot infrastructure as command-and-control against political dissidents, opposition figures, and journalists critical of the Iranian regime. The technique involves social-engineering victims (impersonating known contacts or tech support) into installing trojanized apps disguised as legitimate Telegram/WhatsApp builds; once installed, Telegram's own Bot API is abused as a C2 channel to remotely command the implant, exfiltrate files, capture screenshots, and record video calls — blending malicious C2 traffic with legitimate Telegram network traffic to evade detection.
During the February 28-March 5, 2026 hacktivist surge tied to the Iran-Israel-US conflict, 149 DDoS claims were logged against 110 distinct organizations across 16 countries, with Keymous+, DieNet, and NoName057(16) responsible for nearly 70% of claimed activity in the peak Feb 28-Mar 2 window. Targeting concentrated heavily on the Middle East (107 of 149 claims), led by Kuwait (28%), Israel (27.1%), and Jordan (21.5%), with Europe absorbing 22.8% of remaining activity; government entities represented 47.8% of targets, followed by finance (11.9%) and telecommunications (6.7%).
Handala itself (established December 18, 2023, in the weeks following the October 7, 2023 attacks) has a documented history beyond pure DDoS, including the HamsaUpdate wiper deployment (December 2023), high-profile email/data breaches of senior Israeli officials (Ehud Barak, Gadi Eisenkot, Benny Gantz, Naftali Bennett), an alleged Shin Bet personnel-data infiltration (~30,000 records), an alleged 197GB exfiltration from Soreq Nuclear Research Center, a March 2026 attack claim against Stryker Corporation (healthcare device manufacturer, allegedly affecting data tied to 150 million patients), and a claimed compromise of FBI Director Kash Patel's personal email account. US DOJ and FBI attribution places a Handala-linked MOIS unit under identified leadership, including Yahya Hosseini Panjaki, reported killed during the June 2025/2026 Iran war.
Overall, DomainTools and downstream reporting (Cyberpress, SOCRadar, Unit 42, Rapid7, Sophos, Infosecurity Magazine, GBHackers, The Hacker News) characterize this as a durable, reusable wartime cyber-influence apparatus: personas can be spun up, retired, or rebranded quickly, infrastructure (Telegram channels, booter services, leak sites) is shared and recycled across identities, and impact is measured as much in psychological/propaganda terms as in technical damage — while still producing real operational disruption against government, critical-infrastructure, financial, healthcare, and media targets globally.
MITRE ATT&CK techniques by tactic:
Collection
T1005 Data from Local System; T1113 Screen Capture; T1125 Video Capture
Defense Evasion
T1027 Obfuscated Files or Information; T1036.005 Match Legitimate Resource Name or Location
Exfiltration
T1041 Exfiltration Over C2 Channel; T1567.002 Exfiltration to Cloud Storage
Discovery
T1046 Network Service Discovery
Credential Access
T1056.004 Credential API Hooking
Execution
T1059 Command and Scripting Interpreter; T1204.002 Malicious File
Command and Control
T1071.001 Web Protocols; T1090.003 Multi-hop Proxy; T1102.002 Bidirectional Communication
Initial Access
T1133 External Remote Services; T1566.002 Spearphishing Link
Impact
T1485 Data Destruction; T1491.002 External Defacement; T1498.001 Direct Network Flood; T1498.002 Reflection Amplification; T1499.004 Application or System Exploitation; T1565.002 Transmitted Data Manipulation
Persistence
Resource Development
T1583.005 Botnet; T1584.006 Web Services; T1585.001 Social Media Accounts; T1587.001 Malware
Reconnaissance
T1589.001 Credentials; T1593.002 Search Engines
reconnaissance
Remediation
Patches
- Apply vendor patches promptly during hacktivist-exploited disclosure windows (e.g., Canonical's high-severity 'Copyfail' Linux vulnerability disclosed concurrently with the May 2026 DDoS campaign) to prevent opportunistic pivoting from disruption to exploitation.
Immediate actions
- Enable and tune DDoS scrubbing/CDN protection (rate limiting, anycast, upstream scrubbing) for internet-facing web, package-repository, and API endpoints ahead of anticipated wartime escalation windows.
- Block or throttle known booter/stresser infrastructure (e.g., beamed.cc and associated DDoS-for-hire endpoints) at perimeter and CDN layers.
- Monitor Telegram Bot API traffic patterns (recurring polling to api.telegram.org from unexpected endpoints/processes) as a potential C2 indicator.
- Alert on installation of Telegram/WhatsApp application binaries from non-official sources; verify code-signing and distribution channel for messaging-app installers.
- Flag and triage 'proof of impact' claims validated only via check-host[.]net as unverified until independently confirmed.
- Brief communications/PR and executive-protection teams on hack-and-leak/extortion patterns (Telegram-posted ceasefire/extortion demands) to avoid amplifying unverified claims.
Workarounds
- Where scrubbing capacity is insufficient, implement geofencing/rate-limiting biased against traffic surges correlated with regional conflict escalation events.
- Maintain out-of-band/mirrored update-distribution channels for critical software repositories to preserve availability during sustained DDoS against primary infrastructure.
Longer-term hardening
- Deploy behavioral EDR/NDR detection for messaging-app-disguised C2 (screenshot capture, video-call recording, remote-command execution triggered via chat-bot commands).
- Establish DDoS incident-response runbooks with pre-negotiated scrubbing-provider failover for public-facing infrastructure, especially package/update-distribution systems.
- Maintain a recurring-breach-data watchlist: correlate newly claimed 'leaks' against previously known breach corpora to rapidly identify recycled/exaggerated data.
- Track hacktivist Telegram channel churn (persona rebranding, channel bans/reinstatement) as an ecosystem-tracking signal rather than treating each named group as fully independent.
- Extend executive and staff digital-protective-intelligence monitoring to cover doxxing/identity-exposure campaigns from Evil Markhors/Cyber Isnaad Front-style enabling cells.
Affected and fixed versions
- Canonical — Ubuntu.com / Launchpad / security update APIs
Vulnerable versions: public-facing web and package-distribution infrastructure, May 2026
Fixed in: N/A - availability incident, not a code vulnerability - Multiple — Government, critical infrastructure, financial services, telecommunications, healthcare, and media sector internet-facing services
Vulnerable versions: Internet-exposed web applications and services lacking DDoS mitigation, primarily in Middle East (Kuwait, Israel, Jordan) and Europe
Fixed in: N/A - Meta/WhatsApp, Telegram FZ-LLC — Trojanized/impersonated Telegram and WhatsApp application builds
Vulnerable versions: unofficial/sideloaded builds distributed to political dissidents, opposition figures, and journalists
Fixed in: official app-store builds with verified signing
Timeline
- Handala-linked HamsaUpdate wiper malware deployed against Israeli targets.
- Handala Hack persona established on Telegram and X in the weeks following the October 7, 2023 attacks.
- Hider Nex/Tunisian Maskers Cyber Force launches the first DDoS attack of the Feb 28-Mar 5, 2026 hacktivist surge tied to the Iran-Israel-US conflict.
- Keymous+, DieNet, and NoName057(16) drive nearly 70% of claimed DDoS activity during the Feb 28-Mar 2 peak window; total reaches 149 claims against 110 organizations in 16 countries by March 5.
- FBI/IC3 publishes advisory 260320 documenting Iranian state-linked actors (assessed connection to Handala/MOIS) using Telegram Bot API C2 against dissidents, opposition figures, and journalists via trojanized Telegram/WhatsApp builds.
- 313 Team (Islamic Cyber Resistance in Iraq) launches a Beamed-powered DDoS campaign against ~14 Ubuntu-related domains including locked-ioc-2 and Launchpad, disrupting Canonical infrastructure; extortion/ceasefire demand posted via Telegram.
- Canonical confirms the DDoS disruption; the incident coincides with disclosure of the high-severity 'Copyfail' Linux vulnerability; X/Twitter later suspends 313 Team's account.
- DomainTools Investigations publishes analysis characterizing Handala, Homeland Justice, and Karma/KarmaBelow80 as interchangeable MOIS-operated 'skins' over shared infrastructure and tooling.
- Cyber Security News reports on the broader pro-Iran hacktivist ecosystem's continued use of Telegram, shared target lists, DDoS-for-hire tooling, and leak-amplification campaigns against government, infrastructure, finance, and media targets.
Sources cited
Showing 15 of 20 sources, primary sources first.
- Government of Iran Cyber Actors Deploy Telegram C2 to Target Dissidents, Journalists (IC3 Advisory 260320) ic3.gov · Advisory · 2026-03-23
- Threat Intelligence Report: The Pro-Iran Hacktivist Ecosystem 2026 (DomainTools Investigations summary) hendryadrian.com · Research · 2026-07-01
- Handala Hack Team - Wikipedia en.wikipedia.org · Research · 2026-07-01
- Dark Web Profile: Mr Hamza socradar.io · Research · 2026-05-01
- Threat Brief: Escalation of Cyber Risk Related to Iran (Updated April 17) Unit 42 · Vendor report · 2026-04-17
- Iran's Cyber Playbook in the Escalating Regional Conflict Rapid7 · Vendor report · 2026-03-01
- How hacktivist cyber operations surged amid Israeli-Iranian conflict outpost24.com · Vendor report · 2026-04-01
- Hacktivist campaigns increase as United States, Iran, and Israel conflict intensifies Sophos · Vendor report · 2026-03-15
- The Digital Front of Iranian Cyber Offensive and Defensive Response extrahop.com · Vendor report · 2026-04-05
- Iran's Digital Proxy Army Turns DDoS Attacks and Data Leaks Into Wartime Psychological Weapons cyberpress.org · Blog · 2026-06-15
- Ubuntu Hit by DDoS Attack: Pro-Iran 313 Team Claims Responsibility thecybrdef.com · Blog · 2026-05-02
- Telegram Hacktivist Activity Timeline of Iran - Israel & US War socradar.io · Blog · 2026-04-01
- Monitoring Cyberattacks Directly Linked to the US-Israel-Iran Military Conflict flare.io · Blog · 2026-04-01
- FBI says Iranian hackers are using Telegram to steal data in malware attacks techcrunch.com · News · 2026-03-23
- 149 Hacktivist DDoS Attacks Hit 110 Organizations in 16 Countries After Middle East Conflict The Hacker News · News · 2026-03-06
More from VOID MANTICORE - G1055
Previous and next in threat intel
Drafted by the Threadlinqs research pipeline from 20 sources; published ; last updated —.