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 IBM QRadar
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
QRadar Detection Query
SELECT
DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') AS EventTime,
"SenderAddress" AS SenderAddress,
"RecipientAddress" AS RecipientAddress,
"Subject" AS Subject,
"AttachmentCount" AS AttachmentCount,
"UrlList" AS UrlList,
CASE
WHEN "UrlList" ILIKE '%uid=%' OR "UrlList" ILIKE '%token=%' OR "UrlList" ILIKE '%tid=%'
OR "UrlList" ILIKE '%track=%' OR "UrlList" ILIKE '%beacon=%'
THEN 1 ELSE 0
END AS HasTrackingToken,
CASE
WHEN "UrlList" ILIKE '%.gif%' OR "UrlList" ILIKE '%.png%' OR "UrlList" ILIKE '%.jpg%' OR "UrlList" ILIKE '%.jpeg%'
THEN 1 ELSE 0
END AS IsPixelUrl
FROM events
WHERE LOGSOURCETYPENAME(devicetype) ILIKE '%Office 365%'
AND "AttachmentCount" = 0
AND (
"UrlList" ILIKE '%uid=%' OR "UrlList" ILIKE '%token=%' OR "UrlList" ILIKE '%tid=%'
OR "UrlList" ILIKE '%track=%' OR "UrlList" ILIKE '%beacon=%'
OR "UrlList" ILIKE '%.gif%' OR "UrlList" ILIKE '%.png%'
)
LAST 7 DAYS
ORDER BY starttime DESCQRadar AQL query flagging inbound email events with zero attachments where the embedded URL(s) contain a per-recipient tracking token query parameter or reference a raster image beacon file extension — the structural signature of a low-payload pretexting reconnaissance email. Requires the Office 365 email DSM to expose custom properties AttachmentCount, UrlList, SenderAddress, and RecipientAddress; adapt property names to your QRadar Office 365 log source extension.
Data Sources
Required Tables
False Positives & Tuning
- Marketing automation platforms (Mailchimp, HubSpot, SendGrid) embedding open-tracking pixels — build a QRadar reference set of known marketing sender domains and exclude via a building block
- Sales engagement tools (Outreach.io, Salesloft) generating per-recipient tracking URLs for legitimate business development outreach
- CRM/helpdesk read-receipt tracking (Salesforce, Zendesk, Intercom) that structurally resembles adversary beacon 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