Malicious Chrome Launch with HTTP2 and QUIC Disabled for Man-in-the-Browser Interception (via process_creation)

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-11-10
Updated
2026-11-10

ATT&CK techniques

Collection
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects Chrome being started with HTTP/2 and QUIC disabled together with a one-byte disk cache, the launch arguments Ramnit forces in the drIBAN banking-fraud operation to downgrade traffic to HTTP/1.1 that it can intercept and modify. Adversaries constrain the browser this way to enable reliable man-in-the-browser tampering of banking sessions, making early detection critical for exposing web-inject fraud before funds are transferred.

Related detections4 linkedT1185 — drag to rearrange
Suspicious Chrome Launch With Remote Debugging via Airstalk (via process_creation)
Suspicious Browser Launch With Remote Debugging Port via Process Creation
Windows Chromium-Based Browsers Launched with Headless Debugging and User Profile Directory
Windows: Detect Browsers Launched with Remote Debugging Flags
Malicious Chrome Launch with HTTP2 and QUIC Disabled for Man-in-the-Browser Interception (via process_creation)
Pivot detection · T1185 · 4 related

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