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 Google Chronicle
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
YARA-L Detection Query
rule pretexting_recon_tracking_beacon_email {
meta:
author = "df00tech Detection Engineering"
description = "Detects low-payload pretexting reconnaissance emails carrying a unique per-recipient tracking pixel or beacon link, used to fingerprint and validate live targets ahead of a follow-on spearphishing attack."
severity = "MEDIUM"
priority = "MEDIUM"
mitre_attack_tactic = "Reconnaissance"
mitre_attack_technique = "T1598.002"
mitre_attack_subtechnique = "T1598.003"
reference = "https://attack.mitre.org/techniques/T1598/003/"
created = "2026-07-19"
version = "1.0"
events:
$email.metadata.event_type = "EMAIL_TRANSACTION"
$email.network.email.direction = "INBOUND"
$email.network.email.attachments = 0
$email.target.url.query = /(?i)(uid|id|token|tid|rid|cid|pid|mid|track|beacon|open|px)=[A-Za-z0-9_-]{8,}/
$email.principal.hostname = $hostname
condition:
$email
}
rule pretexting_recon_beacon_fired {
meta:
author = "df00tech Detection Engineering"
description = "Correlates a flagged pretexting tracking URL with a subsequent outbound network request to the same domain, confirming the beacon fired and the target mailbox was validated as live."
severity = "HIGH"
priority = "HIGH"
mitre_attack_tactic = "Reconnaissance"
mitre_attack_technique = "T1598.003"
created = "2026-07-19"
version = "1.0"
events:
$email.metadata.event_type = "EMAIL_TRANSACTION"
$email.target.url.domain = $domain
$net.metadata.event_type = "NETWORK_HTTP"
$net.target.url.domain = $domain
$net.principal.hostname = $hostname
match:
$domain over 3d
condition:
$email and $net
}Two Chronicle YARA-L 2.0 rules. Rule 1 (pretexting_recon_tracking_beacon_email) flags inbound, zero-attachment emails whose target URL query string carries a unique per-recipient tracking token, using UDM EMAIL_TRANSACTION events. Rule 2 (pretexting_recon_beacon_fired) performs a temporal correlation over 3 days between the flagged email's tracking domain and a subsequent NETWORK_HTTP event to the same domain, confirming the beacon fired and the recipient was fingerprinted as a live target.
Data Sources
Required Tables
False Positives & Tuning
- Marketing automation and newsletter platforms embedding tracking pixels/links for engagement analytics — add a Chronicle reference list of approved marketing/sales-tooling domains and exclude via a NOT condition on $domain
- Sales engagement platforms (Outreach.io, Salesloft, Yesware) generating per-recipient tracking links for legitimate outreach
- CRM/helpdesk read-receipt features using structurally similar per-message tracking tokens
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