New ROMULUS ClickFix Platform Delivers Malware, Evades Detection
Key Takeaways A new malware delivery platform, dubbed ROMULUS, is actively distributing various malicious payloads through “ClickFix” social engineering tactics. ROMULUS employs...
Key Takeaways
- A new malware delivery platform, dubbed ROMULUS, is actively distributing various malicious payloads through “ClickFix” social engineering tactics.
- ROMULUS employs sophisticated evasion techniques, including hidden PowerShell scripts, trojanized software installers, and multi-layered encrypted archives.
- The platform supports multiple infection chains, notably one that installs LegionLoader and another that leverages a legitimate Stardock application for DLL sideloading.
- Researchers from Forescout’s Vedere Labs identified ROMULUS, emphasizing the need for comprehensive security monitoring beyond isolated events.
ROMULUS Platform Emerges, Leveraging ClickFix for Malware Delivery
Cybersecurity researchers have uncovered a new, versatile platform named ROMULUS that facilitates the distribution of diverse malware through “ClickFix” social engineering schemes. This sophisticated delivery system integrates concealed PowerShell scripts, manipulated software installers, and layered encrypted archives to bypass detection and infect target systems.
Table Of Content
- Key Takeaways
- ROMULUS Platform Emerges, Leveraging ClickFix for Malware Delivery
- Discovery and Operational Insights
- Advanced Evasion Techniques: Hidden PowerShell and DLL Sideloading
- What You Should Do
- Indicators of Compromise (IoCs)
- Network and Delivery Indicators
- SHA-256 File Hashes
- Supporting Archive Artifacts
The ROMULUS platform demonstrates its adaptability by supporting distinct infection pathways. One identified route deploys the LegionLoader malware, while another exploits a legitimate Stardock application to inject malicious code via DLL sideloading. This modularity highlights a growing trend among threat actors to utilize flexible delivery mechanisms capable of serving multiple malware types while masquerading behind seemingly legitimate tools.
ClickFix attacks manipulate users into executing commands themselves, typically by presenting deceptive verification prompts or system repair instructions. This tactic transforms a routine web browsing session into a critical entry point for Windows-based infections.
Discovery and Operational Insights
Researchers from Forescout’s Vedere Labs identified ROMULUS during an independent incident investigation, subsequently publishing their detailed analysis on October 15, 2026. Their investigation uncovered six IP addresses exposing an identical login panel, allowing for the examination of two primary delivery chains. The identities of the operators behind ROMULUS remain unknown, and no connection has been established between this platform and the previously reported RomulusLoader.
The investigation linked the ROMULUS platform to a malware package previously documented by Huntress, which was involved in a campaign exploiting ChatGPT Custom GPTs. This earlier activity leveraged AI-powered pages to redirect unsuspecting visitors toward ClickFix traps. The observed operational pattern suggests that ROMULUS functions as a reusable backend for malware delivery, rather than a system designed for a singular payload. Its routing mechanisms utilize twelve-character tokens to retrieve either PowerShell staging scripts or malicious MSI installers. Researchers have not yet determined whether these tokens serve to identify victims, campaigns, assignments, or specific delivery jobs.
An exposed statistics page associated with ROMULUS tracked metrics such as unique installations, total runs, a fourteen-day historical overview, and geographical distribution by country. These features indicate the platform’s capability to assist operators in monitoring and evaluating campaign effectiveness. However, current evidence does not definitively classify ROMULUS as a private tool, a commercial criminal service, an affiliate system, or a shared resource among various threat groups.
Advanced Evasion Techniques: Hidden PowerShell and DLL Sideloading
Analysis of the recovered PowerShell scripts revealed a consistent design: obfuscated code is reconstructed from extensive numerical arrays before execution. Each script also includes a self-deletion mechanism upon completion. This approach allows for variations in appearance, such as changing keys and variable names, while maintaining the same underlying execution logic.
One observed infection route involved downloading an MSI installer via an IP address represented as a single decimal number, rather than the standard dotted-decimal notation. The installer was saved to a temporary folder, its downloaded-file restriction was removed, and Windows Installer was launched silently. Such ClickFix MSI installation attacks underscore the critical need for defenders to scrutinize the entire process chain rather than relying solely on the apparent legitimacy of an installer. In this instance, the package mimicked the “Stardock Smart DeElevation Tool” and, after installation, launched a genuine executable. This legitimate program then loaded a modified DLL from its own directory, which subsequently initiated the malicious loader. This DLL sideloading technique enables attackers to leverage trusted software as a springboard for malicious execution.
The second infection route concealed its PowerShell window and downloaded an encrypted archive alongside the legitimate 7-Zip command-line utility. This setup involved a nested archive structure: one password-protected archive contained another, with the inner archive’s password stored in an accompanying text file. Encrypted archive headers effectively obscure filenames and contents from scanners that lack the necessary password.
The extracted executable from this second route measured an exceptionally large 882,716,672 bytes. However, the majority of this size was attributed to repetitive padding within its relocation section. This technique allows an archive smaller than one megabyte to expand into a file large enough to bypass certain upload limits, sandbox budgets, or scanning thresholds, serving as an evasion method rather than an indication of widespread security product failure.
The LegionLoader delivery chain involved two unpacking stages, utilizing AES encryption and reversed decrypted bytes before loading LegionLoader into memory. Prior reports on other LegionLoader delivery chains confirm its use beyond ROMULUS, though a direct link between operators has not been established. Researchers also discovered five additional binary files whose specific functions remained unconfirmed.
Once deployed, LegionLoader registered infected systems, received commands, supported PowerShell execution, and managed the download of additional payloads. It was also found to access Chrome Local State key material to exfiltrate sensitive browser information. Its command-and-control (C2) traffic employed RC4 encryption and Base64 encoding, disguised within requests masquerading as ordinary web forms.
What You Should Do
- Monitor PowerShell script logs for unusual activity, especially scripts reconstructing hidden code.
- Inspect silent MSI installations originating from temporary folders, as these often indicate suspicious activity.
- Detect and investigate unusual DLL loads, particularly those where legitimate applications load unexpected or modified DLLs.
- Implement network visibility solutions to identify form requests containing single large Base64 blobs instead of typical form fields.
- Educate users to close browser verification pages that demand immediate command execution or software installation.
- Configure security solutions to review files that are skipped due to exceeding size limits, as this is a known evasion tactic.
- Correlate browser activity, script execution, and subsequent network traffic to identify complete attack chains rather than isolated events.
- Utilize the provided Indicators of Compromise (IoCs) in your threat intelligence platforms (e.g., MISP, VirusTotal, SIEM) for proactive detection and blocking. Remember to re-fang defanged IP addresses and domains only within controlled environments.
Indicators of Compromise (IoCs)
Network and Delivery Indicators
| Type | Indicator | Source context |
|---|---|---|
| IP address | 96.62.224[.]81 |
Huntress-documented ClickFix delivery node; ROMULUS frontend observed |
| Decimal IP | 1614733393 |
Decimal representation of the Huntress delivery node |
| IP address | 86.109.75[.]7 |
ROMULUS node serving both analyzed delivery chains |
| Decimal IP | 1450003207 |
Decimal representation used for the analyzed ROMULUS node |
| IP address | 151.240.151[.]223 |
Additional ROMULUS host; not individually analyzed |
| IP address | 23.94.145[.]224 |
Additional ROMULUS host; not individually analyzed |
| IP address | 93.152.224[.]118 |
Additional ROMULUS host; not individually analyzed |
| IP address | 2.27.248[.]127 |
Additional ROMULUS host; not individually analyzed |
| Staging URL | hxxp://86.109.75[.]7/s/19481b28bd67 |
PowerShell route for the Stardock package |
| MSI URL | hxxp://86.109.75[.]7/app/19481b28bd67/IconEdit2Turb.msi |
Trojanized Stardock installer |
| Decimal-IP URL | hxxp://1450003207/app/19481b28bd67/IconEdit2Turb.msi |
Installer URL used by the staging script |
| Staging URL | hxxp://86.109.75[.]7/s/6c67e0336a7b |
PowerShell route leading to LegionLoader |
| Delivery domain | orbitflownetwork[.]lol |
Hosts the encrypted archive |
| Archive path | /dl/J8QkZUVJgV.7z |
Archive location on the delivery domain |
| C2 domain | smashshape[.]com |
LegionLoader command-and-control server |
| C2 endpoint | /nfront.php |
Registration and command retrieval |
| C2 endpoint | /nback.php |
Results reporting |
| Earlier stager | novatrafficcore[.]lol/AsFJfTQYDTkpOg6K |
Direct ROMULUS connection unconfirmed |
| Additional MSI route | /app/60f9f0dbd64c/FreePhotoSlideShowDesktop_signed.msi |
Observed on the analyzed node; payload not analyzed |
| Additional MSI route | /app/40152518488f/235235.msi |
Observed on the analyzed node; payload not analyzed |
| Additional MSI route | /app/2c56afb54013/overlay.msi |
Observed on the analyzed node; payload not analyzed |
| Earlier staging path | /s/50d6565cf39e |
Route referenced in the earlier Huntress chain |
| Panel artifacts | /login, /api/login, /stats.htm |
Login, authentication, and exposed statistics paths |
SHA-256 File Hashes
All hashes below are SHA-256 values reported in Forescout’s analysis, including two helper-module hashes listed in its component table. The legitimate host executable is included for package correlation, not as proof that the file itself is malicious.
| File or stage | SHA-256 |
|---|---|
IconEdit2Turb.msi |
91a22cf3154944897cbcaffc7d20d4596e972d280ee134197d41d8d8eefb0fe2 |
DeElevate64.exe — legitimate host |
22869e3326fe1de011cd500e666769027126c5c440b76837baf55139f30094e4 |
DeElevator64.dll — patched DLL |
0457414c4504b70115798eee9c8384a8bf9e793461ffb2e0661a6dcc6ed4809f |
I++u.dll — malicious loader |
3cd1484cc5bf10e22d79784beba58a75d7b126c46efb5e1a85d6aab884447621 |
senddmp.resources.dll — helper module |
b59a21a8d4c0c11a9ecbbdbe2a2938499c99c5ebb210c9c6db9683c7ad19f4c4 |
res.dll — helper module |
a27cafb84876a3374ef4aba1062345def6cd0b029eaf8e0dc44fa24fc943f3c6 |
Build.dat — loader container |
d3fda1e6cf886fd530bf62e2d16c39ad23ed12a2c933fc211f1f4876ceaa033e |
execute_engine_disconnect.raw |
d5acf44658f0dce90bd160f15d8e07a96938c81661d87dc7e9cb0107863bfb90 |
| Route A staging script | 6147d56b5e35d6435d83adb49908c40a97520a0c3379121104816e37cbd1df28 |
| Route B staging script | 62ca523863337ac5d6b1c4d9ae262d1b2eb7dd9ca764b702ef719c84b2437a39 |
J8QkZUVJgV.7z |
3b074d6f9bc399fbb1362aeb6ffe1e02013f10e8fa095fc2b3381d8cec270435 |
CarJqRHyOtBu3mI.7z |
4e2955f5f5861a51c07fe386d782a3872cfe1c9e750295daa94626f2bd97d84a |
| Inflated executable carrier | 1f403ac059f172e99968ce96bd0ef1bd1981070b454e3e5d75a71368c3c8762a |
| Stage 2 shellcode | 4e0941d243c0b16e9019e4f9c5eb0f6e6630af4d44d9677611917450bb2e696e |
| Stage 3 LegionLoader executable | 2e3d378d6a842af2404dfcd1dcbfc0df84b01b799b2c8270ddbfe5eb18837762 |
Supporting Archive Artifacts
These passwords are analysis artifacts from the source, rather than standalone evidence of compromise.
| Archive | Reported password | Password location |
|---|---|---|
J8QkZUVJgV.7z |
iQQaQ7Yo41rbZ |
Hardcoded in the staging script |
CarJqRHyOtBu3mI.7z |
RkfZvXZt6XtfuoZsHfSr |
Text file extracted from the outer archive |
Note: IP addresses and domains are intentionally defanged (e.g., [.]) to prevent accidental resolution or hyperlinking. Re-fang only within controlled threat intelligence platforms such as MISP, VirusTotal, or your SIEM.
Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.



No Comment! Be the first one.