# Wiz CIRT AI-driven multi-cloud intrusions

- ID: wiz-ai-driven-cloud-2026-10
- Reported: 2026-10-19
- Researcher: Eden Abergil, Zohar Kaplan, Kurt Giacchino
- Organization: Wiz CIRT
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/wiz-ai-driven-cloud-2026-10/
- Entry JSON: https://openattacks.ai/api/attacks/wiz-ai-driven-cloud-2026-10.json
- Browse title: Wiz CIRT: AI-driven multi-cloud intrusions
- Editorial summary: An AI agent ran a noisy, full multi-cloud intrusion from initial access to data theft. The same source IP scanned 600+ other Wiz customer environments.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Cloud & SaaS
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/wiz-ai-driven-cloud-2026-10.json

## Technique
AI agent ran full cloud operations: initial access, credential theft, pivots across GCP/AWS/K8s/CI-CD/IdP, debugging its own scripts. Loud (thousands of actions/hour), pentest-named resources, numeric task IDs with -b/-c retries, commented generated scripts. Lived off SSM, SA token minting, IdP admin creation, GitOps manifests, runner-log exfil.

## Stack relevance (editorial)
Assessment: attacker\_tool\_only. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
The named AI product is used by the attacker. No reviewed mapping from owning that product to the reported victim conditions is available.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Confirmed Java RCE in exposed Kafka UI among multiple probed doors; same source IP scanned 600+ other Wiz customer environments

## AI tooling and models
- Unnamed AI agent system (Wiz: agent ran the whole operation)

## Other tooling
- Kafka UI exploit
- [SSM](https://aws.amazon.com/systems-manager/)
- GCP SA token creation
- IdP admin APIs
- CI/CD pipelines
- GitOps/K8s manifests
- [webhook.site](https://github.com/webhooksite/webhook.site)
- IMDS credential harvest

## Victims and sectors
Large multi-cloud organization (Wiz customer); opportunistic scanning across many other customers

## Target geography
- unknown

## Attribution
unknown

## Scale and metrics
Hundreds–thousands of actions per hour; 600+ environments scanned from same IP

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Exposed Kafka UI is exploited [access]
The report confirms a Java RCE route among multiple probed entry points.
Evidence: https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks

### step-2: Agent executes and debugs cloud operations [ai]
The automation generates and retries scripts at high volume.
Evidence: https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks

### step-3: Credentials enable cross-service pivots [execution]
Reported paths span cloud accounts, Kubernetes, identity and CI/CD.
Evidence: https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks

### step-4: Data leaves through operational channels [impact]
The research describes runner-log exfiltration and abuse of legitimate cloud-management capabilities.
Evidence: https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Web exploitation → host activity
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/web.sigma.yml
- KQL query download: /api/detections/web.kql
- SPL query download: /api/detections/web.spl
- Hunt hypothesis: Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
- Required telemetry: Reverse-proxy / WAF request logs; Server process and file events; Outbound DNS / proxy records
- Investigate: Join requests to the affected host and process tree by time and request ID.
- Investigate: Inspect uploaded files and server-spawned shells; distinguish authorized testing from exploitation.
- Limitation: A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Unexpected cloud / inference identity use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/cloud.sigma.yml
- KQL query download: /api/detections/cloud.kql
- SPL query download: /api/detections/cloud.spl
- Hunt hypothesis: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
- Required telemetry: Cloud control-plane and identity audit; AI-service invocation / diagnostic logs when enabled; Usage, quotas, cost and key inventory
- Investigate: Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Investigate: Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
- Limitation: Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Unexpected cloud / inference identity use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/cloud.sigma.yml
- KQL query download: /api/detections/cloud.kql
- SPL query download: /api/detections/cloud.spl
- Hunt hypothesis: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
- Required telemetry: Cloud control-plane and identity audit; AI-service invocation / diagnostic logs when enabled; Usage, quotas, cost and key inventory
- Investigate: Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Investigate: Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
- Limitation: Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: Sensitive data → unusual destination
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/exfil.sigma.yml
- KQL query download: /api/detections/exfil.kql
- SPL query download: /api/detections/exfil.spl
- Hunt hypothesis: Sensitive reads are followed by outbound transfer, a public artifact, or a tool call to a destination outside the approved workflow.
- Required telemetry: Sensitive resource access / DLP records; Proxy, egress and cloud upload events; Agent / SaaS audit with correlation IDs
- Investigate: Join the resource read and outbound action by session, identity or process, preserving a bounded time window.
- Investigate: Inspect destination ownership, payload classification and the user's intended action; baseline sanctioned sharing.
- Limitation: An outbound connection or high byte count alone is not exfiltration. Encrypted traffic may hide content, and bulk legitimate exports are common.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0016.002: Generative AI — The supplied source explicitly describes generative-model tooling assisting the reported activity; this mapping does not establish additional autonomy or victim impact.
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks

## Defensive notes
Unify multi-platform logs; runtime visibility on runners/VMs/pods; restrict cross-system trust; rotate credentials on compromise; correlate loud agent tells (pentest- prefixes, task IDs)

## Sources
- https://www.wiz.io/blog/anatomy-of-ai-driven-cloud-attacks
