Anthropic High File Upload Activity
Description
Detects an unusually high volume of Claude file uploads from the same user email and source IP within a rolling 24-hour period. Sustained upload activity can indicate staging of sensitive documents in Claude chats for later retrieval, automated ingestion of data into LLM workflows, or abuse of organizational Claude access to move files into the cloud service.
Query · esql
from logs-anthropic.audit-*
| where
data_stream.dataset == "anthropic.audit" and
event.action == "claude_file_uploaded" and
event.outcome == "success" and
user.email is not null and
source.ip is not null
| stats
Esql.event_count = count(*),
Esql.event_id_values = values(event.id),
Esql.file_name_values = values(file.name),
Esql.anthropic_audit_claude_file_id_values = values(anthropic.audit.claude_file_id),
Esql.anthropic_audit_claude_chat_id_values = values(anthropic.audit.claude_chat_id),
Esql.anthropic_audit_claude_project_id_values = values(anthropic.audit.claude_project_id),
Esql.user_agent_original_values = values(user_agent.original),
Esql.anthropic_audit_actor_type_values = values(anthropic.audit.actor.type),
Esql.timestamp_first_seen = min(@timestamp),
Esql.timestamp_last_seen = max(@timestamp)
by user.email, source.ip
| where Esql.event_count >= 100
| keep user.email, source.ip, Esql.*
Investigation fields
Pivot points the source recommends for triage.
user.emailsource.ipEsql.event_countEsql.event_id_valuesEsql.file_name_valuesEsql.anthropic_audit_claude_file_id_valuesEsql.anthropic_audit_claude_chat_id_valuesEsql.anthropic_audit_claude_project_id_valuesEsql.user_agent_original_valuesEsql.anthropic_audit_actor_type_valuesEsql.timestamp_first_seenEsql.timestamp_last_seen
Known false positives
- Developers, analysts, or knowledge workers bulk-uploading documents during migrations, evaluations, or large project onboarding can exceed the daily threshold from a single workstation or VPN egress.
Analyst notes
Investigating Anthropic High File Upload Activity
One user.email + source.ip pair uploaded a large volume of Claude files in 24 hours — possible staging for later
retrieval, automated ingestion, or abuse of org Claude access.
Unauthorized / escalate when filenames look sensitive, uploads target shared/sensitive projects, UA looks automated (curl/python vs browser), or artifact sharing / exports follow. Close as FP for documented migrations, RAG pilots, or batch attach jobs with expected project IDs.
Possible investigation steps
- Start with
Esql.event_count,Esql.file_name_values, and chat/project ID lists — sensitive names or shared project IDs raise priority. - Triage
user_agenton raw uploads: browser-like vs scripting clients. Scripting UAs with many distinct file IDs look more like automation than interactive work. - Pivot raw
logs-anthropic.audit-*for individualanthropic.audit.claude_file_id/ filenames and whetherclaude_file_viewedor chat activity matches the upload volume. - Correlate with artifact sharing, data exports, or compliance key creation from the same user.
False positive analysis
- Document migrations and RAG indexing from one seat commonly exceed the threshold.
Response and remediation
- On unauthorized staging: revoke sessions, review uploaded names/file IDs for sensitive content, and tighten project sharing or upload policy for the actor.