Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for THREAT-Recon-PretextingReconEmailTrackingBeacon.
Upgrade to ProDetect Pretexting Reconnaissance Email with Tracking Pixel / Beacon Link in Splunk
Before committing to a spearphishing attachment (T1598.002) or spearphishing link (T1598.003) payload, adversaries increasingly send an innocuous, low-payload pretexting email first — a brief 'checking in', 'meeting request', or 'invoice follow-up' message with no attachment and no overt malicious link. The email instead embeds a uniquely-tokenized tracking pixel (a 1x1 image or invisible-CSS beacon) or a benign-looking beacon link, where the token is minted per-recipient. When the recipient's mail client renders the image or a human clicks the link, the beacon fires a GET request back to adversary-controlled infrastructure, confirming the mailbox is live, fingerprinting the recipient's IP address, approximate geolocation, mail client/user agent, and open time, and validating that a real human (not a sandbox or secure email gateway detonation chamber) triggered it. Star Blizzard, TA453, and TA427 have been documented using single-pixel and unique-URL tracking beacons in low-content reconnaissance emails to qualify targets and time follow-on credential-harvesting or malware-laden messages for when the mailbox is confirmed active. Because these emails carry no attachment and no overtly malicious URL pattern, they routinely pass secure email gateway and sandbox scoring; detection instead relies on correlating the low-payload email itself (via EmailEvents/EmailUrlInfo) with the subsequent beacon fetch observed in web proxy/gateway logs.
MITRE ATT&CK
- Tactic
- Reconnaissance
SPL Detection Query
index=o365 sourcetype="o365:management:activity" Workload=Exchange Operation=MessageReceived
| eval AttachmentCount=coalesce(AttachmentCount, 0)
| eval UrlList=coalesce(Urls, "")
| eval UrlCount=if(isnull(UrlList) OR UrlList=="", 0, mvcount(split(UrlList, ";")))
| where AttachmentCount=0 AND UrlCount<=2 AND UrlCount>0
| eval HasTrackingToken=if(match(UrlList, "[?&](uid|id|token|tid|rid|cid|pid|mid|track|beacon|open|px)=[A-Za-z0-9_\-]{8,}"), 1, 0)
| eval IsPixelUrl=if(match(UrlList, "\.(gif|png|jpe?g)(\?|$)"), 1, 0)
| eval FreemailSender=if(match(SenderAddress, "@(gmail|yahoo|hotmail|outlook|protonmail|tutanota|icloud|aol)\."), 1, 0)
| eval SuspicionScore=HasTrackingToken + IsPixelUrl + FreemailSender
| where SuspicionScore>=1
| eval ThreatType="PretextingRecon_TrackingBeaconEmail"
| table _time, SenderAddress, RecipientAddress, Subject, UrlList, HasTrackingToken, IsPixelUrl, FreemailSender, SuspicionScore, ThreatType
| sort - _timeSPL detection of low-payload pretexting reconnaissance emails via Office 365 Management Activity logs. Flags inbound messages with zero attachments and one or two embedded URLs where a URL contains a unique per-recipient tracking token or points directly to a raster image (pixel beacon). A companion search (see huntingQueries) joins the flagged tracking URL against proxy access logs to confirm the beacon actually fired, which is the strongest indicator that a mailbox was fingerprinted and validated as a live target.
Data Sources
Required Sourcetypes
False Positives & Tuning
- Legitimate email marketing platforms (Mailchimp, HubSpot, SendGrid) embedding open-tracking pixels for campaign analytics
- Sales engagement tools (Outreach.io, Salesloft, Yesware) tracking outreach email opens for legitimate business development
- CRM/helpdesk read-receipt features (Salesforce, Zendesk) using per-message tracking tokens
- Calendar scheduling confirmations (Calendly, Doodle) with per-recipient tracking parameters in links
Other platforms for THREAT-Recon-PretextingReconEmailTrackingBeacon
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.
- Test 1Low-Payload Email with Unique Tracking Token URL
Expected signal: EmailEvents record with AttachmentCount=0, UrlCount=1; EmailUrlInfo record for the tracking URL containing a uid= query parameter matching the tracking token regex.
- Test 2Tracking Pixel Beacon Fetch Simulation
Expected signal: Web proxy/gateway access log entry showing a GET request to status-updates-portal.example/px.gif with the uid= tracking parameter, timestamped shortly after the simulated email delivery.
- Test 3Bulk Freemail Sender Recon Email Without Tracking Token (Negative Control)
Expected signal: EmailEvents record with AttachmentCount=0, UrlCount=0; no EmailUrlInfo record for this NetworkMessageId.
References (5)
- https://attack.mitre.org/techniques/T1598/002/
- https://attack.mitre.org/techniques/T1598/003/
- https://www.proofpoint.com/us/blog/threat-insight
- https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/advanced-hunting-emailurlinfo-table
- https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/advanced-hunting-emailevents-table
Unlock playbooks & atomic tests with Pro
Get the full detection package for THREAT-Recon-PretextingReconEmailTrackingBeacon — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month