# Novice actor LLM-enabled malware builder progression

- ID: anthropic-novice-malware-builder-2025-03
- Reported: 2025-04-23
- Researcher: Anthropic Threat Intelligence
- Organization: Anthropic
- AI role: llm_generated_malware (LLM-generated malware)
- Confidence in AI involvement: not assessed
- Research / borderline: true
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/anthropic-novice-malware-builder-2025-03/
- Entry JSON: https://openattacks.ai/api/attacks/anthropic-novice-malware-builder-2025-03.json
- Browse title: Novice actor uses Claude to build a GUI malware builder
- Editorial summary: A low-skill actor used Claude to advance from batch scripts to a malware builder focused on evasion and persistence. Anthropic did not confirm real-world deployment.
- Evidence class (catalog annotation): Provider report
- Source-stated target environments: Provider-side
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/anthropic-novice-malware-builder-2025-03.json

## Evidence qualification
Capability elevation case; Anthropic did not confirm real-world deployment.

## Technique
Limited-skill actor used Claude to evolve from basic batch scripts to GUI malware builder focused on evasion and persistence, plus doxing/remote-access tooling with facial recognition and dark-web scanning features.

## 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
unknown

## AI tooling and models
- [Claude](https://claude.com/product/overview)

## Other tooling
- unknown

## Victims and sectors
unknown

## Target geography
- unknown

## Attribution
unknown

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Limited-skill actor requests help [access]
The actor starts with basic batch-script development.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-2: Claude assists iteration [ai]
Model assistance supports increasingly complex malware tooling.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-3: GUI builder takes shape [execution]
The reported builder adds evasion, persistence and remote-access features.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-4: Deployment is not established [unknown]
The entry describes tool development rather than a confirmed victim intrusion.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

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: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
- Qualification: Development requests require provider-side visibility; do not infer deployed malware from a request.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: 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.


## 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.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

## Defensive notes
Model abuse detection; classic malware detections still apply to outputs

## Sources
- https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025
