# Storm-2139 / FizzDogg Azure OpenAI LLMjacking (Microsoft DCU)

- ID: storm-2139-fizzdogg-microsoft-llmjacking-2024-12
- Reported: 2024-12-19
- Researcher: Microsoft Digital Crimes Unit
- Organization: Microsoft
- AI role: ai_credential_theft (AI credential theft)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/storm-2139-fizzdogg-microsoft-llmjacking-2024-12/
- Entry JSON: https://openattacks.ai/api/attacks/storm-2139-fizzdogg-microsoft-llmjacking-2024-12.json
- Browse title: Storm-2139 / FizzDogg Azure OpenAI LLMjacking (Microsoft DCU)
- Editorial summary: A Microsoft civil action alleges the group stole Azure OpenAI credentials and bypassed safety controls to generate harmful images at victims' expense.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Cloud & SaaS
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/storm-2139-fizzdogg-microsoft-llmjacking-2024-12.json

## Technique
Microsoft civil action against Storm-2139 (FizzDogg) network alleged theft of Azure OpenAI credentials and custom tooling to bypass safety controls and generate harmful images via DALL-E/GenAI services at victims' expense.

## Stack relevance (editorial)
Assessment: mapped. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
First action: Review Azure OpenAI key ownership, rotate exposed credentials and investigate unexpected usage.
- Relationship: credential; tools: ai-api-keys; OS scope: not OS-specific / not stated; requires existing MCP connections: false.
  Relevance: The civil-action account concerns stolen Azure OpenAI credentials and usage charged to victim resources.
  Condition to check: Confirm that you operate Azure OpenAI resources and store keys or tokens that could be exposed.
  Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
unknown

## AI tooling and models
- [Azure OpenAI](https://azure.microsoft.com/en-us/products/ai-foundry/models/openai/)
- DALL-E

## Other tooling
- unknown

## Victims and sectors
unknown

## Target geography
- unknown

## Attribution
Storm-2139 / FizzDogg

## Scale and metrics
unknown (litigation)

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Theft route is not detailed in the seed [unknown]
Microsoft’s civil case alleges stolen Azure OpenAI credentials.
Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/

### step-2: Stolen keys access victim resources [access]
The credentials provide unauthorized access to generative services.
Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/

### step-3: Custom tooling bypasses safety controls [ai]
The alleged operation generates harmful content through DALL-E and related services.
Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/

### step-4: Victim accounts bear the usage [impact]
The civil action describes unauthorized model use at account owners’ expense.
Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/

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: No source-backed runtime hunt yet
- Visibility: Not established
- Query origin: catalog_authored; status: not_applicable; log scope: gap
- Hunt hypothesis: The supplied account does not establish a deployed victim-side behavior for this stage.
- Required telemetry: not assessed
- Investigate: Obtain a source-backed procedure and identify which party could observe it before drafting a detection.
- Limitation: Marketing claims, unknown steps and unconfirmed deployments are not detection coverage. No rule is generated for this stage.
- Qualification: The supplied account leaves this stage unestablished. Obtain a source-backed procedure before proposing a runtime query.
- 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: 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.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0012: Valid Accounts — The civil case alleges use of stolen Azure OpenAI credentials.
  Technique: https://atlas.mitre.org/techniques/AML.T0012
  Evidence: https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/

## Defensive notes
Protect Azure OpenAI keys; monitor anomalous image/model invocation

## Sources
- https://www.microsoft.com/en-us/corporate-responsibility/customer-security-trust/digital-crimes-unit/notice-of-pleadings/storm-2139/
