# Microsoft detects LLM-obfuscated SVG phishing that hid code behind business terminology

- ID: microsoft-detects-llm-obfuscated-svg-phishing-2025-09
- Reported: 2025-09-24
- Researcher: unknown
- Organization: Microsoft Threat Intelligence
- AI role: llm_generated_malware (LLM-generated malware)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: not assessed
- Entry page: https://openattacks.ai/attacks/microsoft-detects-llm-obfuscated-svg-phishing-2025-09/
- Entry JSON: https://openattacks.ai/api/attacks/microsoft-detects-llm-obfuscated-svg-phishing-2025-09.json
- Browse title: Microsoft detects LLM-obfuscated SVG phishing that hid code behind business terminology
- Editorial summary: An SVG credential-phishing lure used likely LLM-written code that encoded its payload as sequences of business words.
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/microsoft-detects-llm-obfuscated-svg-phishing-2025-09.json

## Technique
An SVG credential-phishing lure used likely LLM-written code that encoded its payload as sequences of business words.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
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
- Unspecified LLM (code assessed as AI-generated)

## Other tooling
- unknown

## Victims and sectors
Multiple sectors

## Target geography
- unknown
Target geography was not captured by the Notion feed. Actor attribution is not used as a victim location.

## Attribution
unknown

## Scale and metrics
unknown

## Attack flow
Summary diagram derived from entry fields; a detailed sequence has not been supplied.
### entry: Reported initial access [unknown]
unknown
Evidence: https://microsoft.com/en-us/security/blog/2025/09/24/ai-vs-ai-detecting-an-ai-obfuscated-phishing-campaign ; https://www.helpnetsecurity.com/2025/09/25/microsoft-spots-llm-obfuscated-phishing-attack/ ; https://thehackernews.com/2025/09/microsoft-flags-ai-driven-phishing-llm.html

### activity: Reported activity [execution]
An SVG credential-phishing lure used likely LLM-written code that encoded its payload as sequences of business words.
Evidence: https://microsoft.com/en-us/security/blog/2025/09/24/ai-vs-ai-detecting-an-ai-obfuscated-phishing-campaign ; https://www.helpnetsecurity.com/2025/09/25/microsoft-spots-llm-obfuscated-phishing-attack/ ; https://thehackernews.com/2025/09/microsoft-flags-ai-driven-phishing-llm.html

### ai: AI involvement [ai]
Unspecified LLM (code assessed as AI-generated)
Evidence: https://microsoft.com/en-us/security/blog/2025/09/24/ai-vs-ai-detecting-an-ai-obfuscated-phishing-campaign ; https://www.helpnetsecurity.com/2025/09/25/microsoft-spots-llm-obfuscated-phishing-attack/ ; https://thehackernews.com/2025/09/microsoft-flags-ai-driven-phishing-llm.html

Connections:
- entry -> activity
- ai -> activity (AI context)

## 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.
### entry: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### activity: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### ai: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- 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.
No source-backed mapping is currently recorded.

## Defensive notes
unknown

## Sources
- https://microsoft.com/en-us/security/blog/2025/09/24/ai-vs-ai-detecting-an-ai-obfuscated-phishing-campaign
- https://www.helpnetsecurity.com/2025/09/25/microsoft-spots-llm-obfuscated-phishing-attack/
- https://thehackernews.com/2025/09/microsoft-flags-ai-driven-phishing-llm.html

## Source notes
Imported from the AI Threat Watch Notion feed (an automated daily scan); not yet editorially reviewed. Feed severity: Medium. Feed novelty: Evolution.
