# Claude-polished Eastern Europe recruitment fraud

- ID: anthropic-recruitment-fraud-2025-03
- Reported: 2025-04-23
- Researcher: Anthropic Threat Intelligence
- Organization: Anthropic
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: true
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/anthropic-recruitment-fraud-2025-03/
- Entry JSON: https://openattacks.ai/api/attacks/anthropic-recruitment-fraud-2025-03.json
- Browse title: Claude-polished recruitment fraud targeting Eastern Europe
- Editorial summary: Recruitment scammers posing as hiring managers used Claude to polish their English and interview scripts. Anthropic did not confirm that any victims were successfully defrauded.
- Evidence class (catalog annotation): Provider report
- Source-stated target environments: Provider-side
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/anthropic-recruitment-fraud-2025-03.json

## Evidence qualification
AI used for language sanitization of scam content; successful victim compromise not confirmed by Anthropic.

## Technique
Recruitment fraud impersonating hiring managers used Claude for real-time language refinement, native-English polishing, interview scripts, and more legitimate-looking formatting.

## 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
Job seekers primarily in Eastern European countries

## Target geography
- Europe
The source describes job seekers in Eastern Europe without naming individual countries.

## Attribution
unknown

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Recruiter identities are impersonated [access]
The fraud targets job seekers with hiring-manager personas.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-2: Claude polishes the dialogue [ai]
Model assistance refines language, interview scripts and formatting.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-3: Fraudulent recruitment messages [execution]
The actor uses more legitimate-looking recruitment communications.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-4: Individual losses are undisclosed [unknown]
The supplied record does not quantify successful fraud or victim losses.
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: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- Qualification: Investigate recruiter identity and message provenance; successful fraud is not established by impersonation alone.
- 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: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- 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
Verify recruiters outside chat channels; AI polish is not proof of legitimacy

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