Between February and April 2026, the Iran-nexus Advanced Persistent Threat (APT) group Screening Serpens (also known as UNC1549 and Smoke Sandstorm) launched a series of sophisticated cyberespionage campaigns. The attacks targeted high-value entities in the technology, aerospace, and defense sectors across the United States, Israel, and the United Arab Emirates. Unit 42 researchers observed a significant evolution in the group's tactics, techniques, and procedures (TTPs), highlighted by the use of AppDomainManager hijacking to disable security controls in .NET applications. The group deployed six new Remote Access Trojan (RAT) variants, categorized into two new malware families named MiniUpdate and MiniJunk V2, demonstrating a continuous cycle of development and operational refinement.
The campaigns, occurring from mid-February through April 2026, coincide with the timing of a regional conflict that began on February 28, 2026. Screening Serpens has maintained a high operational tempo, leveraging targeted social engineering as its primary initial access vector. The group impersonates trusted brands and hiring platforms, sending personalized recruitment lures to professionals in their target sectors.
The infection chain typically begins with a malicious archive file (e.g., Hiring Portal.zip) containing a payload that uses T1574.002 - DLL Sideloading for execution. A key innovation is the use of AppDomainManager hijacking, a technique that manipulates the initialization of .NET applications to disable their security features, allowing the RATs to operate unimpeded. The actor routes command and control (C2) traffic through a set of unique, target-specific domains, many hosted on Azure, to enhance operational resilience and avoid cross-contamination between campaigns.
Screening Serpens's recent operations showcase a marked increase in technical sophistication. The core of their new toolkit consists of two malware families, MiniUpdate and MiniJunk V2.
The most critical evolution is the group's use of AppDomainManager hijacking. This technique involves modifying a legitimate .NET application's configuration file (.config). By adding specific XML tags (<appDomainManagerAssembly> and <appDomainManagerType>), the attacker can force the .NET Common Language Runtime (CLR) to load a malicious assembly during the application's startup process. This malicious assembly can then programmatically disable security features like Antimalware Scan Interface (AMSI), effectively blinding endpoint security products before the main application code even runs.
UpdateChecker.dll, this family was deployed in two coordinated waves against targets in the U.S., Israel, and the UAE. Analysis shows continuous refinement, with later variants including features like the ability to exfiltrate files in chunks. The primary infection vector was an archive file delivered via spear phishing.Both families establish persistence and communicate with C2 servers over standard web protocols (T1071.001 - Web Protocols). The C2 domains are dedicated per target and variant, demonstrating a high degree of operational planning to hinder detection and attribution.
The primary objective of these campaigns is cyberespionage, aligned with the strategic interests of the Iranian government. By targeting aerospace, defense manufacturing, and telecommunications organizations, Screening Serpens seeks to acquire sensitive intellectual property, defense secrets, and other confidential information. The compromise of professionals within these high-value sectors can lead to long-term strategic losses for the affected nations and companies. The use of advanced defense evasion techniques like AppDomainManager hijacking indicates that the group is capable of bypassing standard security controls, increasing the likelihood of a successful and prolonged intrusion.
Hiring Portal.zipUpdateChecker.dllThe source article did not provide specific hash values, IP addresses, or C2 domains.
Security teams may want to hunt for the following patterns to detect activity related to this threat:
*.exe.config<appDomainManagerAssembly>.config files for the presence of this XML element, which is used to specify the malicious assembly for AppDomainManager hijacking.MSBuild.exeMSBuild.exe spawning suspicious child processes or making outbound network connections, as it can be abused to execute malicious code.InstallUtil.exe, MSBuild.exe) spawning unusual child processes like cmd.exe or powershell.exe..exe.config files, particularly the addition of the appDomainManager configuration elements. This can be achieved with File Integrity Monitoring (FIM).Process Analysis to baseline normal process behavior and detect anomalies.4688 (Process Creation) with command-line logging enabled, to hunt for suspicious execution chains.UpdateChecker.dll or similar variants outside of their expected application directories.M1017): Educate employees, especially those in high-value roles, to recognize and report sophisticated spear phishing and social engineering attempts, particularly those involving job offers.M1038): Implement application allowlisting solutions to prevent the execution of unauthorized executables and DLLs. This can directly counter the DLL sideloading technique.M1028): Enforce policies to restrict modifications to sensitive files, including application .config files in Program Files. Use file integrity monitoring to alert on unauthorized changes.M1030): Segment the network to limit lateral movement and restrict outbound C2 traffic. Egress filtering should be used to block connections to known malicious or untrusted destinations.Training users to recognize and report phishing attempts is crucial, as social engineering is the primary initial access vector for this threat actor.
Implementing application allowlisting can prevent the execution of malicious DLLs and executables dropped by the attacker.
Enable detailed logging and auditing of file modifications (especially for .config files) and process creation to detect TTPs like AppDomainManager hijacking.
Mapped D3FEND Techniques:
Segmenting the network can contain the threat actor's movement and limit the blast radius of an intrusion.
Mapped D3FEND Techniques:
A MiniJunk V2 family sample was uploaded, marking the start of the observed campaign preparations.
A regional conflict started in the Middle East, aligning with the timing of the APT campaigns.
A MiniUpdate family sample was uploaded, potentially targeting entities in the U.S. and Israel.
Another MiniJunk V2 family sample was uploaded.
A MiniUpdate family sample was uploaded, potentially targeting an entity in the UAE.
A MiniUpdate family sample was uploaded, potentially targeting another Middle Eastern entity.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.