« AWS S3 Credential File Retrieved from Bucket Entra ID Microsoft Authentication Broker Sign-In with Non-Standard User Agent »
Elastic Docs ›Elastic Security [8.19] ›Downloadable rule update v8.19.25

Entra ID Kali365 Default User-Agent Detected

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Entra ID Kali365 Default User-Agent Detected

edit

Identifies the default user agent string associated with Kali365 (also referred to as Kali365 Live), a phishing-as-a-service (PhaaS) platform that automates OAuth 2.0 device code phishing and adversary-in-the-middle (AiTM) session capture against Microsoft 365 and Microsoft Entra ID. The Kali365 Electron desktop client identifies itself with the user agent kali365-live/1.0.0 when polling for and replaying captured OAuth tokens, so its appearance in Entra ID sign-in logs, Entra ID audit logs, or the Microsoft 365 unified audit log indicates that an attacker-controlled Kali365 client is interacting with the tenant using stolen tokens. Unlike dual-use offensive tooling, Kali365 is a criminal service with no legitimate enterprise use, making this user agent a high-fidelity indicator of active account compromise.

Rule type: query

Rule indices:

  • logs-azure.auditlogs-*
  • logs-azure.signinlogs-*
  • logs-o365.audit-*

Severity: high

Risk score: 73

Runs every: 5m

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Domain: Cloud
  • Domain: Identity
  • Data Source: Azure
  • Data Source: Microsoft Entra ID
  • Data Source: Microsoft Entra ID Sign-in Logs
  • Data Source: Microsoft Entra ID Audit Logs
  • Data Source: Microsoft 365
  • Data Source: Microsoft 365 Audit Logs
  • Use Case: Identity and Access Audit
  • Use Case: Threat Detection
  • Threat: Kali365
  • Tactic: Initial Access
  • Tactic: Credential Access
  • Resources: Investigation Guide

Version: 1

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit

Triage and analysis

Investigating Entra ID Kali365 Default User-Agent Detected

Kali365 (Kali365 Live) is a phishing-as-a-service platform distributed via Telegram that provides affiliates with AI-generated lures, automated device code phishing campaigns, target-tracking dashboards, and OAuth token capture. The typical flow is: a lure delivers a Microsoft device code, the victim enters it on the legitimate Microsoft verification page and unknowingly authorizes the attacker, Kali365 captures the resulting OAuth access and refresh tokens, and the attacker uses those tokens for persistent, MFA-free access to Microsoft 365 (Outlook, Teams, OneDrive).

The Kali365 desktop client presents the user agent kali365-live/1.0.0. This rule fires when that user agent is observed in Entra ID sign-in logs, Entra ID audit logs, or the Microsoft 365 unified audit log. Because the user agent maps to a criminal service with no legitimate use, an alert generally indicates that stolen tokens are already being replayed against the tenant.

Possible investigation steps

  • Confirm the tool and identify the affected identity.
  • user_agent.original matches kali365-live/*.
  • Pivot on user.name, azure.signinlogs.properties.user_principal_name, or the M365 audit user.id.
  • Review the origin and compare against the user’s normal sign-in behavior.
  • source.ip, source.geo.*, and source.as.organization.name; flag hosting/VPS ASNs and unexpected geographies.
  • Cross-reference published Kali365 infrastructure (216.203.20.95, 162.243.166.119, 199.91.220.111).
  • Confirm the device code grant in sign-in logs.
  • azure.signinlogs.properties.authentication_protocol is deviceCode.
  • Review app_id/app_display_name and resource_display_name for the brokered mail or collaboration API.
  • Scope follow-on access in the Microsoft 365 unified audit log for the same user and timeframe.
  • Look for mailbox access, inbox rule creation, OneDrive/SharePoint downloads, or Teams activity from the same session or IP.
  • Check the Entra ID audit log for a device registration by the same identity around the alert window.
  • A Register device event by the identity paired (via azure.correlation_id) with an Add device event from the Device Registration Service indicates a Primary Refresh Token (PRT) was issued for persistence that survives password resets.

False positive analysis

  • This user agent has no legitimate enterprise use.
  • The only expected matches are authorized security research or red team exercises running the Kali365 client; validate and document before dismissing.

Response and remediation

  • Remove rogue device registrations created by the user BEFORE revoking sessions.
  • Device-bound PRTs survive revokeSignInSessions, so a device left in place re-establishes access.
  • GET /v1.0/users/{id}/registeredDevices and /ownedDevices, then DELETE /v1.0/devices/{deviceObjectId} for unrecognized devices.
  • Revoke refresh tokens and sessions, then reset credentials and re-register MFA.
  • POST /v1.0/users/{id}/revokeSignInSessions.
  • Temporarily disable the account if you need to halt activity during investigation.
  • PATCH /v1.0/users/{id} with body {"accountEnabled": false}.
  • Remove other attacker persistence: malicious inbox/forwarding rules, OAuth consents, and app passwords.
  • Block or monitor Kali365 source IPs and infrastructure, and hunt for the user agent across other users and tenants.
  • Apply Conditional Access to the device code grant.
  • Require a managed/compliant device, or block the device-code flow outside approved app and user populations.

Rule query

edit
data_stream.dataset : ("azure.signinlogs" or "azure.auditlogs" or "o365.audit") and user_agent.original: kali365-live/*

Framework: MITRE ATT&CKTM

« AWS S3 Credential File Retrieved from Bucket Entra ID Microsoft Authentication Broker Sign-In with Non-Standard User Agent »