Suspicious Helm Tiller Unauthenticated Access on Port 44134

PremiumReviewedSigma · Medium · v1
Product
linux
Category
network_connection
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

ATT&CK techniques

Execution → Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects network connections to TCP port 44134 used by the Helm Tiller gRPC service. Wiz Research found unauthenticated Tiller instances in the SAP AI environment that let an attacker install a malicious chart and obtain a cluster-admin pod, so connections to this port can indicate abuse of an exposed legacy Helm component.

Related detections9 linkedT1610 — drag to rearrange
Possible IngressNightmare Exploitation via NGINX Loading Shared Object From Proc (CVE-2025-1974)
Suspicious Docker Container Spawning Remote Script Download (via process_creation)
Suspicious Docker Socket Access via curl Unix Socket for Container Escape
Suspicious Access To Kubernetes Service Account Token File
Suspicious Kubernetes Pod Deployment with Privileged or Host Namespace Flags
Malicious Container Escape via Privileged Docker Host PID Namespace
Suspicious Kubernetes Secret Enumeration via kubectl
Suspicious Privileged Docker Container Launch With Host chroot
Malicious Docker Client Targeting Remote Exposed 2375 API
Suspicious Helm Tiller Unauthenticated Access on Port 44134
Pivot detection · T1610 · 9 related

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