<p>The last time Iranian cyber operators went quiet before a major geopolitical escalation, a major Saudi oil and gas company lost 35,000 workstations in a single afternoon. That was Shamoon, 2012.</p>
<p>Six Iranian advanced persistent threat (APT) groups with confirmed targeting of Saudi banks are being actively updated across threat intelligence platforms — and none of them are generating public-attack reporting. Meanwhile, hacktivist groups are getting louder, botnet operators are recruiting Saudi devices, and fresh command-and-control infrastructure is lighting up on the Kingdom's largest telecom network.</p>
<p>If you're a CISO in Saudi financial services, the next 14 days may define your year.</p>
<p>This post breaks down what our analysts are seeing, what it means, and exactly what you should do about it — starting today.</p>
<h2>What Changed</h2>
<p>Three developments in the last 72 hours have converged to create a threat environment we haven't seen since the Shamoon era:</p>
<ol> <li>Geopolitical trigger. US-Israeli military strikes killed Ayatollah Khamenei in late February. Six independent sources — USA Today, American Banker, Bloomberg Law, Forbes, Nextgov, and SecurityWeek — confirm that financial services globally are bracing for Iranian retaliatory cyberattacks. Saudi Arabia, as a US/Israel-aligned Gulf state with deep historical Iranian enmity, is a primary target.</li> <li>Hacktivist escalation to Gulf energy targets. The Iranian-aligned hacktivist group Handala— responsible for 132 attacks since April 2024 — claimed breaches of major oil and gas companies in Saudi Arabia on March 3. This represents a geographic expansion from their primary focus on Israel (44% of victims) into Gulf state critical infrastructure for the first time at this tempo.</li> <li>Active malicious infrastructure on Saudi networks. On March 4, our analysts identified three NetSupportManager RAT command-and-control servers, three fresh Mirai botnet infections, and three high-confidence malicious IPs tied to a Saudi-registered financial entity— all active on telecom and hosting infrastructure. Nine new indicators of compromise in a single day.</li>
</ol>
<p>The most concerning signal, however, is what we did not see.</p>
<h2>Threat Timeline</h2>
<table dir="ltr"><colgroup><col width="200" /><col width="787" /><col width="185" /></colgroup>
<tbody> <tr> <td>Date</td> <td>Event</td> <td>Severity</td> </tr> <tr> <td>Late Feb 2026</td> <td>US-Israeli strikes kill Iran's supreme leader</td> <td>🔴 Geopolitical trigger</td> </tr> <tr> <td>Feb 1 – Mar 4</td> <td>Three NetSupportManager RAT C2 servers stood up on a major Saudi telco provider (ASN 25019)</td> <td>🟠 Active C2 infrastructure</td> </tr> <tr> <td>Mar 3</td> <td>CISA adds CVE-2026-22719 (VMware Aria Operations RCE, CVSS 8.1) to Known Exploited Vulnerabilities catalog</td> <td>🟠 Active exploitation</td> </tr> <tr> <td>Mar 3</td> <td>SecurityWeek reports hacktivist activity spiking; state-sponsored actors "staying low"</td> <td>🔴 Pre-positioning indicator</td> </tr> <tr> <td>Mar 3</td> <td>Handala claims breaches on two major oil and gas companies</td> <td>🟠 Gulf targeting escalation</td> </tr> <tr> <td>Mar 3</td> <td>Google patches CVE-2026-21385 (Qualcomm Android zero-day, actively exploited) — 129 vulnerabilities in March Android update</td> <td>🟡 Mobile banking risk</td> </tr> <tr> <td>Mar 4</td> <td>Three fresh Mirai infections detected on a major telco’s residential IPs — identical binary, automated propagation</td> <td>🟠 Botnet recruitment</td> </tr> <tr> <td>Mar 4</td> <td>Two high-confidence malicious IPs traced to "Global Financial Digital Solution Company JSC" (Saudi-registered, ASN 61073) + Fesber trojan on a major video conferencing company’s infrastructure</td> <td> <div> <div>🟡 Financial infrastructure compromise</div> </div> </td> </tr>
</tbody>
</table>
<h2>The Iranian Threat: Two Layers, One Strategy</h2>
<h3>Layer 1: The Noise — Hacktivists</h3>
<p>Handala, DieNet, Team 313, Liwa Thar Allah, Fad Team, Cyb3rDrag0nzz, and Fynix are all active and generating headlines. Handala alone has claimed 132 victims and operates a dedicated leak site hosted behind DDoS-Guard. Their March 3 claim about an oil and gas company — alleging the "entire infrastructure dismantled" — is almost certainly exaggerated. Multiple sources note that Iranian-linked hackers have consistently overstated their success.</p>
<p>But the noise serves a purpose. It consumes SOC attention, generates media coverage, and creates a fog that obscures what's happening underneath.</p>
<h3>Layer 2: The Silence — State-Sponsored APTs</h3>
<p>Our analysts searched specifically for recent reporting on Iranian state-sponsored operations against Saudi Arabia — APT34(OilRig/Helix Kitten/Hazel Sandstorm), MuddyWater (Mango Sandstorm/Cobalt Ulster), APT35 (Charming Kitten/Mint Sandstorm), Pioneer Kitten(Lemon Sandstorm), and TEMP.Zagros (Seedworm/Static Kitten). The result: zero public reporting.</p>
<p>This is not reassuring. It is alarming.</p>
<p>Of the Iranian groups we identified in our [<a href="https://www.anomali.com/blog/irans-cyber-retaliation-clock-is-ticking-what-cisos-need-to-know-right-now">March 3 assessment</a>], some have been updated in threat intelligence platforms within the last 72 hours — all with confirmed financial services targeting. APT34's known target set explicitly includes well-known banks, payments companies and oil and gas companies in the region. Their profiles were updated in threat intelligence platforms within the last 72 hours. Their known tradecraft — spear-phishing with credential harvesting, DNS tunneling, web shell deployment, and tools like the Karkoff backdoor and SideTwist — is well-documented.</p>
<p>The historical pattern is clear: state-sponsored actors go quiet before major operations to avoid burning access. Shamoon had minimal precursor reporting in open sources. The current silence, combined with the most significant geopolitical trigger in a generation, should be treated as a pre-positioning indicator until proven otherwise.</p>
<h2>Active Threats on Saudi Infrastructure</h2>
<h3>NetSupportManager RAT — Command and Control Inside the Kingdom</h3>
<p>Three validated C2 servers running NetSupportManager RAT were identified on a Saudi telecom provider’s infrastructure (ASN 25019):</p>
<table dir="ltr"><colgroup><col width="116" /><col width="32" /><col width="200" /></colgroup>
<tbody> <tr> <td>Indicator</td> <td>Port</td> <td>First Seen</td> </tr> <tr> <td>`167.86.142.38`</td> <td>443</td> <td>Feb 1, 2026</td> </tr> <tr> <td>`130.164.164.220`</td> <td>443</td> <td>Feb 19, 2026</td> </tr> <tr> <td>`143.92.169.237`</td> <td>443</td> <td>Mar 4, 2026</td> </tr>
</tbody>
</table>
<p>NetSupportManager is a legitimate remote administration tool that has been extensively weaponized by threat actors including FIN6 and TA569 (Mustard Tempest). It is commonly delivered through ClickFix social engineering— fake browser update prompts and malvertising — and provides persistent remote access once installed.</p>
<p>The concentration of three C2 servers on a Saudi telecom provider’s infrastructure within a 30-day window suggests either compromised Saudi hosts being used as relay points, or deliberate staging of C2 inside the Kingdom to blend with legitimate banking traffic.</p>
<p>What to look for on endpoints:`client32.exe`, `NSM.LIC`, and `GatewayDefaultSite.ini` in `%APPDATA%` and startup folders.</p>
<h3>Mirai Botnet — Recruiting Saudi Devices</h3>
<p>Three Saudi IPs were detected hosting an identical Mirai malware binary (SHA256: `0d4602f60008115e617026ad78ac0abbd9516f98610f8bd3374c66630d31e17f`), geolocated to southwestern Saudi Arabia, the Medina area, and Jeddah:</p>
<table dir="ltr"><colgroup><col width="94" /><col width="200" /><col width="200" /></colgroup>
<tbody> <tr> <td>Indicator</td> <td>Location</td> <td>Network</td> </tr> <tr> <td>`87.76.72.42`</td> <td>SW Saudi Arabia</td> <td>ASN 25019</td> </tr> <tr> <td>`77.30.17.75`</td> <td>Medina area</td> <td>ASN 25019</td> </tr> <tr> <td>`84.235.33.82`</td> <td>Jeddah area</td> <td>ASN 25019</td> </tr>
</tbody>
</table>
<p>The identical binary across all three hosts indicates automated propagation — a botnet in active recruitment mode. The Aisiru and Kimwolf variants of Mirai have been documented shifting from direct DDoS attacks to operating as residential proxy networks, building capacity that can be rented to other threat actors — including nation-states seeking to obscure their infrastructure.</p>
<p>This is not a theoretical concern. A growing pool of compromised Saudi residential IPs provides ideal cover for targeted operations against Saudi banks: the traffic originates from local IP ranges that are difficult to block without impacting legitimate customers.</p>
<h3>Fesber Trojan and Suspicious Financial Infrastructure</h3>
<p>Two high-confidence malicious IPs (`185.183.99.113` and `185.183.99.103`) were traced to an entity registered as "Global Financial Digital Solution Company JSC" on ASN 61073. A third IP (`159.124.249.106`), registered to a video communications provider’s infrastructure in Saudi Arabia, was tagged with the Fesber trojan — a worm capable of modifying the Windows registry, establishing persistence through Winlogon Helper DLLs, and performing system location discovery.</p>
<p>Whether "Global Financial Digital Solution Company JSC" is a compromised legitimate fintech or a front entity requires investigation, but two high-confidence malware indicators registered to a financial services company in the Kingdom demands immediate attention.</p>
<h2>Vulnerabilities Under Active Exploitation</h2>
<h3>CVE-2026-22719 — VMware Aria Operations (CVSS 8.1)</h3>
<p>A command injection vulnerability in VMware Aria Operations that allows unauthenticated remote code execution during support-assisted product migration. CISA added it to the Known Exploited Vulnerabilities catalog on March 3. Both Bleeping Computer and SecurityWeek independently confirmed active exploitation in the wild.</p>
<p>VMware Aria Operations is widely deployed across Saudi enterprise environments as part of ongoing IT modernization programs. If your organization runs it, this is a patch-now situation.</p>
<h3>CVE-2026-21385 — Qualcomm Android Zero-Day</h3>
<p>An integer overflow in Qualcomm's Graphics subcomponent, confirmed exploited in targeted attacks with possible ties to commercial spyware or nation-state threat groups. Google's March 2026 Android update patches this along with 128 other vulnerabilities.</p>
<p>For organizations with mobile banking applications — which is effectively every Saudi bank — this vulnerability creates a direct path to compromising customer and employee devices.</p>
<h2>Predictive Assessment: What Comes Next</h2>
<p>Based on the convergence of geopolitical triggers, observed infrastructure activity, and historical patterns, our analysts assess the following probabilities over the coming 30 days:</p>
<table dir="ltr"><colgroup><col width="981" /><col width="70" /><col width="69" /><col width="406" /></colgroup>
<tbody> <tr> <td>Scenario</td> <td>Timeframe</td> <td>Probability</td> <td>Impact</td> </tr> <tr> <td>Iranian hacktivist groups (Handala, DieNet, Team 313) conduct DDoS or defacement attacks against Saudi financial sector websites</td> <td>7 days</td> <td>70%</td> <td>Moderate — reputational, temporary service disruption</td> </tr> <tr> <td>Iranian state-sponsored actors (APT34, MuddyWater) launch targeted spear-phishing campaigns against Saudi banking employees, using the conflict as lure content</td> <td>14 days</td> <td>40%</td> <td>High — potential credential theft, initial access</td> </tr> <tr> <td>Aisiru/Kimwolf botnet capacity is contracted for DDoS-for-hire attack against a Saudi bank</td> <td>30 days</td> <td>25%</td> <td>Moderate-High — sustained volumetric attack using local IPs</td> </tr> <tr> <td>Destructive wiper attack (Shamoon-style) against Saudi financial infrastructure</td> <td>30 days</td> <td>15%</td> <td>Catastrophic — potential for data destruction, operational shutdown</td> </tr>
</tbody>
</table>
<p>The 15% wiper scenario deserves special attention. Low probability does not mean low priority when the impact is existential. Shamoon destroyed 35,000 workstations at a major oil and gas company. A similar attack against a major Saudi bank's core systems during a period of record lending growth and $1B sukuk issuances would have consequences far beyond IT.</p>
<h2>Defense Recommendations</h2>
<h3>Immediate — Next 48 Hours</h3>
<table dir="ltr"><colgroup><col width="49" /><col width="1254" /><col width="213" /></colgroup>
<tbody> <tr> <td align="center">Priority</td> <td>Action</td> <td>Owner</td> </tr> <tr> <td align="center">1</td> <td>Elevate SOC monitoring posture for Iranian TTPs: spear-phishing with credential harvesting themes related to the Iran conflict, DNS tunneling to uncommon TLDs, web shell deployment on internet-facing servers. Specifically watch for APT34 tooling signatures (Karkoff backdoor, SideTwist, VALUEVAULT).</td> <td>SOC / Threat Hunting</td> </tr> <tr> <td align="center">2</td> <td>Patch VMware Aria Operations against CVE-2026-22719. If immediate patching is not possible, apply the vendor workaround from VMSA-2026-0001 and restrict network access to the management interface.</td> <td>Infrastructure / Patch Management</td> </tr> <tr> <td align="center">3</td> <td>Scan for NetSupportManager RAT artifacts across endpoints: `client32.exe`, `NSM.LIC`, `GatewayDefaultSite.ini` in user profile directories and startup folders. Any hit indicates active compromise.</td> <td>Endpoint Security / Threat Hunting</td> </tr> <tr> <td align="center">4</td> <td>Scan IoT and edge devices for the Mirai binary hash `a1718cb582cf05bf5dec74f2fdcff522`. Compromised devices on your network perimeter can be leveraged as pivot points.</td> <td>Network Operations / OT Security</td> </tr>
</tbody>
</table>
<h3>7-Day Actions</h3>
<table dir="ltr"><colgroup><col width="49" /><col width="1529" /><col width="243" /></colgroup>
<tbody> <tr> <td align="center">Priority</td> <td>Action</td> <td>Owner</td> </tr> <tr> <td align="center">5</td> <td>Deploy the March 2026 Android security update across all corporate-managed mobile devices. CVE-2026-21385 is actively exploited and directly relevant to mobile banking applications.</td> <td>Mobile Device Management</td> </tr> <tr> <td align="center">6</td> <td>Hunt for the ClickFix-to-RAT kill chain. Our analysis indicates a plausible attack sequence: compromised residential IPs (Aisiru/Kimwolf botnet) deliver AI-generated social engineering lures (fake browser updates, malvertising) that install NetSupportManager RAT for persistent access. Search web proxy logs for anomalous browser update redirects and correlate with any NetSupportManager network signatures.</td> <td>Threat Hunting / SOC</td> </tr> <tr> <td align="center">7</td> <td>Review DDoS mitigation readiness. Confirm Cloudflare/Akamai configurations can absorb volumetric attacks from local Saudi IP ranges (stc Saudi ASN 25019). Traditional geo-blocking will not work when the botnet traffic originates from within the Kingdom.</td> <td>Network Security / Vendor Management</td> </tr>
</tbody>
</table>
<h3>30-Day Actions</h3>
<table dir="ltr"><colgroup><col width="49" /><col width="1825" /></colgroup>
<tbody> <tr> <td align="center">Priority</td> <td>Action</td> </tr> <tr> <td align="center">8</td> <td>Conduct a tabletop exercise for an Iranian destructive attack scenario. Model a Shamoon-style wiper targeting core banking systems during peak transaction hours. Include scenarios where the wiper is delivered through a compromised supply chain partner (e.g., shared infrastructure with Aramco or Saudi Payments/mada network). The state-actor silence pattern makes this exercise urgent, not theoretical.</td> </tr> <tr> <td align="center">9</td> <td>Investigate "Global Financial Digital Solution Company JSC" (ASN 61073). Two high-confidence malware indicators are registered to this entity. Determine whether it is a legitimate Saudi fintech that has been compromised, or a front organization. If your institution has any business relationship with this entity, treat it as a potential supply chain compromise.</td> </tr> <tr> <td align="center">10</td> <td>Review and harden all internet-facing infrastructure against the specific vulnerability classes being exploited: command injection (CVE-2026-22719), remote access tool abuse (NetSupportManager), and mobile platform vulnerabilities (CVE-2026-21385). Prioritize assets connected to SWIFT, mada payment network, and core banking platforms.</td> </tr> <tr> <td align="center">11</td> <td>Establish or reinforce threat intelligence sharing with peer institutions through SAMA's financial sector ISAC and Saudi CERT. The hacktivist groups targeting major oil and gas companies today will target banks tomorrow. Shared IOCs and TTP signatures across the sector multiply defensive coverage.</td> </tr>
</tbody>
</table>
<h2>The Bottom Line</h2>
<p>The convergence of three factors — a regime-decapitation event in Iran, active malicious infrastructure on Saudi networks, and the deliberate silence of six state-sponsored APT groups with confirmed Saudi bank targeting — creates the most dangerous cyber threat window for the Kingdom's financial sector since Shamoon.</p>
<p>The hacktivist noise is the distraction. The state-actor silence is the threat. The nine new indicators of compromise identified today are the evidence that the battlefield is being prepared.</p>
<p>The organizations that will weather this period are the ones acting now: blocking the C2 servers, scanning for NetSupportManager RAT artifacts, patching VMware and Android, and — critically — not allowing the Handala headlines to distract from the disciplined, patient work of threat hunting for APT34 and MuddyWater footholds that may already exist in their networks.</p>
<p>The historical pattern is clear. After Shamoon, the organizations that recovered fastest were those that had validated their backups, rehearsed their response plans, and understood their exposure before the wiper landed. You have that window right now. It will not stay open for long.</p>