Proxy Log User-Agent Ending with '=' Suggesting Base64 Encoding

Alerts on proxy requests with User-Agent values ending in '=' that may indicate Base64-encoded content.

FreeReviewedSigma · Medium · v2
Category
proxy
Author
Florian Roth (Nextron Systems), Brian Ingram (update) (SigmaHQ), DRL 1.1
Published
2022-07-08
Updated
2026-07-31
title: Proxy Log User-Agent Ending with '=' Suggesting Base64 Encoding
id: e5be63ab-c47b-4ace-a83e-8c113e6b90a1
related:
  - id: d443095b-a221-4957-a2c4-cd1756c9b747
    type: derived
  - id: 894a8613-cf12-48b3-8e57-9085f54aa0c3
    type: derived
status: test
description: This rule flags proxy requests where the User-Agent field ends with an equals sign, a common base64 padding character. Attackers may use base64-encoded identifiers or payload markers within User-Agent to obfuscate command-and-control related data. It relies on proxy telemetry capturing the full User-Agent string and evaluates only the trailing character pattern.
references:
  - https://blogs.jpcert.or.jp/en/2022/07/yamabot.html
  - https://deviceatlas.com/blog/list-of-user-agent-strings#desktop
  - https://github.com/SigmaHQ/sigma/blob/master/rules/web/proxy_generic/proxy_ua_susp_base64.yml
author: Florian Roth (Nextron Systems), Brian Ingram (update), Huntrule Team
date: 2022-07-08
modified: 2023-05-04
tags:
  - attack.command-and-control
  - attack.t1071.001
logsource:
  category: proxy
detection:
  selection:
    c-useragent|endswith: =
  condition: selection
falsepositives:
  - Unknown
level: medium
license: DRL-1.1