Proxy User-Agent starts with Base64-like prefixes associated with encoded client strings

Identifies proxy requests with User-Agent values starting with known Base64-encoded prefixes.

FreeReviewedSigma · Medium · v2
Category
proxy
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-05-04
Updated
2026-07-31
title: Proxy User-Agent starts with Base64-like prefixes associated with encoded client strings
id: cd917286-80cd-4ceb-a761-9d02d8d65b8e
related:
  - id: 894a8613-cf12-48b3-8e57-9085f54aa0c3
    type: derived
  - id: d443095b-a221-4957-a2c4-cd1756c9b747
    type: derived
status: test
description: This rule flags HTTP proxy logs where the User-Agent header starts with specific Base64-like prefixes that indicate an encoded client identity. Attackers and malware may use encoded User-Agent values to evade simple filtering, blend into traffic patterns, or obscure their tooling. Detection relies on proxy telemetry capturing the User-Agent field and matching the specified starting substrings.
references:
  - https://deviceatlas.com/blog/list-of-user-agent-strings#desktop
  - https://github.com/SigmaHQ/sigma/blob/master/rules/web/proxy_generic/proxy_ua_base64_encoded.yml
author: Nasreddine Bencherchali (Nextron Systems), Huntrule Team
date: 2023-05-04
tags:
  - attack.command-and-control
  - attack.t1071.001
logsource:
  category: proxy
detection:
  selection:
    c-useragent|startswith:
      - Q2hyb21l
      - QXBwbGVXZWJLaX
      - RGFsdmlr
      - TW96aWxsY
  condition: selection
falsepositives:
  - Unknown
level: medium
license: DRL-1.1