Windows Browser-Injected rundll32 Execution Indicative of GuLoader Activity

Flags rundll32.exe being launched from a browser process, matching GuLoader-style injected browser execution behavior on Windows.

FreeReviewedSigma · High · v5
Product
windows
Category
process_creation
Author
@kostastsale (SigmaHQ), DRL 1.1
Published
2023-08-07
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule matches process creation where a rundll32.exe instance is spawned with its command line ending in \rundll32.exe and the parent process image is a browser (chrome.exe, firefox.exe, or msedge.exe). It is intended to flag GuLoader-style behavior where malware executes via a browser-injected process path and then initiates activity through rundll32. Detection relies on Windows process creation telemetry including parent image, child image, and command line fields.

Related detections9 linkedT1055 — drag to rearrange
Malicious AddInProcess32 Network Beacon on PureRAT C2 Ports
Suspicious Payload Staging in ProgramData IntelDriver Folder (via file_event)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious Named Pipe Created by Kazuar Backdoor for Interprocess Command Channel
Suspicious SmallTiger Backdoor DLL Load via Image Load
Suspicious svchost Execution With Anomalous Arguments via DeedRAT (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Suspicious GodRAT Shellcode Injection via Puppet Argument (via process_creation)
Windows Browser-Injected rundll32 Execution Indicative of GuLoader Activity
Pivot detection · T1055 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.