Real estate wire fraud is one of the most financially damaging and emotionally devastating cybercrimes in the United States — not because it is technically sophisticated, but because it exploits the single most trusted moment in a real estate transaction: the closing wire. The FBI's 2025 IC3 Annual Report documented 12,368 complaints and $275.1 million in losses from real estate wire fraud — a 59% increase from $173 million in 2024 and a 90% increase from $145 million in 2023. Even with the FBI's Recovery Asset Team successfully freezing funds in some cases, the recovery rate is approximately 58%. The remaining 42% is gone permanently.
The attack is a variant of Business Email Compromise (BEC) in which the attacker impersonates a trusted party to the transaction — a title company, a closing attorney, a real estate agent, or a lender — and sends fraudulent wire instructions at the exact moment the buyer is expecting them. The email arrives at the right time, references the correct transaction details, and creates urgency around a deadline the buyer already knows is real. Nothing about it feels wrong. Because the money moves via wire transfer, which is designed to be final and irreversible, recovery is the exception rather than the rule.
Current email security detection for this specific attack vector is a gap. Existing BEC rules target generic patterns — new sender domains, invoice language, executive impersonation — but none specifically address the real estate closing wire scenario, where the timing of the email, the impersonated parties, and the specific language around "closing," "escrow," and "wire instructions" are the detection signals.
A real estate closing involves a predictable sequence of high-value wire transfers between parties who have often never interacted before, operating under strict deadlines, using email as the primary communication channel. The buyer expects to receive wire instructions from their title company, closing attorney, or escrow agent in the days before closing. The wire amount is large — often the single largest financial transaction of a person's life. The timeline is fixed and non-negotiable. The urgency is built into the legitimate transaction.
Attackers exploit every one of these structural conditions. They monitor compromised email accounts belonging to title companies, real estate attorneys, mortgage brokers, or buyers' agents — waiting for the right moment. When a transaction approaches closing, they send fraudulent wire instructions that appear to come from the expected party, at the expected time, referencing the correct transaction details. The buyer wires the funds. By the time the fraud is discovered — often at the closing table when the real parties ask where the money is — the funds have already moved through multiple accounts and are effectively gone.
IC3 documented case, August 2025: A couple closing on a home received an email impersonating their legitimate attorneys with modified wire instructions. They wired over $449,000 to the fraudulent account. The FBI's Recovery Asset Team initiated the Financial Fraud Kill Chain immediately upon receiving the IC3 complaint — but recovery was not guaranteed. This is not an edge case. The FBI's RAT handles hundreds of these incidents annually.
The FBI has specifically designated Real Estate Wire Fraud (REWF) as a sub-category of BEC due to its prevalence and financial impact. Victims include buyers, sellers, title companies, law firms, real estate agents, and lenders — every party to a transaction is a potential target. The attack does not require technical sophistication. It requires access to one party's email, knowledge of the transaction timeline, and a wire instruction email sent at the right moment.
Sender: titleco@firstamericantitle.com — known domain, established relationship, DMARC passing
Timing: Sent 3-5 days before closing date as expected
Content: Wire instructions to the title company's escrow account, correct bank name, routing and account numbers the buyer has verified previously
Tone: Professional, references specific property address and closing date, no unusual urgency
Sender: titleco@firstamericantitle-closings.com — lookalike domain registered days earlier, DMARC not established
Timing: Sent just before closing — urgency framing around same-day or next-day wire deadline
Content: "Updated" wire instructions with different bank, routing, and account numbers. References same property address and closing date. Asks buyer to disregard previous instructions.
Tone: Adds urgency — "funds must be received by 2pm to proceed with closing" — mirroring real transaction pressure
Attack model based on FBI IC3 2025 Annual Report documented cases and FBI Congressional Report on BEC and Real Estate Wire Fraud.
Defense against real estate wire fraud operates at two levels: individual transaction hygiene and email-layer detection. Both are necessary. Neither is sufficient alone.
| Signal | Indicator | Confidence | Notes |
|---|---|---|---|
| Sender domain age | network.whois().days_old < 30 | High | New domains impersonating established title companies |
| Reply-to mismatch | reply_to domain ≠ sender domain | High | Attacker routes replies to separate fraudulent account |
| Wire instruction language | routing number + account number pattern | Medium-High | Regex pattern for bank routing/account number strings |
| Closing urgency language | "closing," "wire by," "funds due" | Medium | Combined with other signals — alone too broad |
| Title company impersonation | Display name ≠ sender domain | High | Known title company names in display name from unknown domain |
| Updated instructions framing | "updated wire," "new account," "disregard previous" | High | Extremely specific to fraud — rarely in legitimate closing email |
| BEC NLU intent | ml.nlu_classifier intent == "bec" | Medium | Supports other signals — not sufficient alone |
Real estate wire fraud is not a new attack. It has been documented by the FBI since at least 2015, and the FBI has run a dedicated congressional reporting category for it since 2022. The losses have grown every year. The attack pattern is well understood. And yet a dedicated email security detection rule for the specific signals of a closing wire fraud email does not exist in any major open-source ruleset.
This is not because the problem is technically hard to detect. The signals are specific and identifiable: a recently registered domain impersonating a title company, wire instruction language with routing and account numbers, urgency framing around a closing date, and a reply-to mismatch routing the conversation to a separate fraudulent account. These signals are not present in normal business email. They are present in real estate wire fraud emails. The combination is detectable at the email layer before any wire transfer occurs.
The 90% growth in losses over three years suggests the attack is scaling faster than awareness and detection are keeping up. AI has made the targeting cheaper and the personalization more convincing — the Cisco Talos "democratisation" observation applies directly here. An attacker no longer needs to spend hours researching a target. They need access to one email account, enough public information to reference the correct transaction, and a lookalike domain registered the week before.
The email is still the only reliable intervention point. Once the wire is sent, the recovery window is measured in hours and closes quickly. The detection rule that catches this before delivery is straightforward to write. The analysis that explains why it matters is this one.
This analysis is based on publicly available information including the FBI IC3 2025 Annual Report, the FBI Congressional Report on Business Email Compromise and Real Estate Wire Fraud, Cisco Talos Threat Source newsletter (April 2026), and industry documentation from Stewart Title and First American. A companion Sublime Security detection rule targeting real estate closing wire fraud email patterns is in development and will be submitted to the open-source rule feed when complete. This analysis represents independent research produced as a contribution to the security community.
I'm a security researcher in Connecticut. Analysis is the part I love: tracing threat actor behavior, pulling apart supply chain attacks, and following evidence even when it lands on "unknown." When a question needs a tool that doesn't exist, I build it; most of the tools on this site started that way. Before security I spent 15 years designing enterprise software, which is why my tools assume a human will actually have to use them. I contribute detection rules to Sublime Security's open-source production ruleset. Security+ in progress. Everything here is independent work, shared as a contribution to the security community.