The threat actor Storm-0249, previously known primarily as an Initial Access Broker (IAB) that sold network access to other cybercrime groups, is evolving its tactics to become a more direct participant in malware and ransomware deployment. Research from ReliaQuest shows the group adopting more sophisticated and stealthy techniques, including DLL side-loading and fileless execution. This marks a significant shift from their previous business model of simply finding and selling access, to now being a hands-on enabler of the final payload. The group's updated TTPs, which involve social engineering via the "ClickFix" method and abusing legitimate security software for defense evasion, indicate a move towards higher-tier operations and a deeper integration with ransomware affiliates.
Storm-0249 is transitioning from a specialized IAB into a more versatile threat actor. This evolution suggests the group is either starting its own ransomware operations or working in a much closer partnership with specific ransomware gangs.
The group's updated modus operandi includes several key components:
curl.exe and PowerShell to download and run malware in memory, avoiding writing files to disk.MachineGuid, which are specifically used by ransomware families like LockBit and ALPHV.This tactical shift makes Storm-0249 a more dangerous and potent threat, as they now control more of the attack chain from initial access to final impact.
The new attack chain observed by ReliaQuest is multi-staged and focuses on stealth:
Win+R) (T1204.002 - Malicious File, but with user-pasted commands).curl.exe binary to download a PowerShell script from an actor-controlled domain (e.g., sgcipl[.]com/us.microsoft.com/bdo/). The script is piped directly into PowerShell for execution, a fileless technique to avoid on-disk scanners (T1059.001 - PowerShell).SentinelAgentWorker.exe: The legitimate, signed executable from the SentinelOne security agent.SentinelAgentCore.dll: A malicious, trojanized DLL with the same name as a legitimate DLL required by the executable.
When SentinelAgentWorker.exe is run, the operating system loads the malicious DLL from the same directory instead of the legitimate one. This allows the attacker's code to run within the context of a trusted, signed process, evading application control and some EDR detections (T1574.002 - Hijack Execution Flow: DLL Side-Loading).MachineGuid, a unique identifier. This is a known precursor for ransomware attacks, as groups like LockBit use this GUID to generate unique encryption keys for each victim.| Tactic | Technique ID | Name | Description |
|---|---|---|---|
| Initial Access | T1566.002 |
Phishing: Spearphishing Link | The ClickFix technique is initiated through a lure, likely from a phishing campaign. |
| Execution | T1059.001 |
PowerShell | The actor uses fileless PowerShell to download and execute the next stage. |
| Defense Evasion | T1574.002 |
Hijack Execution Flow: DLL Side-Loading | Abusing the SentinelOne agent executable to load a malicious DLL is the key evasion tactic. |
| Defense Evasion | T1218.011 |
System Binary Proxy Execution: Rundll32 | The ClickFix method often uses rundll32.exe to execute the initial command. |
| Discovery | T1082 |
System Information Discovery | The malware gathers the MachineGuid as part of its reconnaissance phase. |
The evolution of Storm-0249 increases the overall risk to organizations. By bringing malware deployment in-house, the group can:
This trend signifies a maturation in the cybercrime ecosystem, where specialized actors are verticalizing their operations to increase efficiency and profitability.
| Type | Value | Description | Context | Confidence |
|---|---|---|---|---|
| command_line_pattern | curl.*|.*powershell |
The use of curl to download content and pipe it directly into a PowerShell process is a classic fileless execution pattern. |
EDR, Sysmon (Event ID 1), PowerShell Script Block Logging (Event ID 4104). | high |
| file_name | SentinelAgentCore.dll |
The presence of this DLL outside of the legitimate SentinelOne installation path is highly suspicious. | File integrity monitoring, EDR file creation events. | high |
| process_name | SentinelAgentWorker.exe |
Monitor for this process running from an unusual directory (i.e., not its default Program Files location). | EDR, Sysmon (Event ID 1). | high |
| domain | sgcipl.com |
The domain used to host the malicious PowerShell script. Should be blocked. | DNS logs, proxy logs, firewall logs. | high |
SentinelAgentWorker.exe) with the loading of an unsigned or mismatched DLL (SentinelAgentCore.dll).SentinelAgentCore.dll from being loaded.Push Security launches browser tool to block 'ClickFix' copy-paste attacks, directly mitigating a key social engineering tactic.
Use application control to prevent unauthorized DLLs from being loaded, which would defeat the side-loading technique.
Mapped D3FEND Techniques:
Train users to recognize social engineering techniques like 'ClickFix' and to never run commands from untrusted sources.
To directly counter Storm-0249's DLL side-loading tactic, organizations should implement a robust application control solution like Windows Defender Application Control (WDAC) or AppLocker. A properly configured policy would prevent the core of this attack. The policy should be configured to only allow signed binaries from trusted vendors to execute. More importantly, it should enforce that DLLs loaded by a process are also signed by the same trusted certificate. In this specific attack, while SentinelAgentWorker.exe is legitimately signed by SentinelOne, the malicious SentinelAgentCore.dll is not. An effective application control policy would block the signed executable from loading the unsigned, malicious DLL, thus breaking the attack chain at the defense evasion stage. This moves security from a reactive detection model to a proactive prevention model.
Given Storm-0249's reliance on fileless PowerShell, comprehensive PowerShell logging and analysis is a critical detection strategy. Organizations must enable PowerShell Script Block Logging (Event ID 4104) and Transcription Logging via Group Policy. This ensures that the full content of every PowerShell script executed on an endpoint is logged, even if it's downloaded and run entirely in memory, as seen with the curl | powershell technique. These logs should be forwarded to a SIEM, where analysts can create detection rules to hunt for suspicious activity. Rules should look for obfuscated commands, use of Invoke-Expression or IEX, network connection cmdlets, and scripts that attempt to interact with the registry or file system in unusual ways. This visibility into PowerShell activity is essential for de-obfuscating and understanding the attacker's actions during the initial execution phase.

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