
After the Breach: The Compensation Email
After a crypto exchange breach, two scam emails reach a Dublin advisory firm: one asks for a Bitcoin fee, the other links to a wallet "verification" page. You read headers and bodies, scope the campaign in the message trace and find in the web proxy who fell for it.
Start this operation
Investigation Tasks
Complete each task by investigating alerts and submitting your findings.
Who signed the desk email?
5The reconciliation desk email in the finance assistant's mailbox shows Kestovan as its display name. Find the domain that put its DKIM signature on the message.
No link, a wallet address
5The reconciliation desk message has no links and no attachments. It asks for a 0.0042 BTC "wallet-verification fee". Read the body and give the Bitcoin address the fee must be sent to.
Where does Verify go?
5The wallet email arrived at 07:52 on Monday with one button. Its text says Verify; its link can say something else. Find the host name the Verify button really points to.
How many mailboxes got it?
5Each copy of the wallet email went to one recipient, from the same sender with the same subject. Count how many mailboxes in Ardmor Lane Advisory received the wallet verification email, the reporter's included.
Who sent data to the page?
5Two people opened the verification page on Monday morning; two more requests to it were refused by the block list. A GET reads a page, a POST sends data to it. Give the account name of the person who sent data to the verification page, without the ARDMOR\ domain.
Find the withdrawal request
5The finance assistant replied to the reconciliation desk. A fee paid from an exchange account starts as a withdrawal request. Find the withdrawal request that belongs to this case and give the time it was submitted: the POST to the exchange's withdrawal API, not the opening of the withdrawal page, in UTC, as HH:MM (drop the seconds).
Decide the case
5Decide what happens to this case now, using the runbook below. Answer with the one word the runbook uses for that outcome.
7 tasks · 35 points total
Training Tools
Email Console
Email header & content analysis
SIEM Console
Log analysis & SPL queries
Skills You'll Build
Ideal for newcomers to SOC operations. Guided investigation with clear indicators.
Prerequisites
- No prior experience required
- Familiarity with Email concepts
- Familiarity with SIEM concepts
Ready to investigate?
More Operations
View allTerminalFix: Steganographic PNG Payload to a Python Reverse Tunnel
An endpoint alert fired on a claims analyst's workstation at Caldwyn Mutual: a signed Microsoft binary, LockScreenContentServer.exe, ran this morning, and three PNG image files landed on the same machine around the same time. A signed Windows component and a few pictures are the kind of thing a busy shift closes as noise. The analyst already told the help desk they pasted a verification command into a terminal earlier, so how the activity started is not the question. What the signed binary and the images did after that is. Work the endpoint, SIEM and firewall evidence and the Query tab, and establish what the signed binary and the images did on the host.
Automated Transcript: A Voicemail From Your Own Domain
A voicemail notification from your own company's domain, with an SVG attached. In mail, endpoint and proxy logs, read the delivery record instead of the From line, see why an image can be code, then find who got it, who opened it, who reached the page and whether anyone fell.
Call This Number: The Debt-Relief Email With Nothing to Click
A debt-relief email with no link and no attachment, only a phone number. Step by step, find the sender, the number, who else got it, who called, what was taken and whether the caller rang back, using the delivery records and the call logs.