O365 Email Reported by Admin Found Malicious
Detection of emails manually submitted to Microsoft through the Security & Compliance portal and subsequently identified as malicious (Phish or Malware).
Triage facts
Revision 2- Evidence
- Unknown
- Severity
- High
- Sources
- 1 public source
- Freshness
- Revision 2Jan 2, 10:00 UTC
- Detection
- 2 rules
Revision history 1 entry · Revision 2
- Revision 2
Repaired a legacy canonical identity collision
Changed: slug
This detection focuses on identifying malicious emails within Microsoft 365 environments that have been reported by administrators through the Security & Compliance portal. This feature allows administrators to proactively submit suspicious emails for analysis. The analytic triggers when a submitted email receives a "Phish" or "Malware" verdict upon analysis by Microsoft's systems. This capability is an enhanced protection feature that can be used within o365 tenants by administrative users to report potentially malicious emails. This detection is valuable because it highlights cases where human intuition, combined with automated analysis, confirms a malicious email that may have bypassed initial security filters. This insight allows security teams to quickly respond to potential phishing or malware campaigns.
Attack Chain
- An attacker sends a phishing or malware-laden email to a user within the organization.
- The email bypasses initial security filters and reaches the user's inbox.
- An administrator, suspecting the email is malicious, manually submits the email for analysis through the Microsoft Security & Compliance portal using the Admin Submission feature.
- Microsoft's systems analyze the submitted email, examining its content, links, and attachments.
- The analysis returns a verdict of either "Phish" or "Malware", confirming the malicious nature of the email.
- The "AdminSubmission" event is logged within the Office 365 Unified Audit Log, containing details about the submission, sender, recipients, and the verdict.
- The detection analytic identifies the "AdminSubmission" event with a "Phish" or "Malware" verdict.
- Security teams can investigate the reported email, block the sender, and identify other potentially affected users to prevent further compromise.
Impact
A successful phishing or malware campaign can lead to credential theft, data breaches, and ransomware infections. Even a single successful compromise can have significant financial and reputational consequences. This detection helps identify emails that have bypassed initial security layers, potentially preventing a successful attack.
Recommendation
- Deploy the Sigma rule
O365 Email Reported By Admin Found Maliciousto your SIEM to detect malicious emails reported by administrators. - Investigate any alerts triggered by the
O365 Email Reported By Admin Found Maliciousrule, focusing on the sender and recipients of the reported email. - Block sender addresses associated with confirmed malicious emails at the email gateway (reference the source IP from the logs).
- Correlate
AdminSubmissionevents with other security logs to identify potentially related malicious activities (e.g., failed login attempts, unusual file access). - Configure the Microsoft Office 365 add-on in Splunk to collect the necessary
o365:management:activitylogs.
Detection coverage 2
O365 Email Reported By Admin Found Malicious
highDetects when an email manually submitted to Microsoft through the Security & Compliance portal is found to be malicious.
O365 Admin Submission with Suspicious Subject
mediumDetects O365 Admin Submissions with subject lines commonly used in phishing campaigns.
Detection queries are available on the platform. Get full rules →