Live evidence workspace
Evidence
Sanitized incident threads, signals, evidence planes, and AI conclusions update continuously.
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Response contains non-reflected process identity output
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
A process modified an inventory-resolved resource attached to multiple workloads
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Response contains non-reflected process identity output
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Response contains non-reflected process identity output
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven outbound-capable client was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Response contains non-reflected process identity output
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven process targeted a sensitive file in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Response contains non-reflected process identity output
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Response contains non-reflected kernel identification
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Request contains shell metacharacters and command tokens
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven discovery command was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Exploit request received non-reflected process identity output
Broad unauthenticated route and HTTP method enumeration observed
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
An event-driven shell execution was observed in a protected workload without correlated HTTP evidence
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Broad unauthenticated route and HTTP method enumeration observed
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
Request contains shell metacharacters and command tokens
Broad unauthenticated route and HTTP method enumeration observed
Rapid enumeration of PHP and WordPress web-shell paths
Request contains shell metacharacters and command tokens
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.
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.
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.
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.
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.
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.
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]).
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.
Likely true positive for suspicious in-workload command execution, but not proof of remote exploitation or compromise. Event-driven process telemetry shows repeated root-run dash shells in one workload, including discovery activity and a root-run cat process classified as targeting a sensitive file (process evidence [redacted], [redacted], [redacted], [redacted], [redacted], and [redacted]). The first and latest cited shells exited successfully, indicating short-lived execution rather than persistence ([redacted] and [redacted]). No HTTP or flow evidence reference is available in this incident, so the trigger, actor, authorization, and any network consequence remain unknown.
Verified HTTP evidence shows non-reflected root identity output and kernel identification returned by the server, despite HTTP 400 responses. Event-driven process telemetry independently observed root-run dash shells and an id child in the correlated workload during those response windows, followed by zero-result lifecycle exits. Together, this establishes real server-side command execution and discovery, not reconnaissance alone. The HTTP-to-process edge remains temporal/workload correlation rather than unique request causality, and no incident-cited flow evidence was available to assess network follow-on activity.
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.
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.
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.
Likely true positive command-injection exploitation with workload-level execution. Multiple HTTP requests were classified as containing shell metacharacters and command tokens, and root-context dash processes appeared tens of milliseconds later in the correlated processor workload. The strongest examples include dash spawning the discovery utilities id and uname as direct children. This repeated request/exec pattern strongly supports successful command execution, although routing affinity and temporal correlation do not provide a unique per-request causality edge. No cited flow evidence was available, so outbound communication, command-and-control, and exfiltration are not established.
Process telemetry conclusively shows repeated root-level dash execution in the processor workload, including discovery-classified shells and a final root dash→id parent-child chain [redacted]. Exact PID-matched lifecycle evidence also shows sampled shells exiting, generally successfully [redacted]. These are real execution consequences, but the bounded evidence does not establish whether they were authorized processor behavior or malicious activity. No usable HTTP or flow evidence was cited, so initial access, actor, request causality, network consequences, and compromise cannot be determined.
True positive confirmed compromise: captured exploit/response evidence shows command-oriented input followed by non-reflected root identity and kernel output in the responding workload, despite HTTP 400 [[redacted]; [redacted]]. Event-driven telemetry independently observed root shells and discovery processes in the correlated workload [redacted]. The detector's immutable state is confirmed, and the inspected evidence supports that result. Later sensitive-target and network-client-class processes increase concern, but request-to-process and request-to-socket causality remain unproven [redacted].
Three event-driven process records confirm root-context `dash` shell executions in the same workload, all with parent PID 2212455 [redacted]. Matching lifecycle records show all three PIDs subsequently exited with outcome zero [redacted]. This proves shell execution inside the workload, but the available argument-free summaries do not identify the commands or actor. No HTTP or flow evidence IDs are cited by the incident, so exploitation and network consequences cannot be established. The behavior could represent malicious execution or legitimate processor/administrative activity.
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.
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.
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.
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.
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.
The incident is strongly supported as web-surface reconnaissance. The detector aggregated 58 unauthenticated requests across 32 unique paths, two methods, and eight path categories from one derived source cluster, with 32 rejected responses (HTTP evidence set [redacted] through [redacted]). Verified samples corroborate a rapid sequence of empty-body GET probes against distinct path hashes: the root returned 200, while several subsequent routes returned 404. This supports route enumeration but does not establish exploit execution or compromise. Authorization and the real actor behind the source cluster remain unknown.
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.
Verified process telemetry shows a repeated pattern of root-run dash executions in one processor workload, including a discovery-classified shell and a two-process parent/child chain classified as both shell and network client. The first verified shell has a matching exit event moments later. This substantiates the detector's suspicious execution findings (process refs [redacted], [redacted], [redacted], and [redacted]). However, the bounded evidence does not establish malicious intent, an originating HTTP request, or any actual outbound connection. The verdict is therefore likely true positive for suspicious workload execution, not confirmed exploitation or compromise.
Confirmed remote command injection with successful root-level execution in the responding application workload. Non-reflected process-identity and kernel output in HTTP responses proves execution even though the responses were HTTP 400. Event-driven process telemetry independently shows root-run dash shells spawning id, uname, and hostname in matching windows. A public-web outbound flow was also observed from an inventory-attributed media-edge workload, but it is not causally linked to the requests or processor command execution. The detector's immutable state is confirmed and is consistent with the evidence.
This is likely a true positive for repeated attempted exploitation, not proof of successful command execution. Two captured PUT requests to target privatekind, five minutes apart and associated with the same derived source cluster, each triggered the high-severity command-injection-attempt detector for shell metacharacters with command tokens [[redacted]; [redacted]]. The incident further attributes the second request to targeting an application environment file [[redacted]]. Both requests received HTTP 200 with empty response bodies, but status alone does not establish execution. No cited process or flow events were available to validate a workload consequence or outbound activity.
Real process activity is confirmed, but malicious intent or compromise is not. Event-driven telemetry directly observed root-run dash shells in the processor workload, including repeated shells from the same parent lineage. An exact lifecycle record shows one observed shell exited successfully. Separate root-run processes accessed a shared resource. However, no HTTP or flow evidence is cited, and the bounded summaries do not expose command arguments, resource contents, or an initiating actor. The short-lived, repeated shell pattern could be normal worker or administrative activity. Exploitation, persistence, host escape, lateral movement, command-and-control, and data theft are not established.
Likely true positive for suspicious workload-level execution, but not a proven externally initiated exploit. Event-driven telemetry directly observed repeated root-run dash shells, discovery activity, a sensitive-file-targeting shell, and execution from an inventory-resolved shared resource in the same workload context [redacted]. The repeated common parent PID may indicate an application service or administrative automation rather than a remote actor, and no HTTP or flow evidence was available to establish origin, request-to-process causality, or network consequences. At least one observed shell had an exact exit event with a zero outcome; that establishes process completion only, not benign intent or exploit causality [redacted].
The immutable detector state is confirmed, and the evidence supports that conclusion. A command-injection request returned non-reflected root/UID 0 process output and kernel identification in the same captured HTTP transaction, proving command execution despite HTTP 400 (HTTP [redacted]). A separate injection request returned non-reflected OS-release and kernel data (HTTP [redacted]). Event-driven process telemetry also observed a root dash shell spawning id and later root processes targeting a sensitive resource and performing mutation, execution, and access operations. HTTP-to-process attribution remains temporal/workload-based rather than a unique causality edge. No cited flow event was available, so outbound communication, C2, or exfiltration is not established.
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.
Likely true positive for suspicious root-level workload activity, but not proof of remote exploitation. Event-driven process telemetry recorded a root dash shell and child shell, repeated root discovery-class env executions, and a root process associated with mutation of an inventory-resolved shared resource [redacted]. The first two shells exited successfully within milliseconds [redacted]. Attribution and intent remain unresolved because no correlated HTTP evidence or cited flow evidence is available and exact arguments are excluded from the summaries.
The incident reflects real, high-risk process activity in the protected image-host workload: root-run dash shells, a root cat child classified as targeting a sensitive file, and a root shell associated with mutation of an inventory-resolved shared resource. Exact lifecycle evidence also shows sampled shells exited, with both zero and nonzero outcomes. However, the available evidence does not establish who initiated the activity, whether it was authorized workload/administrative behavior, or whether exploitation occurred. No HTTP request is cited as correlated, and no cited flow evidence is available to assess network consequences. Escalation and workload-owner validation are warranted, but compromise cannot be adjudicated from these process observations alone.
The detector's immutable state is confirmed, and this assessment agrees. Repeated injection-shaped requests produced non-reflected server identity and kernel output showing UID 0/root execution on the responding workload, including in HTTP 400 responses; the status codes do not negate execution [redacted]. Event-driven telemetry also observed root shells, discovery commands, sensitive-file targeting, and operations on an inventory-resolved shared resource [redacted]. HTTP-to-process causality remains temporal/workload-based rather than a unique trace edge, so the verdict proves RCE in the responding workload but not host escape, persistence, lateral movement, C2, or exfiltration.
Likely true positive for suspicious root-context execution inside the protected processor workload. Verified process telemetry shows a root dash shell spawning root discovery activity, followed later by repeated root shells classified as targeting sensitive files and additional discovery execution. Exact lifecycle evidence shows several processes exited, including zero exits, but that proves only process completion—not successful sensitive-data access or malicious intent. No HTTP- or flow-plane evidence reference was available to establish the originating action, actor, request causality, or network consequence.
The incident is likely a true positive for suspicious command execution inside the protected workload. Event-driven telemetry independently observed repeated root-run dash shells, discovery-classified shell executions, and root-run cat processes targeting sensitive files. This is materially stronger than a payload-only alert, although maliciousness and initial access are not proven: no usable HTTP or flow evidence is cited, command arguments and file identities are unavailable, and legitimate administrative or workload activity remains possible.
The detector's immutable state is confirmed with classification confirmed_compromise, and the evidence supports that result: an exploit request/response exchange returned non-reflected process identity output showing root/UID 0, proving command execution in the responding workload despite HTTP 400. Root shell and discovery executions, sensitive-file-targeting commands, and outbound-capable process activity were also observed in correlated workload/time windows. The evidence does not establish host escape, persistence, data theft, or actual outbound socket activity.
The detector's critical suspicious-activity output is supported at the process-observation level: event-driven root `dash` executions occurred repeatedly, one was classified as both a shell and network client, and later root processes executed/accessed inventory-resolved shared resource [redacted] (process evidence [redacted], [redacted], [redacted], [redacted], [redacted], [redacted]; inventory evidence [redacted]). However, the bounded evidence exposes neither command arguments/content nor a causal originating action. No incident-cited HTTP or flow event was available to establish exploitation or an outbound connection. The same observations could reflect unauthorized execution or legitimate processor/administrative behavior, so compromise cannot be adjudicated from the available evidence.
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.
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.
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.
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.
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.
Repeated command-injection HTTP activity was followed within the correlated windows by event-driven root shell, discovery, sensitive-target, and shared-resource process activity. The strongest sequences are: a suspicious PUT targeting the system account database followed about 2.4 seconds later by root dash and env execution [redacted], and later suspicious GETs followed within hundreds of milliseconds by root shell mutation/execution of the same shared resource and, in the final sequence, a parent-linked dash→dash→cat sensitive-target chain [redacted]. This strongly supports successful workload-level command execution, but request-to-process causality remains inferential rather than a unique trace edge. No flow-plane event was available, so no network consequence is assessed.
Three repeated command-injection-shaped GET requests to the same API endpoint were followed within the request windows by recurring root shell/discovery process chains. The final sequence shows the same shared resource being mutated in one workload and then executed in another, followed by a root cat process targeting sensitive material and exiting zero. This strongly supports successful command execution rather than a request-only attempt. The verdict remains “likely” rather than definitive because workload/time correlation does not provide a unique request-to-process trace edge, response content is unavailable, and no cited flow evidence establishes outbound communication.
Likely successful command-injection exploitation, not merely an attempt. Three HTTP events from the same derived source cluster contained shell metacharacters and command tokens; the last was followed about 281 ms later by an event-driven root dash exec in the correlated processor workload, with a root discovery child. The processor-side lineage mutated shared resource [redacted]; shortly afterward, root dash processes in a different workload mutated and executed that same resource. This sequence is highly suspicious and supports actual workload command execution and shared-resource impact. However, correlation is based on routing/workload affinity and time proximity rather than a unique request-to-process trace, so the initiating HTTP request cannot be proven as the sole cause. The incident remains detector-classified as attempted_exploitation/open; this assessment elevates the likely observed consequence while preserving that causality limitation. No flow evidence is cited by the incident, so outbound network consequences are not established.
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.
Verified process telemetry establishes two short-lived parent/child pairs of root-run dash shell executions in the same workload, approximately 63 seconds apart ([redacted], [redacted], [redacted], [redacted]). The second pair was associated with execution from inventory-resolved shared resource [redacted]. Exact lifecycle evidence shows all four processes exited quickly: the first pair nonzero and the second pair zero. This is security-relevant execution, but the bounded evidence contains no correlated HTTP event, cited network-flow event, command arguments, or actor attribution. It therefore cannot distinguish exploitation from expected image-host, automation, or administrative activity. The incident's critical suspicious-activity detector output remains intact, but malicious compromise is not established.