Suspicious Kubernetes RBAC Binding Granting Access to Anonymous Users

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects kubectl creating a role or cluster role binding whose subject is system:anonymous or system:unauthenticated which grants API privileges to unauthenticated callers. Wiz describes this misconfiguration as a Kubernetes control plane initial access vector. This is important because binding real permissions to the anonymous group exposes the cluster API to anyone who can reach it and is a common path to full cluster compromise.

Related detections9 linkedT1190 — drag to rearrange
Suspicious SmarterMail Force Password Reset API Request Indicating Account Takeover
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Windows Failed Logon (Event ID 4625) From Non-Private Public IP
Suspicious Kubelet Started With Anonymous Auth and AlwaysAllow Authorization
Possible CUPS cups-browsed Remote Code Execution via Shell Child Process
Malicious mshta Execution Spawned by PHP-CGI (CVE-2024-4577)
Possible IngressNightmare Exploitation via NGINX Loading Shared Object From Proc (CVE-2025-1974)
Malicious PHASEJAM Webshell Dropped in Ivanti dana-na Auth Directory
Suspicious Modification of CUPS cups-browsed Configuration File
Suspicious Kubernetes RBAC Binding Granting Access to Anonymous Users
Pivot detection · T1190 · 9 related

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