Query Details
// Social Engineering Attack (Mail Bomb followed by Social Engineered Call - Initial access via RMM Tool)
// https://admin.microsoft.com/?ref=MessageCenter/:/messages/MC1096885
let MailBombVictim =
EmailEvents
| where TimeGenerated > ago(1h)
| where isnotempty(DetectionMethods)
| where tostring(DetectionMethods) has "Mail Bombing"
| distinct RecipientEmailAddress;
let ApprovedRMM = dynamic("bomgarcloud.com"); // E.g Approved Corporate RMM - Whitelisting
let RMMList=externaldata(URI: string, RMMTool: string) // Lookup list of RMM Tools Url from Microsoft
[h'https://raw.githubusercontent.com/jischell-msft/RemoteManagementMonitoringTools/refs/heads/main/Network%20Indicators/RMM_SummaryNetworkURI.csv'];
let RMMUrl =
RMMList
| project URI;
DeviceNetworkEvents
| where TimeGenerated > ago(1h)
| where ActionType == @"ConnectionSuccess"
| where RemoteUrl has_any(RMMUrl)
| where not (RemoteUrl has_any(ApprovedRMM)) // Unauthorized Outbound RMM Tool Connection
| summarize arg_max(TimeGenerated, *) by DeviceId
| where InitiatingProcessAccountUpn has_any(MailBombVictim) // RMM Tool Connection made by Mail Bomb Victim
This query is designed to detect a specific type of social engineering attack that involves a mail bombing followed by a social engineering call, ultimately leading to unauthorized access via a Remote Monitoring and Management (RMM) tool. Here's a simplified breakdown:
Identify Mail Bomb Victims:
Approved RMM Tools:
Fetch RMM Tool URLs:
Detect Unauthorized RMM Connections:
Correlate with Mail Bomb Victims:
In essence, the query aims to detect if a user who was targeted by a mail bomb attack subsequently made an unauthorized connection to an RMM tool, which could indicate a successful social engineering attack leading to unauthorized access.

Steven Lim
Released: June 18, 2025
Tables
Keywords
Operators