Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Recon-VishingPretextEmailFollowup.

Upgrade to Pro
THREAT-Recon-VishingPretextEmailFollowup

Low-Signal Pretext Email Followed by Voice Phishing Call to Same Target

Reconnaissance Last updated:

Ahead of a voice-phishing (vishing) attempt, actors frequently send a low-signal reconnaissance or spearphishing-link email to a target employee — often themed as an IT helpdesk notice, password-expiry warning, VPN access request, or service-desk ticket confirmation — that by itself carries little malicious payload (no attachment, a benign or absent link, generic wording) and is easily missed by content-based email filtering. The email's real purpose is to prime the target and establish a plausible pretext ('I'm following up on the ticket I just emailed you about') before the actor places a phone call posing as IT support, a vendor, or a colleague to harvest credentials, MFA codes, or internal information directly from the target. Because neither artifact alone is highly suspicious — a generic IT-themed email and an inbound support call are both routine — the highest-fidelity signal is the temporal correlation between the two: the same recipient receiving a pretext-themed email and then being the subject of an inbound call logged in the PBX/UC platform or a new/updated ticketing-system entry referencing them, within a short window (typically under two hours). Detection focuses on three pillars: (1) identifying low-signal, pretext-themed inbound email to a recipient, (2) correlating that recipient with an inbound call record in PBX/UC/telephony logs shortly afterward, and (3) correlating with a helpdesk/ticketing-system entry created or updated for the same user in the same window, since actors sometimes have the (socially engineered) helpdesk agent open the ticket rather than placing the call themselves.

What is THREAT-Recon-VishingPretextEmailFollowup Low-Signal Pretext Email Followed by Voice Phishing Call to Same Target?

Low-Signal Pretext Email Followed by Voice Phishing Call to Same Target (THREAT-Recon-VishingPretextEmailFollowup) maps to the Reconnaissance tactic — the adversary is trying to gather information they can use to plan future operations in MITRE ATT&CK.

This page provides production-ready detection logic for Low-Signal Pretext Email Followed by Voice Phishing Call to Same Target, covering the data sources and telemetry it touches: Email Gateway: Email Content, Application Log: Application Log Content, Microsoft Defender for Office 365 EmailEvents. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Reconnaissance
Microsoft Sentinel / Defender
kusto
let LookbackWindow = 24h;
let CorrelationWindow = 2h;
let PretextKeywords = dynamic(["helpdesk", "help desk", "it support", "service desk", "password expir", "password reset", "vpn access", "account verification", "ticket confirmation", "technical support", "account suspended", "mfa re-enrollment"]);
EmailEvents
| where TimeGenerated > ago(LookbackWindow)
| where (Subject has_any (PretextKeywords) or SenderDisplayName has_any (PretextKeywords))
| where AttachmentCount == 0
| where UrlCount <= 1
| where ThreatTypes !has "Malware" and ThreatTypes !has "Phish"
| project EmailTimestamp = TimeGenerated, RecipientEmailAddress, SenderFromAddress, SenderDisplayName, Subject, NetworkMessageId
| join kind=inner (
    PBXCallLog_CL
    | where TimeGenerated > ago(LookbackWindow)
    | project CallTimestamp = TimeGenerated, RecipientEmailAddress = TargetUserPrincipalName_s, CallerNumber_s, CallDirection_s, CallDurationSeconds_d
    | where CallDirection_s == "Inbound"
  ) on RecipientEmailAddress
