GKE Pod Exec Potential Reverse Shell
Description
Detects successful GKE pod exec sessions whose command resembles reverse-shell or bind-shell one-liner patterns, including /dev/tcp and /dev/udp redirection, netcat/ncat exec-style flags, socat shell handoff, mkfifo pipelines, and common language socket idioms. Legitimate debug sessions sometimes use similar building blocks, but together these patterns align with post-exploitation interactive access and command-and-control. Common localhost /dev/tcp health-check ports are excluded. GKE records the command in gcp.audit.labels.command.gke.io/command when an explicit command is passed to exec.
Query · kuery
data_stream.dataset:gcp.audit and service.name:"k8s.io" and event.outcome:success and
event.type:start and
event.action:("io.k8s.core.v1.pods.exec.create" or "io.k8s.core.v1.pods.exec.get") and
gcp.audit.labels.command.gke.io/command:(
(
*/dev/tcp/* or */dev/udp/* or */inet/tcp/* or
*0\\\>&1* or
*IO*Socket*INET* or *TCPSocket.new* or *bash*-i* or *fsockopen* or
*import*pty* or *import*socket* or *mkfifo* or
*nc*-c* or *nc*-e* or *netcat*-e* or
*socat*exec* or *socat*pty* or *socket.socket* or
*zsh/net/tcp* or *zsh/net/udp*
) and not (
*127.0.0.1* or *localhost*
)
)
Investigation fields
Pivot points the source recommends for triage.
@timestampclient.user.emailsource.ipuser_agent.originalevent.actionevent.outcomeevent.typegcp.audit.labels.command.gke.io/commandgcp.audit.resource_namedata_stream.namespace
Implementation guide
The GCP Fleet integration with GKE audit logs enabled is required to be compatible with this rule.
Known false positives
- Security training, CTF-style images, or vendor diagnostics may include bash redirection or /dev/tcp examples. Baseline approved images then expand exclusions as needed.
Analyst notes
Investigating GKE Pod Exec Potential Reverse Shell
This alert fires when a successful pods/exec API call includes a command matching reverse/bind-shell idioms.
Review gcp.audit.labels.command.gke.io/command for the reconstructed payload.
Possible investigation steps
- Identify the actor (
client.user.email), source IP, and user agent (human kubectl vs automation). - Resolve the target namespace and pod from
gcp.audit.resource_nameand correlate with workload ownership. - Hunt nearby events from the same identity: secret reads, pods/exec to other workloads, RoleBinding changes.
- Do not replay the command against live infrastructure unless policy explicitly allows a sandboxed recreation.
False positive analysis
- Security training or CTF images may include reverse-shell examples; scope exceptions to those namespaces/images.
- Some observability or mesh sidecars use socat or sockets in overlapping ways; validate image and command lineage.
Response and remediation
- If malicious, terminate the exec session, isolate the workload or node, rotate credentials reachable from the pod, and revoke pods/exec for the abused principal unless strictly required.