Microsoft Sentinel KQL / Sigma: Zammad Webhook Session Fixation & YAML Deserialization Hunting — Threat Hunting Query
Hunting Telemetry & Platform Metadata
Section titled “Hunting Telemetry & Platform Metadata”| Evaluation Dimension | Observed Telemetry / Attribute | Epistemic Status |
|---|---|---|
| Hunting Query Identifier | HUNT-ZAMMAD-WEBHOOK-DESER | Canonical Hunt Node |
| Target SIEM / Analytics Platform | Microsoft Sentinel / Linux Web Access Logs | Telemetry Ingestion Engine |
| Platform Syntax Dialect | sentinel_kql | Query Language Standard |
| Telemetry & Log Sources | Nginx Access Logs, Apache Access Logs, Puma Application Logs, Linux Auditd | Data Sensor Sources |
| Targeted Adversary Syndicates | ShinyHunters, CLOSEDQUORUM Threat Cluster | Threat Attribution |
| Associated Weaponized CVEs | CVE-2026-102489 | Vulnerabilities Targeted |
| Associated Intrusion Campaigns | CLOSEDQUORUM Autonomous Infiltration Wave | Monitored Campaign |
| Analytical Confidence | 99% | Hypothesis Validity Score |
| Primary Evidence Sources | SRC-CISA-KEV, SRC-MANDIANT-GOOGLE | Intelligence Attestation |
Threat Hunting Hypothesis
Section titled “Threat Hunting Hypothesis”Adversaries are actively exploiting CVE-2026-102489 by injecting fixed session identifiers in X-Zammad-Session-Hint headers and supplying Ruby YAML deserialization gadget chains to achieve unauthenticated remote code execution.
Adversary operations frequently slip through standard alerting thresholds by leveraging legitimate binaries or abusing valid service configurations. Proactive threat hunting formulates precise hypotheses based on known architectural chokepoints and queries historical telemetry to unearth stealthy intrusion footholds.
Production Hunting Query
Section titled “Production Hunting Query”DeviceProcessEvents| where InitiatingProcessFileName =~ "puma" or InitiatingProcessCommandLine has "zammad"| where FileName in~ ("bash", "sh", "dash", "python", "python3", "curl", "wget", "nc")| project Timestamp, DeviceName, ActionType, FileName, CommandLine, InitiatingProcessCommandLine, AccountName| order by Timestamp descTriage Guidance & Investigation Protocol
Section titled “Triage Guidance & Investigation Protocol”Inspect Puma web worker child processes spawning interactive shells. Audit web server logs for inbound_webhooks POST requests with DeprecatedInstanceVariableProxy markers. Invalidate active sessions via Rails console.
- Verify Timeline Baseline: Review the first seen and last seen timestamps of returned events to distinguish chronic benign traffic from sudden operational spikes.
- Examine Parent-Child Lineage: Ensure that all parent processes match authorized deployment manifests and do not conceal unexpected interactive utilities.
- Inspect Network Pivots: Cross-reference communicating source and destination IP addresses against Hermes Adversary Infrastructure endpoints.