# Claude-assisted IoT security camera credential scraping toolkit

- ID: anthropic-iot-camera-cred-scrape-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-iot-camera-cred-scrape-2025-03/
- Entry JSON: https://openattacks.ai/api/attacks/anthropic-iot-camera-cred-scrape-2025-03.json
- Browse title: Claude-assisted IoT security camera credential scraping toolkit
- Editorial summary: An actor used Claude to build tooling that tests leaked IoT camera credentials against internet-facing devices. Anthropic did not confirm successful 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-iot-camera-cred-scrape-2025-03.json

## Evidence qualification
Capability development assisted by Claude; Anthropic did not confirm successful real-world deployment.

## Technique
Actor used Claude to rewrite scraping toolkit, scrape target URLs, process stealer-log Telegram posts, and improve UI/backend for testing leaked IoT camera credentials against internet-facing devices.

## 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
- commercial breach data platforms
- Telegram stealer log communities

## Victims and sectors
Potential IoT/security camera owners (deployment unconfirmed)

## Target geography
- unknown

## Attribution
unknown sophisticated actor

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Leaked credentials and target URLs [access]
The actor processes URLs and Telegram stealer-log posts.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-2: Claude rewrites the toolkit [ai]
Claude helps improve scraping, processing and the toolkit interface.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-3: Credentials are tested [execution]
The toolkit tests leaked camera credentials against internet-facing devices.
Evidence: https://www.anthropic.com/news/detecting-and-countering-malicious-uses-of-claude-march-2025

### step-4: Victim impact is undisclosed [unknown]
The supplied report does not establish a confirmed set of compromised cameras.
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: Review credential-processing requests in provider/operator records. This does not establish successful camera access.
- 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: Credential / session use outside baseline
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/identity.sigma.yml
- KQL query download: /api/detections/identity.kql
- SPL query download: /api/detections/identity.spl
- Hunt hypothesis: Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
- Required telemetry: Identity / service authentication logs; Device, source-IP and session context; Resource access and token issuance audit
- Investigate: Compare failures, successes and session reuse by account and source; inspect access to new resources.
- Investigate: Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
- Limitation: Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
- 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
Rotate default/IoT credentials; block internet exposure of cameras

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