Potential Sidecar Injection Into Running Deployment
Detects attempts to inject a sidecar container into a running deployment. A sidecar container is an additional container within a pod, that resides alongside the main container. One way to add containers to running…
Description
Detects attempts to inject a sidecar container into a running deployment. A sidecar container is an additional container within a pod, that resides alongside the main container. One way to add containers to running resources like Deployments/DeamonSets/StatefulSets, is via a "kubectl patch" operation. By injecting a new container within a legitimate pod, an attacker can run their code and hide their activity, instead of running their own separated pod in the cluster.
Detection logic
Detection requirements
- Platform
- Containers
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source product
- kubernetes
- Log source category
- application
- Log source service
- audit
Known benign triggers
- Unknown
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| kubernetes.io/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch | Only this detection cites it |
| microsoft.github.io/Threat-Matrix-for-Kubernetes/techniques/Sidecar%20Injection/ | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- ad9012a6-e518-4432-9890-f3b82b8fc71f
- Tagged by the source as
- attack.execution
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1