| where CallTimestamp between (EmailTimestamp .. EmailTimestamp + CorrelationWindow)
| extend MinutesBetweenEmailAndCall = datetime_diff('minute', CallTimestamp, EmailTimestamp), CorrelationSource = "PBXCallLog"
| project EmailTimestamp, CallTimestamp, MinutesBetweenEmailAndCall, RecipientEmailAddress, SenderFromAddress, Subject, CallerNumber_s, CallDurationSeconds_d, NetworkMessageId, CorrelationSource
| union (
    EmailEvents
    | where TimeGenerated > ago(LookbackWindow)
    | where (Subject has_any (PretextKeywords) or SenderDisplayName has_any (PretextKeywords))
    | where AttachmentCount == 0
    | where UrlCount <= 1
    | where ThreatTypes !has "Malware" and ThreatTypes !has "Phish"
    | project EmailTimestamp = TimeGenerated, RecipientEmailAddress, SenderFromAddress, SenderDisplayName, Subject, NetworkMessageId
    | join kind=inner (
        ServiceDeskAudit_CL
        | where TimeGenerated > ago(LookbackWindow)
        | where Action_s in ("TicketCreated", "TicketUpdated", "PasswordReset", "MFAReset")
        | project TicketTimestamp = TimeGenerated, RecipientEmailAddress = User_s, Agent_s, Action_s
      ) on RecipientEmailAddress
    | where TicketTimestamp between (EmailTimestamp .. EmailTimestamp + CorrelationWindow)
    | extend MinutesBetweenEmailAndCall = datetime_diff('minute', TicketTimestamp, EmailTimestamp), CorrelationSource = "ServiceDeskTicket"
    | project EmailTimestamp, CallTimestamp = TicketTimestamp, MinutesBetweenEmailAndCall, RecipientEmailAddress, SenderFromAddress, Subject, CallerNumber_s = Agent_s, CallDurationSeconds_d = real(null), NetworkMessageId, CorrelationSource
  )
| sort by EmailTimestamp desc

Two-pillar correlation detection joining low-signal, pretext-themed inbound email (helpdesk/IT-support/password-reset/VPN-themed subject or sender, no attachment, at most one URL, not already flagged by content-based phishing/malware filtering) against telephony and ticketing-system telemetry for the same recipient within a two-hour window. Pillar 1 correlates against inbound PBX/UC call records (PBXCallLog_CL, a custom-ingested table from the organization's telephony platform); Pillar 2 correlates against helpdesk ticketing-system audit records (ServiceDeskAudit_CL) for a ticket created/updated or a password/MFA reset performed for the same user. Both custom tables must be ingested into the workspace via a Data Collector API, Logic App, or equivalent connector from the PBX/UC platform and ticketing system respectively.

high severity medium confidence

Data Sources

Email Gateway: Email Content Application Log: Application Log Content Microsoft Defender for Office 365 EmailEvents

Required Tables

EmailEvents PBXCallLog_CL ServiceDeskAudit_CL

False Positives

  • Genuine IT helpdesk-initiated password-expiry or VPN-access-renewal email campaigns that are legitimately followed by the employee calling the real helpdesk about the same issue
  • Employees who received an unrelated pretext-themed email and separately, coincidentally, have an inbound personal or business call logged in the same window
  • Managed service provider (MSP) or outsourced IT support workflows where an automated ticket-confirmation email is a standard, expected precursor to a support callback
  • Newly onboarded employees receiving routine IT-onboarding emails (VPN setup, account verification) who then call the real helpdesk with setup questions
  • Internal security-awareness vishing-simulation exercises that intentionally pair a pretext email with a follow-up test call

Sigma rule & cross-platform mapping

The detection logic for Low-Signal Pretext Email Followed by Voice Phishing Call to Same Target (THREAT-Recon-VishingPretextEmailFollowup) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  product: azure

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Low-Signal Pretext Email with No Attachment and Zero URLs

    Expected signal: EmailEvents record with Subject containing 'Service Desk Ticket Confirmation' and 'Password Reset', AttachmentCount=0, UrlCount=0, from a sender display name/domain matching helpdesk-themed keywords.

  2. Test 2Simulated Inbound PBX Call Record Correlated to the Pretext Email Recipient

    Expected signal: A synthetic PBX call-log JSON line simulating an inbound call to [email protected] — in a real environment this would be ingested into the SIEM's PBXCallLog_CL-equivalent custom table.

  3. Test 3Simulated Ticketing-System Password Reset Correlated to the Pretext Email Recipient

    Expected signal: A synthetic ticketing-audit JSON line simulating a PasswordReset action for [email protected] — in a real environment this would be ingested into the SIEM's ServiceDeskAudit_CL-equivalent table.

Unlock playbooks & atomic tests with Pro

Get the full detection package for THREAT-Recon-VishingPretextEmailFollowup — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections