huntrule

Webserver JNDI-Exploit-Kit Exploitation Indicators via Known Payload Paths

Flags webserver requests whose URL paths match known JNDI-Exploit-Kit exploit, deserialization, and memshell pattern strings.

FreeReviewedSigma · High · v2
Category
webserver
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-12-12
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Initial Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies web exploitation attempts using patterns associated with the JNDI-Exploit-Kit by matching specific URL or path substrings in webserver logs. Attackers often use these payload paths to trigger JNDI-related behavior and deploy or execute follow-on functionality such as reverse shells or memshells. The detection relies on keyword/path telemetry from webserver requests containing the listed signature fragments.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
Possible SharePoint ToolShell ToolPane Exploitation Attempt (via webserver)
Possible Apache ActiveMQ Exploitation via Java Spawning Command Shell (via process_creation)
Malicious Veeam CVE-2023-27532 Exploitation Enabling xp_cmdshell via VeeamHax (via process_creation)
Suspicious PraisonAI Unauthenticated Config Endpoint Access via Webserver
Malicious Langflow Build Public Temp RCE Access via Webserver
Suspicious PraisonAI Vulnerability Scanner User Agent via Webserver
Malicious LiteLLM Authentication SQL Injection via Web Request (via webserver)
Possible Marimo Unauthenticated Terminal WebSocket Access via Web Request (via webserver)
Possible React2Shell Next.js Prototype Pollution Exploitation via Web Request (via webserver)
Webserver JNDI-Exploit-Kit Exploitation Indicators via Known Payload Paths
Pivot detection · T1190 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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