Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / NETWORK

Proxy Abuse

This note documents detection patterns related to Proxy Abuse within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Sysmon3Network connectionCriticalDetects outbound connections via proxy clients or proxy-aware tools.
Security4688Process creationCriticalDetects proxy tooling and proxy-enabled commands.
Sysmon1Process creationCriticalBest lineage source for proxy abuse chains.
Sysmon13Registry value setHighProxy settings modified in registry.
Sysmon22DNS queryHighProxy destinations and relays.
PowerShell4104Script block loggingCriticalProxy settings in PowerShell visible here.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Proxy registry changedInternet Settings modifiedCriticalCore proxy abuse primitive.
netsh winhttp proxy setSystem proxy alteredCriticalStrong signal.
curl / bitsadmin uses proxyExfil or stagingCriticalCommon operator path.
Unusual outbound via local proxylocalhost relayHighStealth clue.
Proxy immediately before downloadStrong staging sequenceCriticalHigh-confidence chain.
Proxy reverted after useCleanup behaviorHighSkilled operator sign.

Common Tools

ToolUsage
netshWinHTTP proxy config
PowerShellProxy object creation
curl.exeProxy-aware transfer
bitsadminProxy-aware staging

Relevant Artifacts

  • Sysmon Event IDs 3, 1, 13, 22
  • Security Event ID 4688
  • PowerShell 4104
  • Registry paths:
    • HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings
  • Commands:
    • netsh winhttp set proxy
  • Prefetch:
    • NETSH.EXE
    • CURL.EXE

MITRE ATT&CK References

  • T1090 Proxy

Decision Tree

  1. Which proxy type?

    • WinHTTP
    • User proxy
    • Tool-level proxy
  2. Registry or command?

    • netsh
    • PowerShell
    • Registry edit
  3. Follow-on action?

    • Download
    • Beacon
    • Exfil
  4. Reverted later?

    • Yes
    • No
  5. Expand:

    • DNS
    • Outbound chain
    • Payload path
  6. Scope:

    • Single use
    • Persistent relay
    • Campaign behavior

Example Detection Templates

KQL

SecurityEvent
| where EventID == 4688
| where CommandLine has_any ("netsh winhttp set proxy","proxy")
| project TimeGenerated, Computer, CommandLine
Sysmon
| where EventID == 13
| where TargetObject has "Internet Settings"
| project TimeGenerated, Computer, TargetObject, Details

EQL

process where process.command_line like "*set proxy*"
sequence by host.name with maxspan=5m
  [ process where process.name == "netsh.exe" ]
  [ network where true ]

Sigma

title: Proxy Abuse Detection
id: 2d4b8f16-proxy-abuse
status: experimental
description: Detects suspicious proxy configuration changes
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: security
detection:
  selection:
    EventID: 4688
  keywords:
    CommandLine|contains:
      - 'set proxy'
      - 'winhttp'
  condition: selection and keywords
fields:
  - CommandLine
falsepositives:
  - Legitimate proxy administration
level: high
tags:
  - attack.command_and_control

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Alert on proxy changesStrong signalCriticalCore visibility
Watch Internet Settings writesValuable contextHighLow noise
Correlate proxy + transferHigh-confidence chainCriticalStrong triage
Restrict netsh usageReduce abuseHighPrevent reconfiguration
Preserve 4104Catch scripted proxy setupHighValuable evidence