Claude-assisted IoT security camera credential scraping toolkit
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.
What happened
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.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Capability development assisted by Claude; Anthropic did not confirm successful real-world deployment.
- 01 · Leaked credentials and target URLs
The actor processes URLs and Telegram stealer-log posts.
Hunt: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
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.
Source for step 1 - 02 · Claude rewrites the toolkit
Claude helps improve scraping, processing and the toolkit interface.
Hunt: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
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.
Source for step 2 - 03 · Credentials are tested
The toolkit tests leaked camera credentials against internet-facing devices.
Hunt: Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
Source for step 3 - 04 · Victim impact is undisclosed
The supplied report does not establish a confirmed set of compromised cameras.
Source for step 4
Why it matters
Reported impact: the cited report does not establish a confirmed victim outcome; reported targets include Potential IoT/security camera owners (deployment unconfirmed); using the named AI products does not by itself establish exposure.
What you can do
Protection & prevention
Rotate default/IoT credentials; block internet exposure of cameras
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
01Leaked credentials and target URLsProvider-side abuse investigationCustom schema · Draft
The actor processes URLs and Telegram stealer-log posts.
What to look for
A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Review credential-processing requests in provider/operator records. This does not establish successful camera access.
Visibility: Provider / operator records
Required logs
- Provider-owned account / request audit
- Abuse-review findings and linked-account context
- Lawfully available exposed operator-session evidence
Coverage limit. 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.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Provider-side abuse investigation
id: c8c1edc0-c79a-4644-a876-2c1a6cb9a438
status: experimental
description: A model-provider investigation correlates related accounts,
repeated offensive requests and shared infrastructure or exposed operator
sessions.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- model.request
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("model.request")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("model.request")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
02Claude rewrites the toolkitProvider-side abuse investigationCustom schema · Draft
Claude helps improve scraping, processing and the toolkit interface.
What to look for
A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Visibility: Provider / operator records
Required logs
- Provider-owned account / request audit
- Abuse-review findings and linked-account context
- Lawfully available exposed operator-session evidence
Coverage limit. 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.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Provider-side abuse investigation
id: c8c1edc0-c79a-4644-a876-2c1a6cb9a438
status: experimental
description: A model-provider investigation correlates related accounts,
repeated offensive requests and shared infrastructure or exposed operator
sessions.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- model.request
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("model.request")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("model.request")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
03Credentials are testedCredential / session use outside baselineCustom schema · Draft
The toolkit tests leaked camera credentials against internet-facing devices.
What to look for
Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
Visibility: Defender-side logs where collected
Required logs
- Identity / service authentication logs
- Device, source-IP and session context
- Resource access and token issuance audit
Coverage limit. Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Credential / session use outside baseline
id: 7d73d919-e785-4d40-ab0b-f12949adfaf5
status: experimental
description: Repeated credential attempts or a stolen session are followed by a
successful login or resource access inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- identity.login
- identity.token.use
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("identity.login", "identity.token.use")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("identity.login", "identity.token.use")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Compare failures, successes and session reuse by account and source; inspect access to new resources.
- Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
Tooling as reported
AI products, models and artifacts
Other tooling
- commercial breach data platforms
- Telegram stealer log communities
Targets and reported impact
- Targets / sectors
- Potential IoT/security camera owners (deployment unconfirmed)
Reported attribution
unknown sophisticated actor
Structured attribution
- Actor
- unknown sophisticated actor
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in Claude-assisted IoT security camera credential scraping toolkit. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Rotate default/IoT credentials; block internet exposure of cameras
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
The supplied source explicitly describes generative-model tooling assisting the reported activity; this mapping does not establish additional autonomy or victim impact. Source
Sources & research credit
1 sourceResearch by Anthropic Threat Intelligence · Anthropic
Record & downloads
- Source record name
- Claude-assisted IoT security camera credential scraping toolkit
- Entry ID
- anthropic-iot-camera-cred-scrape-2025-03
- Catalog review
- October 20, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- unverified