Live operation queue
Cases
Potential operations correlated across HTTP, process, network, and workload evidence.
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Request contains shell metacharacters and command tokens
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Request contains shell metacharacters and command tokens
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Response contains non-reflected kernel identification
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Exploit request received non-reflected process identity output
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
The four preserved incident threads are best explained as a likely single operation against the same protected workload, but the evidence does not prove one actor or unique HTTP-to-process causality. Incident [redacted] establishes confirmed root-level command execution during an initial exploitation window; incident [redacted] contains overlapping process-only root shell activity linked by [redacted]. Later, incident [redacted] records enumeration and attempted exploitation from the same source cluster as [redacted] under link [redacted], followed by process-only root shells in [redacted] linked through [redacted]. This connected sequence supports resumed or continued activity more strongly than unrelated operations, while the source-cluster ambiguity, approximately 69-minute gap, and absent unique request-to-process edges prevent a definitive same-operation finding.
Confirmed compromise
The strongest defensible explanation is a likely single operation, while preserving all four incident boundaries. The HTTP activity shows repeated suspected command injection, later confirmed application-workload compromise, and subsequent route/method enumeration against the same target from the same derived source cluster [redacted]. Overlapping shell and discovery activity on the protected workload is also temporally and operationally consistent with the confirmed-compromise thread [redacted]. This is not proof of one actor or a unique request-to-process chain: the source is only a cluster, the process-only incident lacks HTTP parentage, and the later enumeration could be separate or authorized activity.
Confirmed compromise
True positive: HTTP evidence proves successful command injection and root-level command execution in the responding workload, even though the responses were HTTP 400. The strongest event contains shell-command input and non-reflected process-identity output identifying UID 0 ([redacted]); another response disclosed non-reflected kernel information ([redacted]). Event-driven process telemetry independently shows root shells and discovery commands in the correlated workload, followed by sensitive-target and shared-resource activity. The detector's confirmed state and confirmed-compromise classification are therefore supported. Process timing does not establish a unique request-to-process edge, and no cited flow evidence was available to assess outbound consequences.
Confirmed compromise
The three preserved incident threads are best explained as one likely operation, not as proven single-actor activity. Incident [redacted] records confirmed remote command execution as root beginning at [redacted]33Z. Incidents [redacted] and [redacted] then record overlapping root-shell, discovery, sensitive-file, and shared-resource activity. Deterministic links [redacted] and [redacted] connect each process-only thread to the confirmed-compromise thread by protected-workload attribution and temporal proximity. This is a coherent possible exploitation-to-post-compromise progression, but the links do not prove request-to-process causality, and the process-only threads lack correlated HTTP requests or known actors.
Confirmed compromise
The five distinct incident threads are best explained as a likely single operation affecting two protected workload clusters: sustained HTTP command-injection/confirmed remote root execution overlaps two waves of shell, discovery, and sensitive-file-access process activity [redacted]. Repeated activity in each of the two derived workload clusters and the closely synchronized late shell wave strengthen continuity [redacted]. This is not assessed as definitively the same operation because process executions lack correlated HTTP evidence, the earliest process activity predates the HTTP thread, and all deterministic links establish only shared-workload attribution plus temporal proximity—not unique request-to-process causality [redacted]. Incident boundaries remain intact.
Confirmed compromise
The two immutable incident threads are best explained as related parts of one operational episode, but not conclusively one actor or one causal chain. Incident [redacted] records broad HTTP enumeration followed by confirmed command/root execution and related process behavior, while incident [redacted] records overlapping event-driven shell, outbound-client, and shared-resource activity. Deterministic link [redacted] ties them by protected-workload attribution and temporal proximity at 0.9 confidence. The overlap and compatible behaviors support likely_same_operation; the absence of a unique request-to-process edge and the workload-derived identity of the process-only thread prevent a definitive same_operation finding.
Confirmed compromise
Response contains non-reflected process identity output
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Confirmed compromise
Broad unauthenticated route and HTTP method enumeration observed
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
A process modified an inventory-resolved resource attached to multiple workloads
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven outbound-capable client was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven process targeted a sensitive file in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Observed workload execution
The detector's critical suspicious-activity output is supported at the consequence level: event-driven telemetry observed a root-context dash shell in the processor workload and a root-context child id discovery process, followed by zero-result exits. However, the available evidence does not establish whether this execution was malicious, authorized workload behavior, or administrative/testing activity. No incident-cited HTTP or flow evidence was available to establish an originating request, actor, request-to-process causal edge, or network consequence. Therefore, execution and discovery are confirmed, while exploitation or compromise remains indeterminate.
Observed workload execution
The two immutable incident threads are best explained as parts of one likely operation: an HTTP-side sequence of broad unauthenticated enumeration followed by confirmed root-context command execution and system discovery, then a closely timed process-only sequence of additional root shells, discovery, and a sensitive-file access command in the same protected workload [redacted]. This is not assessed as definitively the same operation because the deterministic link establishes only workload attribution and temporal proximity, not a unique request-to-process causal edge or common actor [redacted]. Incident boundaries and detector conclusions remain unchanged.
Observed workload execution
The incident is a true positive for successful command injection, not merely an attempt. Repeated malicious HTTP inputs were observed, including one targeting the system account database [[redacted]]. A captured HTTP response contained non-reflected server-generated identity output identifying UID 0/root even though the response status was 400 [[redacted]]; status therefore does not negate execution. Independent process telemetry recorded root shells, discovery, a sensitive-file command, and mutation/execution of the same shared resource in correlated workload contexts [redacted]. The HTTP-to-process relationship remains temporal/workload correlation rather than a unique per-request parentage edge, but the server-generated output directly establishes server-side root execution.
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Response contains non-reflected process identity output
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Response contains non-reflected process identity output
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Rapid enumeration of PHP and WordPress web-shell paths
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Rapid enumeration of PHP and WordPress web-shell paths
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
Broad unauthenticated route and HTTP method enumeration observed
Attempted exploitation
Request contains shell metacharacters and command tokens
Attempted exploitation
The incident is most consistent with automated reconnaissance followed by a genuine command-injection attempt against target privatekind. The injection-marked PUT carried shell metacharacters and command tokens and received HTTP 200, but its response body was empty; status alone does not establish execution (HTTP [redacted]). Representative later probes used POST against API-category paths and received 404 responses (HTTP [redacted] and [redacted]). No cited process or flow evidence was available to establish command execution or follow-on network activity. The verdict remains “likely” rather than definitive because authorization is unknown and the source key is a traffic cluster rather than a verified actor identity.
Attempted exploitation
A captured POST request triggered the immutable high-confidence command-injection-attempt detector for shell metacharacters with command tokens. The request received HTTP 301 with an empty response body, which neither proves nor disproves execution. No process or flow evidence is cited by this incident, so observed command execution or downstream network activity cannot be established. Evidence: HTTP event [redacted] (SHA-256 [redacted]).
Attempted exploitation
The incident is a true positive for attempted command injection, not confirmed compromise. The verified HTTP event records a POST whose request content triggered the command-injection detector for shell metacharacters with command tokens and identified the targeted resource as the system account database [redacted]. The transaction returned HTTP 200 with a 1,389-byte response, but status and response size do not establish command execution or disclosure [redacted]. No cited process or flow event is available to verify downstream consequences.
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Suspicious activity
Response contains non-reflected process identity output
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Suspicious activity
Response contains non-reflected process identity output
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Reconnaissance
Broad unauthenticated route and HTTP method enumeration observed
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
Rapid enumeration of PHP and WordPress web-shell paths
Opportunistic scan
This is a true positive for opportunistic reconnaissance/web-shell path enumeration against target privatekind, not a confirmed compromise. Verified HTTP summaries show rapid, bodyless GET requests categorized as PHP or WordPress probes from the same source traffic cluster. The sampled responses were redirects or not-found responses with no server-generated command output. The incident cites no process- or flow-plane event IDs, so the available evidence does not establish command execution, outbound communication, persistence, or other post-exploitation impact.
Opportunistic scan
This is a true-positive opportunistic reconnaissance event: the source traffic cluster rapidly issued repeated GET requests categorized as PHP/WordPress probes against target privatekind. The detector aggregate records 37 requests across 20 unique probe paths in about 4.4 seconds. Available HTTP evidence shows redirect/rejection outcomes (301 and 404), with no server-generated command output in the inspected summaries. The evidence supports web-shell path enumeration, but not successful exploitation or compromise.
Opportunistic scan
The incident is a true positive for opportunistic PHP/WordPress web-shell path enumeration against target privatekind. The detector recorded 39 requests across 20 probe paths in roughly 4.3 seconds, and the inspected HTTP evidence confirms repeated GET requests categorized as php_or_wordpress_probe from one derived source cluster [http:[redacted]; http:[redacted]; http:[redacted]; http:[redacted]]. Inspected responses were redirects or 404 rejections; this supports detection of scanning but, because HTTP status alone is not dispositive, does not prove exploit failure. No cited process or flow evidence was available to establish execution or network consequences.
Opportunistic scan
This is a true positive for opportunistic PHP/WordPress web-shell path enumeration, not for successful exploitation. The deterministic detector recorded 41 requests against 20 probe paths in roughly 4.7 seconds. The retained HTTP summaries consistently classify the requests as PHP/WordPress probes from one traffic cluster to target privatekind and show only 301 redirects or 404 responses. No cited process or flow evidence is available to establish command execution, persistence, outbound activity, or other compromise consequences.
Reconnaissance
The incident is best assessed as likely true-positive application-surface reconnaissance. The detector aggregated 64 requests from one traffic/workload cluster across 51 unique paths, five HTTP methods, and six path categories, with 53 rejected responses. The verified samples show rapid requests to distinct route hashes, mixed GET/POST usage, and repeated 401/422 responses, consistent with automated route and method enumeration. Two sampled requests returned HTTP 200, but status alone does not establish exploitation or compromise. Authorization is unknown, so sanctioned security testing or inventory remains a plausible alternative. No process or flow evidence is cited by this incident, so no execution, outbound consequence, persistence, lateral movement, or data loss is established.
Opportunistic scan
The alert accurately identifies a rapid, opportunistic enumeration campaign against PHP/WordPress web-shell-style paths. The verified HTTP samples are bodyless GET probes assigned to the php_or_wordpress_probe category, use multiple distinct path hashes, and span roughly 5.34 seconds. Sampled outcomes are redirects or not-found responses; they establish reconnaissance but not exploitation or compromise. No process- or flow-plane event references are available in this incident to assess downstream execution or network consequences.
Opportunistic scan
The incident is strongly consistent with real opportunistic PHP/WordPress web-shell path enumeration against target privatekind. Verified HTTP summaries show rapid GET requests categorized as PHP/WordPress probes from the same source cluster, with distinct path hashes and rejection/redirect outcomes. The available responses include 404s and a 301; these support unsuccessful discovery attempts but, by themselves, do not prove that every request failed to trigger application behavior. No process or flow evidence is cited by this incident, so there is no evidence-grounded basis to claim command execution, outbound activity, persistence, or compromise. The verdict therefore affirms the scanning activity, not successful exploitation.
Reconnaissance
Likely true positive for automated HTTP reconnaissance against target privatekind. The cited HTTP sequence supports rapid, broad, unauthenticated surface enumeration: the detector aggregated 64 requests to 64 unique paths across two methods and seven path categories in roughly 2.74 seconds, with 52 rejected responses. Verified examples have distinct path hashes, complete captures, empty request bodies, and mostly uniform 404 responses; the root request returned 200. This establishes probing behavior, not exploit success. Authorization is unknown, and no process or flow evidence is cited by the incident, so no workload compromise or follow-on network consequence is established.
Opportunistic scan
The incident is a true positive for opportunistic PHP/WordPress web-shell path enumeration, not for successful exploitation. The detector aggregated 39 requests across 20 probe paths in roughly 4.3 seconds. Verified HTTP summaries identify sampled requests as GETs in the php_or_wordpress_probe category; the first returned a 301 with an empty response body and the next returned a 404. The incident's cited HTTP evidence records only redirects or rejections, with no observed exploit consequence. No process or flow evidence references were available in this incident, so execution, outbound activity, and compromise cannot be determined from those planes.
Reconnaissance
The evidence supports a real, sustained web-surface enumeration pattern against target privatekind: the detector-derived facts report 1,205 requests over 512 connections, 128 unique paths, four methods, and eight path categories. Verified HTTP samples from the cited cluster show requests to multiple path hashes/categories with mixed 200, 400, 403, and 404 responses, consistent with route probing. This is best assessed as likely true-positive reconnaissance, not confirmed compromise. Authorization and intent remain unresolved, and the incident contains a material semantic inconsistency: its summary calls the activity unauthenticated while its own facts count 1,057 authenticated requests. No process- or flow-plane evidence is cited, so execution, persistence, outbound activity, or other post-reconnaissance consequences are not established.
Opportunistic scan
The incident is a true positive for opportunistic reconnaissance: one derived source cluster rapidly issued 39 GET requests covering 20 distinct PHP/WordPress probe paths against target privatekind between [redacted].030Z and [redacted].351Z. Representative complete captures returned redirects or rejections, including 301 and 404 responses (HTTP evidence [redacted], [redacted], and [redacted]). This establishes scanning/enumeration, but the available evidence does not establish web-shell access, command execution, persistence, or outbound activity.
Opportunistic scan
This is a true positive for opportunistic reconnaissance: the detector aggregated 39 rapid GET requests across 20 PHP/WordPress probe paths from one derived traffic cluster. The verified HTTP summaries show capture-complete probe requests receiving redirects or rejections, including 301 and 404 responses. The evidence supports web-shell path enumeration, but not successful exploitation or compromise. No process or flow evidence is cited by this incident, and HTTP status alone cannot establish exploit failure, so execution and network consequences remain unproven rather than ruled out.
Opportunistic scan
This is a true positive for rapid opportunistic reconnaissance, not confirmed exploitation. The detector recorded 39 requests across 20 PHP/WordPress probe paths in about 4.3 seconds, and the bounded HTTP summaries show representative GET probes receiving 301 redirects or 404 rejections. The derived detector outcome remains redirect_or_rejection_only. There is no cited process or flow evidence with which to establish command execution, outbound activity, or any request-to-consequence causal edge.
Reconnaissance
The bounded HTTP evidence supports the detector's reconnaissance classification: one source cluster sent varied HEAD, GET, and POST requests across root, API, and other route categories on target privatekind during the cited interval [redacted]. Responses varied among 200, 401, 404, 422, and 500, and several GETs returned sizable bodies, indicating that some probed resources responded with content [redacted]. This is strong evidence of surface enumeration, but authorization and operator identity are unknown. No cited process or flow events were available to assess consequences beyond HTTP reconnaissance.
Opportunistic scan
The incident is a true positive for rapid automated PHP/WordPress web-shell path enumeration, not for confirmed compromise. The detector grouped 39 requests across 20 unique probe paths in approximately 4.27 seconds. Retrieved representative requests are categorized as php_or_wordpress_probe and returned only 301 or 404 responses. Those status codes do not by themselves prove exploit failure, but the available evidence contains no process or flow references with which to establish execution, outbound activity, persistence, or data access.
Opportunistic scan
The incident is a true positive for opportunistic reconnaissance: the traffic cluster rapidly issued GET requests categorized as PHP or WordPress probes against target privatekind, and the detector aggregated 38 requests spanning 20 unique probe paths. The cited HTTP outcomes were redirects or rejections, so this establishes web-shell path enumeration but not successful exploitation. No process or flow evidence is cited by the incident, leaving execution and downstream network consequences unproven.
Opportunistic scan
The incident is a true positive for rapid opportunistic enumeration of PHP/WordPress web-shell paths against target privatekind. The detector reports 38 requests over roughly 7.7 seconds and 20 unique probe paths; the verified cited samples are bodyless GET requests categorized as PHP/WordPress probes and received only 301 or 404 responses. This establishes hostile or unauthorized reconnaissance behavior, but not successful exploitation or compromise. No process or flow evidence is cited by the incident, so execution, outbound communication, persistence, or other post-request consequences cannot be determined from the available evidence.
Reconnaissance
The incident is strongly supported as broad, unauthenticated HTTP surface enumeration against target privatekind. The detector aggregated 75 requests across 48 unique paths, two methods, six path categories, and 46 connections from one derived source cluster; the verified samples show rapid HEAD/GET probing of distinct path hashes with mixed 200, 404, and 500 responses. Multiple 200 responses indicate that some probed routes returned content, but status codes and response sizes do not establish exploitation or sensitive-data exposure. No process- or flow-plane evidence is cited by this incident, so consequences beyond reconnaissance cannot be assessed. Because authorization and source identity are unknown, sanctioned scanning remains a material alternative.