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 CrowdStrike LogScale
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
LogScale Detection Query
// Alert 1: pretexting recon email — zero attachments, tracking-token or pixel URL
#event_simpleName=EmailMessage
| AttachmentCount = 0
| UrlList = /(?i)(uid|id|token|tid|rid|cid|pid|mid|track|beacon|open|px)=[A-Za-z0-9_-]{8,}/
OR UrlList = /(?i)\.(gif|png|jpe?g)(\?|$)/
| HasTrackingToken := if(UrlList =~ /(?i)(uid|token|tid|rid|cid|pid|mid|track|beacon)=/, "YES", "NO")
| IsPixelUrl := if(UrlList =~ /(?i)\.(gif|png|jpe?g)(\?|$)/, "YES", "NO")
| ThreatType := "PretextingRecon_TrackingBeaconEmail"
| groupBy(
[SenderAddress, RecipientAddress, HasTrackingToken, IsPixelUrl, ThreatType],
function=[count(as=EventCount), values(Subject, as=Subjects), values(UrlList, as=Urls)]
)
| sort(EventCount, order=desc)
// Alert 2 (run separately): beacon fire confirmation via web proxy telemetry
// #event_simpleName=/(HttpRequestHeader|DnsRequest)/
// | join(
// {#event_simpleName=EmailMessage | UrlList = /(?i)(uid|token|tid)=/ | groupBy([RecipientAddress], function=collect([UrlList], as=TrackingUrls))},
// field=[RecipientAddress], mode=inner
// )
// | RequestURL = TrackingUrlsCrowdStrike LogScale (Falcon NG-SIEM) CQL query detecting low-payload pretexting reconnaissance emails via EmailMessage telemetry (Falcon email security integration). Flags zero-attachment messages whose URL list contains a per-recipient tracking token query parameter or a raster image beacon path. A commented follow-on query sketches correlation against HTTP/DNS telemetry to confirm the beacon fired; adapt field names to your Falcon email connector schema.
Data Sources
Required Tables
False Positives & Tuning
- Marketing platforms (Mailchimp, HubSpot) and sales engagement tools (Outreach.io, Salesloft) using structurally identical per-recipient tracking pixels/links — build a LogScale saved-search exclusion using a lookup table of approved sender domains
- Security awareness training platforms (KnowBe4, Proofpoint) that intentionally use tracking pixels/links to measure simulated-phishing click-through rates — exclude by known simulation sending infrastructure
- CRM and helpdesk read-receipt features generating similar tracking token patterns for legitimate customer communications
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