Anthropic Organization User Invite Sent
Description
Sending an organization user invite creates a path for a new member to join the Anthropic tenant with a chosen role. An adversary who compromises an administrator or admin API key can invite a mailbox they control and accept the invite to gain durable access. Invites may target internal corporate addresses or external domains; this rule does not distinguish them because invite events do not carry verified organization domains for reliable comparison.
Query · esql
from logs-anthropic.audit-* metadata _id, _version, _index
| where
data_stream.dataset == "anthropic.audit" and
mv_contains(event.category, "iam") and
event.action == "org_user_invite_sent" and
event.outcome == "success"
| keep _id, _version, _index, @timestamp, event.*, organization.*, user.*, related.*, source.*, user_agent.*, anthropic.audit.*, data_stream.*
Investigation fields
Pivot points the source recommends for triage.
@timestampevent.actionevent.idevent.outcomeorganization.iduser.target.emailrelated.useranthropic.audit.invited_roleanthropic.audit.invite_idanthropic.audit.actor.typeanthropic.audit.actor.admin_api_key_iduser.emailuser.idsource.ipuser_agent.original
Known false positives
- IT administrators and hiring workflows routinely invite new members during onboarding, contractor access, or staffing changes. Verify the invited email, role, and that a hiring or access request exists when policy requires one.
Analyst notes
Investigating Anthropic Organization User Invite Sent
A successful org_user_invite_sent creates a path for a new member. Invitee is user.target.email (also
related.user); role on accept is anthropic.audit.invited_role when present. Audit events do not include the org's
verified domain list — domain judgment is triage's job.
Unauthorized / high priority: invitee domain outside known corporate domains, invited_role of admin (or similarly
privileged), actor is unexpected / API key, or invite followed by accept + privileged activity. Close as FP when HR/IT
ticket names the invitee and role.
Possible investigation steps
- Compare invitee domain to trusted corporate domains; treat unexpected external domains as higher priority.
- Branch actor:
user_actor(email/IP/UA) vsadmin_api_key_actor(anthropic.audit.actor.admin_api_key_idin inventory?). - Search for
org_user_invite_acceptedfor the sameanthropic.audit.invite_idor invitee email. - Look nearby for role grants, SSO changes, or admin API key creation from the same actor.
False positive analysis
- Routine onboarding invites are FP when an HR/IT ticket names the invitee domain and
invited_role.
Response and remediation
- On unauthorized invite: delete/revoke the pending invite (and remove the user if already accepted), review other IAM changes by the same actor, and rotate compromised admin credentials or API keys.