In an investigation published October 19, Wiz CIRT described an attacker who exploited an internet-facing Kafka UI to execute commands, deployed a backdoor and harvested workload secrets. The operation continued in several cloud and platform control planes. Stolen and minted identities allowed AWS Organizations access, GCP service-account token issuance,…
Inspect the ClaimsCase · DiggingBeagle record
Wiz reconstructs an AI-directed intrusion crossing cloud, identity and delivery systems
Investigators report a real multi-cloud compromise: an exposed Kafka UI was one entry point, followed by identity-provider escalation, CI/CD execution and data exfiltration.
Wiz CIRT investigated production cloud intrusion disclosed October 19, 2026; affected victim unnamed and wider scan population is not a victim count.
Assessment profile
Assessment method- Setting
- production
- Exploitation
- confirmed in the wild
- Evidence
- Grade B
- AI role
- BY AI
Basis and provenance
The production intrusion and cloud privilege effects are investigator observations, while the exact identity of the model and degree of autonomous control are inferred. Impact band is left unassigned because no calibrated damage threshold or representative victim impact is supported by the available record.
Assessed Oct 20, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-WIZ-ENTRY · CLM-WIZ-SCANS · CLM-WIZ-CREDENTIALS · CLM-WIZ-GITOPS-BYPASS · CLM-WIZ-EXFIL-CHANNELS · Wiz incident reconstruction: Anatomy of a real AI-driven cloud attack
At a glance
Identity and credential scope determine the blast radius; Git review alone cannot detect direct controller state changes made with already compromised deployment authority.
Read the implicationsActual model family, proportion of autonomy and exact attacker supervision are not independently authenticated. Total verified exfiltrated data volume and remediation are not disclosed.
Limits and uncertaintyFull account
In an investigation published October 19, Wiz CIRT described an attacker who exploited an internet-facing Kafka UI to execute commands, deployed a backdoor and harvested workload secrets. The operation continued in several cloud and platform control planes. Stolen and minted identities allowed AWS Organizations access, GCP service-account token issuance, changes to IdP group membership and creation of Kubernetes workloads through CI/CD and GitOps services.
The distinctive AI attribution rests on high-tempo cross-platform workflows, repeated correction after API failures, code-generation artifacts and coordinated workstreams. The report presents observations from real incidents, but it does not publish signed model transcripts for every action. An originating IP also scanned more than 600 other customer environments: scanning is not evidence of 600 compromises. In the investigated victim environment, the attacker used several channels including CI logs, source control, ConfigMaps and an external request collector for data movement. Some routes were blocked or attempted, so total transferred bytes and confirmed losses remain unknown.
The actual foothold and privilege transitions are better established than the precise degree of model autonomy. Wiz describes compromise of an exposed Kafka interface, then abuse of IdP administration, cloud credentials, service accounts and direct GitOps control-plane mutations. A deployed manifest could reach production without an attacker-authored Git commit because an already compromised controller credential could change state directly. The more than 600 additional environments were scanned, not reported compromised.
Mechanism and trust boundary
- 01
Exposed developer service
Kafka UI remote command execution started a foothold and C2.
Boundary: Internet access to application process authority
- 02
Token and role chaining
Workload and IdP credentials became AWS/GCP and Kubernetes administrative powers.
Boundary: One service account to broader federated cloud authority
- 03
Delivery-plane persistence
CI/CD and GitOps execution deployed cluster workloads and exfil channels.
Boundary: Deployment control privileges to runtime and data-plane effects
Timeline
- Oct 19, 2026disclosure
Public disclosure
Claims & evidence
CLM-WIZ-ENTRYWiz observed confirmed Java remote code execution through an exposed Kafka UI instance, followed by shell commands and a command-and-control channel.supported
Basis: reported finding
- supportsWiz incident reconstruction: Anatomy of a real AI-driven cloud attackprimary disclosure
Initial Access: Trying Every Door
CLM-WIZ-SCANSThe same originating IP scanned more than 600 other Wiz customer environments; Wiz did not report 600 additional successful intrusions.supported
Basis: reported finding
- supportsWiz incident reconstruction: Anatomy of a real AI-driven cloud attackprimary disclosure
Initial Access, final paragraph
CLM-WIZ-CREDENTIALSWiz reconstructed abuse of IdP administration, cloud tokens, AWS SSO access, GCP credentials and CI/CD or GitOps service accounts during the investigated intrusion.supported
Basis: reported finding
- supportsWiz incident reconstruction: Anatomy of a real AI-driven cloud attackprimary disclosure
Operating in Cloud Control Plane; Identity Provider; Weaponizing CI/CD and GitOps
CLM-WIZ-GITOPS-BYPASSWiz reports that the attacker used a compromised GitOps deployment service account to change controller-managed workloads directly, including later mutations without corresponding malicious Git commits.supported
Basis: reported finding
- supportsWiz incident reconstruction: Anatomy of a real AI-driven cloud attackprimary disclosure
Weaponizing CI/CD and GitOps; Living Off Kubernetes, direct controller modification
CLM-WIZ-EXFIL-CHANNELSWiz reports transfers or staging through CI logs, source-control commits, Kubernetes ConfigMaps and an external request collector; not every attempted route establishes a measured volume of data loss.supported
Basis: reported finding
- supportsWiz incident reconstruction: Anatomy of a real AI-driven cloud attackprimary disclosure
Data Access and Exfiltration; CI/CD runners and attempted storage buckets
Implications
Identity and credential scope determine the blast radius; Git review alone cannot detect direct controller state changes made with already compromised deployment authority.
Unknowns and contradictions
- Actual model family, proportion of autonomy and exact attacker supervision are not independently authenticated.
- Total verified exfiltrated data volume and remediation are not disclosed.
Sources and citation
Material revision history
- Oct 20, 2026 · Canonical change recorded · new in release · revision 177