Possible Apache ActiveMQ RCE via Jolokia addNetworkConnector (via webserver)

PremiumReviewedSigma · High · v1
Category
webserver
Author
HuntRule
Published
2026-09-27
Updated
2026-09-27

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects HTTP requests to the ActiveMQ Jolokia API that invoke the addNetworkConnector broker operation with a remote xbean configuration URI. This corresponds to CVE-2026-34197 remote code execution where the broker loads an attacker hosted Spring bean. Administrators rarely add network connectors that reference external HTTP xbean configs.

Related detections9 linkedT1059 — drag to rearrange
Malicious Git Config sshCommand Modification for Code Execution on Linux
Suspicious Reconnaissance Commands Spawned by Node.js Runtime on Linux
Suspicious Selenium Grid Binary Location RCE via Python Interpreter on Linux
Possible Ivanti EPMM Unauthenticated RCE via featureusage Expression Language Injection (via webserver)
Malicious Python pth Site Hook Written via FortiWeb Fabric Connector SQL Injection (via file_event)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious Reconnaissance and Payload Download by Node Web Process
Malicious Text4Shell Apache Commons Text Interpolation Payload in HTTP Request
Possible LiteLLM Unauthenticated Command Execution via MCP Test Endpoints (via webserver)
Possible Apache ActiveMQ RCE via Jolokia addNetworkConnector (via webserver)
Pivot detection · T1059 · 9 related

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