All Posts
Anomali Cyber Watch
1
min read

Iran’s Cyber War Machine Doesn’t Need the Internet to Attack You

Published on
April 6, 2026
Table of Contents
<p><strong>What 37 Days of Conflict Intelligence Reveals About Iranian Operations &mdash; and Why Your Defenses May Already Be Bypassed</strong></p> <p><strong>Threat Assessment Level: HIGH &mdash; ESCALATING</strong></p> <p><em>Continuity note: This assessment maintains the HIGH &mdash; ESCALATING level from the prior cycle (2026-04-05). No change in threat level; new evidence reinforces the escalatory trajectory.</em></p> <h2><strong>Introduction&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</strong></h2> <p>Thirty-seven days into the US-Israeli military conflict with Iran, a single intelligence finding should reshape how every CISO thinks about Iranian cyber threats: <strong>HAYWIRE KITTEN &mdash; the IRGC-affiliated group also known as Emennet Pasargad and NEPTUNIUM &mdash; conducted offensive phishing operations through Iran&rsquo;s own nationwide internet blackout.</strong></p> <p>Let that sink in. Iran imposed a domestic internet blackout in early March 2026, and its offensive cyber units kept operating without interruption. If your incident response plans assume that kinetic strikes on Iranian infrastructure, sanctions on Iranian ISPs, or any form of network disruption will slow down Iranian cyber operations &mdash; those plans are wrong.</p> <p>Meanwhile, the ransomware ecosystem that Iranian intelligence services use as operational cover just gained the ability to kill over 300 endpoint detection and response (EDR) products. Three new ICS/OT vulnerabilities dropped for systems deployed across energy grids and petrochemical plants. And a critical gap in defense industrial base monitoring has gone 28 days without a single detection &mdash; during the most active phase of the conflict.</p> <p>This is not a theoretical threat landscape. This is the operational reality as of today.</p> <h2><strong>What Changed&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</strong></h2> <p>The past 48 hours produced five developments that shift the defensive calculus:</p> <ol> <li><strong>HAYWIRE KITTEN confirmed operating through Iran&rsquo;s internet blackout</strong> &mdash; launching phishing campaigns via WhatsApp, Telegram, and X (formerly Twitter) targeting the Iranian diaspora and individuals involved in Iran-related activities abroad. This invalidates any assumption that domestic infrastructure disruption degrades Iranian offensive capability.</li> <li><strong>Qilin ransomware operators deployed a Bring Your Own Vulnerable Driver (BYOVD) technique</strong> capable of disabling 300+ EDR products. Qilin is part of the documented MOIS-to-ransomware handoff ecosystem, meaning this EDR-killing capability is now potentially available to Iranian state actors operating under criminal cover.</li> <li><strong>Three ICS/OT advisories published simultaneously</strong> &mdash; affecting Siemens SICAM A8000 (energy grid substations), Yokogawa CENTUM VP (oil/gas and petrochemical distributed control systems), and Hitachi Energy Ellipse (utility asset management). All three platforms are deployed in sectors directly targeted by Iranian proxy cyber operations.</li> <li><strong>Defense industrial base monitoring has been silent for 28 consecutive days</strong> &mdash; the longest gap during the active conflict. This is either reassuring or deeply alarming, and the asymmetry of consequences demands proactive investigation.</li> <li><strong>Critical unauthenticated RCE vulnerabilities published for Ivanti EPMM</strong> (CVE-2026-1281 and CVE-2026-1340, CVSS 9.8) &mdash; edge devices matching the preferred initial-access profile of Iranian APTs including MuddyWater and APT34. Emergency patching is required.</li> <li><strong>DPRK supply chain actors expanding npm campaign to Axios (45M+ weekly downloads)</strong> &mdash; the same npm ecosystem used by Iranian actors for supply chain attacks, creating a compounding multi-nation-state risk for CI/CD pipelines.</li> </ol> <h2><strong>Conflict &amp; Threat Timeline&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</strong></h2> <table> <thead> <tr> <th> <p>Date</p> </th> <th> <p>Event</p> </th> <th> <p>Significance</p> </th> </tr> </thead> <tbody> <tr> <td> <p>28 Feb 2026</p> </td> <td> <p>US-Israeli military conflict with Iran begins</p> </td> <td> <p>Day 0 &mdash; kinetic and cyber operations commence</p> </td> </tr> <tr> <td> <p>Early Mar 2026</p> </td> <td> <p>Iran imposes nationwide internet blackout</p> </td> <td> <p>Domestic internet severed; offensive cyber ops continue unaffected</p> </td> </tr> <tr> <td> <p>Early Mar 2026</p> </td> <td> <p>HAYWIRE KITTEN launches WhatsApp/Telegram/X phishing campaign</p> </td> <td> <p>Confirmed operations through blackout &mdash; targets Iranian diaspora</p> </td> </tr> <tr> <td> <p>01 Apr 2026</p> </td> <td> <p>IRGC declares five US tech companies &ldquo;legitimate targets&rdquo;</p> </td> <td> <p>Nvidia, Apple, Google, Microsoft, Tesla explicitly named</p> </td> </tr> <tr> <td> <p>02 Apr 2026</p> </td> <td> <p>CISA publishes three ICS advisories (Siemens, Yokogawa, Hitachi)</p> </td> <td> <p>Expands OT attack surface for Iranian proxy operations</p> </td> </tr> <tr> <td> <p>03 Apr 2026</p> </td> <td> <p>F-15E shot down over southern Iran</p> </td> <td> <p>First US aircraft combat loss since 2003; 48-hour rescue operation</p> </td> </tr> <tr> <td> <p>04 Apr 2026</p> </td> <td> <p>UNC1549/Imperial Kitten profile updated &mdash; no new campaign data</p> </td> <td> <p>Anomalous silence from aerospace/energy-targeting actor</p> </td> </tr> <tr> <td> <p>05 Apr 2026</p> </td> <td> <p>36 malicious npm packages targeting Redis/PostgreSQL discovered</p> </td> <td> <p>Supply chain attack surface expanding across nation-state actors</p> </td> </tr> <tr> <td> <p>05 Apr 2026</p> </td> <td> <p>Trump ultimatum pressure on Iran over Strait of Hormuz blockade</p> </td> <td> <p>Escalatory diplomatic pressure increases cyber retaliation risk</p> </td> </tr> <tr> <td> <p>06 Apr 2026</p> </td> <td> <p>Qilin ransomware BYOVD EDR-kill capability reported</p> </td> <td> <p>300+ EDR products vulnerable; capability available to MOIS-RaaS ecosystem</p> </td> </tr> </tbody> </table> <h2><strong>Key Threat Analysis&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</strong></h2> <h3><strong>1. Iranian Offensive Cyber Operations Are Infrastructure-Independent</strong></h3> <p><strong>Actor:</strong> HAYWIRE KITTEN (aliases: Emennet Pasargad, NEPTUNIUM, Holy Souls, Black Magic, Sangkancil, Generous Thief, Atlas Group, Deus, Al-Toufan, Hackers of Savior)</p> <p><strong>Affiliation:</strong> IRGC &mdash; linked to Emennet Pasargad front company; EU-sanctioned</p> <p>The confirmation that HAYWIRE KITTEN operated through Iran&rsquo;s nationwide internet blackout is the single most strategically significant finding of this cycle. The group used WhatsApp, Telegram, and X to deliver phishing lures to individuals involved in Iran-related activities living abroad &mdash; a classic intelligence collection operation using social media platforms as both delivery mechanism and command-and-control channel.</p> <p>This has three implications for defenders:</p> <ul> <li><strong>Scenario planning must assume continuous Iranian cyber capability.</strong> Any playbook that models reduced threat tempo during infrastructure disruption, ceasefire negotiations, or sanctions enforcement is now empirically invalidated.</li> <li><strong>Social media platforms are the C2 channel.</strong> HAYWIRE KITTEN&rsquo;s use of Telegram for bidirectional communication (ATT&amp;CK T1102.002) means that blocking traditional C2 infrastructure at the network perimeter is insufficient. Detection must extend to anomalous social media API activity on corporate devices.</li> <li><strong>The diaspora targeting will expand.</strong> Organizations employing individuals with connections to Iran, the broader Middle East conflict, or defense/intelligence communities should expect targeted social engineering via personal messaging platforms.</li> </ul> <p>The group&rsquo;s known tooling includes Deus ransomware, Rpivot, WezAgent, and LoreamIpsumBackdoor, with historical exploitation of CVE-2021-36260 (Hikvision) and CVE-2021-33044 (Dahua) for IoT camera compromise.</p> <h3><strong>2. The MOIS-Ransomware Pipeline Now Kills Your EDR</strong></h3> <p><strong>Actors:</strong> MOIS-affiliated groups (MuddyWater/TEMP.Zagros, OilRig/APT34, UNC1860) leveraging Qilin and Warlock ransomware-as-a-service</p> <p><strong>Technique:</strong> BYOVD (Bring Your Own Vulnerable Driver) &mdash; ATT&amp;CK T1068, T1562.001, T1574.001</p> <p>Qilin and Warlock ransomware operators are now deploying a BYOVD technique that disables over 300 EDR products by loading a malicious DLL (msimg32.dll) via DLL sideloading. This was independently confirmed by both Cisco Talos and Trend Micro.</p> <p>Why this matters for the Iran conflict: Iranian intelligence services &mdash; specifically MOIS &mdash; have a documented pattern of handing off access to criminal ransomware operators. This provides plausible deniability while achieving destructive objectives. With Qilin now capable of neutralizing endpoint detection before deploying ransomware, the combined state-criminal threat becomes significantly harder to detect and contain.</p> <p><strong>The defensive implication is stark:</strong> Organizations that rely solely on EDR as their primary detection layer are now vulnerable to a technique that is confirmed in the wild and available to state-sponsored operators through the ransomware-as-a-service ecosystem.</p> <h3><strong>3. ICS/OT Attack Surface Expanding at the Worst Possible Time</strong></h3> <p><strong>Advisories:</strong> - <strong>ICSA-26-092-01:</strong> Siemens SICAM A8000 &mdash; denial of service vulnerabilities in energy grid substation equipment - <strong>ICSA-26-092-02:</strong> Yokogawa CENTUM VP &mdash; authentication bypass allowing attacker to login as PROG user and modify permissions in oil/gas distributed control systems - <strong>ICSA-26-092-03:</strong> Hitachi Energy Ellipse &mdash; Jasper Report vulnerability in utility enterprise asset management</p> <p><strong>Threat actor of concern:</strong> Cyber Av3ngers (aliases: HYDRO KITTEN, IRGC Cyber Electronic Command)</p> <p>Cyber Av3ngers have demonstrated both willingness and capability to target ICS/OT environments, including Unitronics PLCs and water treatment systems. The simultaneous publication of three advisories affecting platforms deployed across energy, oil/gas, and utility sectors creates a predictable exploitation window. Historical patterns show 7&ndash;21 days from ICS advisory publication to weaponized exploitation by Iranian-affiliated actors.</p> <p>The Yokogawa CENTUM VP vulnerability is particularly concerning &mdash; a PROG user login bypass in a distributed control system used in petrochemical and power generation facilities could enable an attacker to manipulate process controls (ATT&amp;CK T0890, T0826).</p> <h3><strong>4. Critical Vulnerabilities Requiring Immediate Attention</strong></h3> <p><strong>CVE-2026-1281 and CVE-2026-1340 &mdash; Ivanti Endpoint Manager Mobile (EPMM)</strong> - <strong>CVSS:</strong> 9.8 (Critical) - <strong>Impact:</strong> Unauthenticated remote code execution - <strong>Status:</strong> Patches available; no confirmed exploitation yet, but Ivanti edge devices are a historically preferred target for Iranian APTs (per documented APT34 and MuddyWater tradecraft)</p> <p><strong>CVE-2026-20127 &mdash; Cisco SD-WAN</strong> - Enriched this cycle; affects edge networking infrastructure commonly deployed in enterprise and government environments</p> <p>Iranian threat actors &mdash; particularly MuddyWater and APT34 &mdash; have a well-documented preference for exploiting internet-facing edge devices and VPN appliances as initial access vectors. Any unpatched Ivanti EPMM instance exposed to the internet should be treated as a critical risk.</p> <h3><strong>5. Supply Chain Convergence: When North Korea and Iran Target the Same Ecosystem</strong></h3> <p>A parallel but intersecting threat: DPRK actors are expanding their Node.js supply chain campaign to target maintainers of widely-used npm packages, including Axios (45M+ weekly downloads). While this is a North Korean operation, it directly threatens the same npm ecosystem that Iranian actors have used for supply chain attacks.</p> <p>The convergence creates a compounding risk: a single compromised npm package could serve multiple nation-state threat actor ecosystems simultaneously. Organizations with CI/CD pipelines pulling from npm should treat this as a shared attack surface across threat actors.</p> <h2><strong>The 28-Day Silence That Should Keep You Up at Night</strong></h2> <p>One finding in this cycle isn&rsquo;t a detection &mdash; it&rsquo;s an absence. Monitoring for Iranian pre-positioning in defense industrial base (DIB) contractor networks has produced zero findings for 28 consecutive days, the longest gap since the conflict began.</p> <p>During the most active phase of a military conflict where Iran has every incentive to pre-position destructive capabilities in adversary supply chains, complete silence is not reassuring &mdash; it&rsquo;s ambiguous. The possibilities are:</p> <ul> <li><strong>Best case:</strong> No activity is occurring.</li> <li><strong>Worst case:</strong> Pre-positioned access has been established and is dormant, evading passive detection.</li> <li><strong>Middle case:</strong> Collection gaps in DIB-specific threat feeds are creating a blind spot.</li> </ul> <p>The asymmetry of consequences &mdash; a missed detection in DIB networks could compromise weapons systems, logistics, or classified programs &mdash; demands proactive hunting rather than continued passive monitoring.</p> <h2><strong>Predictive Analysis: What Comes Next</strong></h2> <p>Based on the current intelligence picture, actor behavior patterns, and conflict dynamics at Day 37:</p> <table> <thead> <tr> <th> <p>Scenario</p> </th> <th> <p>Probability</p> </th> <th> <p>Timeframe</p> </th> <th> <p>Basis</p> </th> </tr> </thead> <tbody> <tr> <td> <p>HAYWIRE KITTEN phishing yields follow-on intrusions against diaspora-connected organizations</p> </td> <td> <p><strong>70%</strong></p> </td> <td> <p>7&ndash;14 days</p> </td> <td> <p>Confirmed active phishing campaign; intelligence collection typically precedes operational intrusion</p> </td> </tr> <tr> <td> <p>Cyber Av3ngers or affiliates attempt exploitation of Yokogawa CENTUM VP or Siemens SICAM</p> </td> <td> <p><strong>60%</strong></p> </td> <td> <p>14 days</p> </td> <td> <p>Historical 7&ndash;21 day advisory-to-exploitation pattern; platforms match actor targeting profile</p> </td> </tr> <tr> <td> <p>Qilin BYOVD EDR-kill technique appears in an Iran-attributed intrusion</p> </td> <td> <p><strong>50%</strong></p> </td> <td> <p>30 days</p> </td> <td> <p>MOIS-RaaS convergence documented; capability now confirmed in the wild</p> </td> </tr> <tr> <td> <p>UNC1549/Imperial Kitten breaks silence with campaign against Gulf state energy or aerospace</p> </td> <td> <p><strong>40%</strong></p> </td> <td> <p>14&ndash;21 days</p> </td> <td> <p>Actor profile updated but no new campaigns; anomalous silence for an actor with this targeting profile during active conflict</p> </td> </tr> <tr> <td> <p>Iranian actors exploit CVE-2026-1281 or CVE-2026-1340 (Ivanti EPMM) against government targets</p> </td> <td> <p><strong>55%</strong></p> </td> <td> <p>7&ndash;14 days</p> </td> <td> <p>CVSS 9.8, unauthenticated RCE, edge device &mdash; matches Iranian APT preferred access vector</p> </td> </tr> </tbody> </table> <h2><strong>SOC Operational Guidance&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</strong></h2> <h3><strong>What to Monitor</strong></h3> <table> <thead> <tr> <th> <p>Focus Area</p> </th> <th> <p>ATT&amp;CK Techniques</p> </th> <th> <p>Detection Logic</p> </th> </tr> </thead> <tbody> <tr> <td> <p>Iranian C2 communications</p> </td> <td> <p>T1071.001 (Web Protocols), T1571 (Non-Standard Port)</p> </td> <td> <p>Alert on any traffic to ASN 43754 (Asiatech) and ASN 213790 (Limited Network, Tehran). Block IOCs listed below at perimeter.</p> </td> </tr> <tr> <td> <p>Social media C2 channels</p> </td> <td> <p>T1102.002 (Bidirectional Communication)</p> </td> <td> <p>Monitor for anomalous Telegram Bot API calls, WhatsApp Web sessions, and X/Twitter API activity from corporate endpoints &mdash; especially from users with Iran-related roles.</p> </td> </tr> <tr> <td> <p>DLL sideloading / BYOVD</p> </td> <td> <p>T1574.001 (DLL Search Order Hijacking), T1562.001 (Disable or Modify Tools), T1068 (Exploitation for Privilege Escalation)</p> </td> <td> <p>Alert on msimg32.dll loaded from any path outside %SystemRoot%\System32. Monitor for EDR agent crashes or service stops across multiple endpoints simultaneously.</p> </td> </tr> <tr> <td> <p>Spearphishing via messaging platforms</p> </td> <td> <p>T1566.001 (Spearphishing Attachment), T1566.002 (Spearphishing Link), T1585.001 (Social Media Accounts)</p> </td> <td> <p>Flag inbound links from unknown Telegram bots to MDM-enrolled devices. Correlate with HR data for personnel in Iran-adjacent roles.</p> </td> </tr> <tr> <td> <p>ICS/OT exploitation attempts</p> </td> <td> <p>T0890 (Exploitation for Evasion), T0816 (Device Restart/Shutdown), T0826 (Loss of Availability)</p> </td> <td> <p>Monitor Yokogawa CENTUM VP for unauthorized PROG user logins. Alert on Siemens SICAM A8000 unexpected restarts. Baseline Hitachi Ellipse Jasper Report access patterns.</p> </td> </tr> <tr> <td> <p>Edge device exploitation</p> </td> <td> <p>T1190 (Exploit Public-Facing Application)</p> </td> <td> <p>Prioritize log review for Ivanti EPMM, Cisco SD-WAN, and Fortinet appliances. Hunt for webshell artifacts and anomalous admin sessions.</p> </td> </tr> </tbody> </table> <h3><strong>Hunting Hypotheses</strong></h3> <ol> <li><strong>Hypothesis: HAYWIRE KITTEN has already compromised accounts via social media phishing.</strong> Hunt for: new OAuth app registrations in Microsoft 365/Entra ID from unfamiliar publishers; Telegram Desktop or WhatsApp Desktop installed on corporate endpoints without MDM approval; email forwarding rules created in the past 30 days pointing to external addresses.</li> <li><strong>Hypothesis: Qilin BYOVD loader has been staged in the environment.</strong> Hunt for: msimg32.dll in user-writable directories (%TEMP%, %APPDATA%, Downloads); recently loaded kernel drivers not on your approved driver allowlist; EDR telemetry gaps &mdash; endpoints that stopped reporting within the last 7 days.</li> <li><strong>Hypothesis: Iranian pre-positioned access exists in development infrastructure.</strong> Hunt for: dormant SSH keys or PATs in GitHub Enterprise created &gt;30 days ago with no recent activity; Rclone or Wasabi S3 client installations on developer workstations; anomalous access to Windchill PLM repositories outside business hours.</li> <li><strong>Hypothesis: ICS/OT reconnaissance is underway against energy sector assets.</strong> Hunt for: Shodan/Censys-style scanning patterns against Yokogawa and Siemens management interfaces; MAVLink protocol traffic on unexpected network segments (relevant to PX4 autopilot vulnerability ICSA-26-090-02); unauthorized PROG user authentication attempts on CENTUM VP systems.</li> </ol> <h3><strong>Defensive Gaps to Close</strong></h3> <ul> <li><strong>EDR is no longer sufficient as a standalone detection layer.</strong> The Qilin BYOVD capability means you need defense-in-depth: network detection (NDR), kernel-level integrity monitoring, and driver allowlisting (Windows Defender Application Control / WDAC) as complementary layers.</li> <li><strong>Social media-based C2 bypasses traditional network monitoring.</strong> If your SOC only monitors DNS and HTTP/S traffic, Telegram and WhatsApp C2 channels will evade detection. Extend monitoring to application-layer telemetry on endpoints.</li> <li><strong>ICS/OT environments need advisory-driven patching cycles.</strong> The 7&ndash;21 day window between ICS advisory publication and weaponized exploitation is your patching window. Treat it as a countdown.</li> </ul> <h2><strong>Sector-Specific Defensive Priorities</strong></h2> <h3><strong>Financial Services</strong></h3> <p>Iranian cyber operations increasingly use ransomware-as-a-service (Qilin, Pay2Key) as cover for destructive attacks against financial institutions. The BYOVD EDR-kill capability makes this more dangerous.</p> <ul> <li><strong>Priority:</strong> Implement driver allowlisting (WDAC) on critical financial transaction servers to prevent BYOVD attacks. Audit SWIFT and core banking system access for dormant service accounts. Monitor for DLL sideloading patterns (msimg32.dll) on trading floor endpoints.</li> <li><strong>Threat actor focus:</strong> MuddyWater (MOIS/TEMP.Zagros), MOIS-RaaS operators using Qilin</li> </ul> <h3><strong>Energy</strong></h3> <p>The three simultaneous ICS advisories (Siemens SICAM, Yokogawa CENTUM VP, Hitachi Energy Ellipse) directly affect energy sector control systems. Cyber Av3ngers have demonstrated ICS targeting capability and intent.</p> <ul> <li><strong>Priority:</strong> Immediately audit Yokogawa CENTUM VP PROG user access controls. Verify Siemens SICAM A8000 firmware versions and apply patches per ICSA-26-092-01. Segment Hitachi Ellipse Jasper Report interfaces from internet-facing networks. Conduct tabletop exercise for ICS compromise scenario within 14 days.</li> <li><strong>Threat actor focus:</strong> Cyber Av3ngers (HYDRO KITTEN / IRGC-CEC), UNC1860</li> </ul> <h3><strong>Healthcare</strong></h3> <p>Healthcare organizations are collateral targets in ransomware campaigns and may be specifically targeted for intelligence value (military medical records, personnel health data for diaspora targeting).</p> <ul> <li><strong>Priority:</strong> Ensure EDR agents are monitored for unexpected service stops (BYOVD indicator). Patch Ivanti EPMM instances used for mobile device management of clinical staff &mdash; CVE-2026-1281 and CVE-2026-1340 are unauthenticated RCE at CVSS 9.8. Review Telegram and WhatsApp usage policies for staff with dual-use personal/corporate devices.</li> <li><strong>Threat actor focus:</strong> Qilin RaaS operators, HAYWIRE KITTEN (social engineering vector)</li> </ul> <h3><strong>Government</strong></h3> <p>Government networks are the primary target of the CISA -flagged Asiatech infrastructure. The Iranian C2 IPs identified this cycle are assessed with high confidence to be targeting government entities.</p> <ul> <li><strong>Priority:</strong> Audit Entra ID / Azure AD for anomalous OAuth application consents and new service principals. Hunt for Rclone, Wasabi, or other cloud exfiltration tools. Review VPN and edge device logs (Ivanti, Cisco SD-WAN, Fortinet) for exploitation indicators.</li> <li><strong>Threat actor focus:</strong> APT34 (OilRig), APT42 (Charming Kitten / IRGC-IO), MuddyWater (MOIS)</li> </ul> <h3><strong>Aviation / Logistics</strong></h3> <p>UNC1549 (Imperial Kitten / Smoke Sandstorm / TA455) specifically targets aerospace and defense sectors in the US, Saudi Arabia, and UAE. Their anomalous silence during active conflict is concerning, not reassuring. The PX4 Autopilot MAVLink vulnerability (ICSA-26-090-02) introduces a new drone firmware attack surface.</p> <ul> <li><strong>Priority:</strong> Proactively hunt for UNC1549 indicators in aerospace supply chain networks &mdash; focus on Azure and DigitalOcean infrastructure. Audit drone fleet management systems for MAVLink interface exposure. Review GitHub and CI/CD pipelines for npm supply chain compromise indicators (Axios and related packages).</li> <li><strong>Threat actor focus:</strong> UNC1549 (Imperial Kitten), DPRK supply chain actors (npm ecosystem convergence)</li> </ul> <h2><strong>Prioritized Defense Recommendations</strong></h2> <h3><strong>IMMEDIATE (Within 24 Hours)</strong></h3> <table> <thead> <tr> <th> <p>Priority</p> </th> <th> <p>Team</p> </th> <th> <p>Action</p> </th> </tr> </thead> <tbody> <tr> <td> <p>IMMEDIATE</p> </td> <td> <p>SOC</p> </td> <td> <p>Deploy Sigma/YARA detection for msimg32.dll loaded from non-standard paths (outside %SystemRoot%\System32). Alert on simultaneous EDR agent service stops across multiple endpoints &mdash; this is the signature of BYOVD deployment.</p> </td> </tr> <tr> <td> <p>IMMEDIATE</p> </td> <td> <p>SOC</p> </td> <td> <p>Implement detection for Telegram Bot API and WhatsApp Web connections from corporate/MDM-enrolled devices, particularly for users in roles related to Iran, Middle East policy, defense, or intelligence.</p> </td> </tr> <tr> <td> <p>IMMEDIATE</p> </td> <td> <p>IT Ops</p> </td> <td> <p>Verify no Ivanti EPMM instances are internet-exposed without WAF protection. Begin emergency patching for CVE-2026-1281 and CVE-2026-1340 (CVSS 9.8, unauthenticated RCE).</p> </td> </tr> </tbody> </table> <h3><strong>7-DAY</strong></h3> <table> <thead> <tr> <th> <p>Priority</p> </th> <th> <p>Team</p> </th> <th> <p>Action</p> </th> </tr> </thead> <tbody> <tr> <td> <p>7-DAY</p> </td> <td> <p>IT Ops</p> </td> <td> <p>Complete Ivanti EPMM patching across all instances. Validate Cisco SD-WAN configurations against CVE-2026-20127.</p> </td> </tr> <tr> <td> <p>7-DAY</p> </td> <td> <p>OT Security</p> </td> <td> <p>Audit Yokogawa CENTUM VP for unauthorized PROG user access per ICSA-26-092-02. Verify Siemens SICAM A8000 firmware versions against ICSA-26-092-01. Restrict Hitachi Energy Ellipse Jasper Report to internal-only access per ICSA-26-092-03.</p> </td> </tr> <tr> <td> <p>7-DAY</p> </td> <td> <p>SOC</p> </td> <td> <p>Implement WhatsApp/Telegram/X phishing detection for personnel in Iran-adjacent roles. Create correlation rules for new OAuth app registrations + email forwarding rule creation within 24-hour windows.</p> </td> </tr> <tr> <td> <p>7-DAY</p> </td> <td> <p>IT Security</p> </td> <td> <p>Deploy Windows Defender Application Control (WDAC) driver allowlisting on critical servers to mitigate BYOVD attacks. Prioritize domain controllers, financial transaction servers, and backup infrastructure.</p> </td> </tr> <tr> <td> <p>7-DAY</p> </td> <td> <p>Executive / IR</p> </td> <td> <p>Conduct tabletop exercise: &ldquo;Iranian wiper deployment via ransomware cover&rdquo; scenario. Test IR playbook for simultaneous EDR failure + ransomware detonation. Validate offline backup restoration procedures.</p> </td> </tr> </tbody> </table> <h3><strong>30-DAY</strong></h3> <table> <thead> <tr> <th> <p>Priority</p> </th> <th> <p>Team</p> </th> <th> <p>Action</p> </th> </tr> </thead> <tbody> <tr> <td> <p>30-DAY</p> </td> <td> <p>CISO</p> </td> <td> <p>Commission proactive threat hunt for dormant Iranian pre-positioned access in DIB contractor networks. Focus areas: GitHub Enterprise repos, Windchill PLM instances, CI/CD pipelines, and Rclone/Wasabi exfiltration patterns. The 28-day detection gap during active conflict is the highest-consequence blind spot.</p> </td> </tr> <tr> <td> <p>30-DAY</p> </td> <td> <p>DevOps</p> </td> <td> <p>Audit all npm dependencies for packages targeted by DPRK supply chain campaign (Axios and related). Pin critical packages to commit SHAs. Implement npm provenance verification across all CI/CD pipelines.</p> </td> </tr> <tr> <td> <p>30-DAY</p> </td> <td> <p>CISO</p> </td> <td> <p>Evaluate network detection and response (NDR) deployment to complement EDR &mdash; the BYOVD EDR-kill capability means endpoint detection alone is no longer sufficient as a primary detection strategy.</p> </td> </tr> <tr> <td> <p>30-DAY</p> </td> <td> <p>CISO</p> </td> <td> <p>Review and update Iran conflict cyber incident response plan. Ensure it accounts for: (a) operations continuing through infrastructure disruption, (b) ransomware used as cover for state-directed destruction, (c) social media platforms as C2 channels, and (d) ICS/OT targeting with compressed advisory-to-exploitation timelines.</p> </td> </tr> <tr> <td> <p>30-DAY</p> </td> <td> <p>Legal / Executive</p> </td> <td> <p>Review cyber insurance coverage for state-sponsored attacks conducted through criminal ransomware infrastructure. The MOIS-RaaS convergence blurs the line between &ldquo;act of war&rdquo; exclusions and criminal cybercrime coverage.</p> </td> </tr> </tbody> </table> <h2><strong>Bottom Line&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;</strong></h2> <p>Five weeks into this conflict, the intelligence picture is clear on what assumptions no longer hold:</p> <p><strong>❌ &ldquo;Iranian cyber operations will slow down if their internet is disrupted.&rdquo;</strong> Disproven. HAYWIRE KITTEN operated through a nationwide blackout.</p> <p><strong>❌ &ldquo;EDR will catch the ransomware.&rdquo;</strong> Challenged. Qilin&rsquo;s BYOVD technique kills 300+ EDR products before the payload ever executes.</p> <p><strong>❌ &ldquo;We&rsquo;d see pre-positioning activity in our logs.&rdquo;</strong> Unverified. 28 days of silence in DIB networks during active conflict is not evidence of absence &mdash; it may be absence of evidence.</p> <p><strong>❌ &ldquo;ICS/OT attacks require sophisticated, custom tooling.&rdquo;</strong> Outdated. Three new advisories in a single day provide off-the-shelf exploitation paths for systems deployed across energy, oil/gas, and utilities.</p> <p><strong>❌ &ldquo;Nation-state threats and criminal ransomware are separate problems.&rdquo;</strong> Obsolete. The MOIS-to-Qilin pipeline means you face state targeting precision with criminal evasion capability.</p> <p>The organizations that will weather this conflict are the ones acting on intelligence today &mdash; not waiting for the breach notification tomorrow. Block the IOCs. Hunt for the pre-positioning. Patch the edge devices. And above all, stop assuming that any single layer of defense is enough when your adversary has already figured out how to bypass it.</p>

FEATURED RESOURCES

April 6, 2026
Anomali Cyber Watch

Iran’s Cyber War Machine Doesn’t Need the Internet to Attack You

Read More
April 6, 2026
Public Sector
Anomali Cyber Watch

When Your Identity Platform Becomes the Front Door: Critical Threats Facing State Government IT

Read More
April 3, 2026
Anomali Cyber Watch

Iran’s IRGC Names Western Tech Giants as “Legitimate Targets”: What CISOs Must Do Now

Read More
Explore All