Threat Intelligence

The Rocket Mortgage Notification That Passed DKIM but Led to a Domain With No Mortgage Business

Written by Audian Paxson | Apr 2, 2026 4:45:00 AM
TL;DR A phishing email impersonating Rocket Mortgage was sent from a compromised account at an Australian consulting firm (positive-solutions[.]com[.]au). DKIM passed for the sender's Microsoft 365 tenant (positivesolutionsbne.onmicrosoft.com). SPF failed at the Votiro relay hop (44.206.213.130), and DMARC produced mixed results across relay points. The email carried Rocket Mortgage branding with a fabricated property address and loan number, plus a 'View now' CTA imposing a 24-hour action deadline. The redirect chain traversed SafeLinks, Rocket Mortgage tracking infrastructure, EdgePilot, and TitanHQ LinkLock before terminating at afd-eg[.]org, a domain registered September 1, 2025, with no connection to mortgage services.
Severity: High Credential Harvesting Impersonation MITRE: {'id': 'T1566.002', 'name': 'Phishing: Spearphishing Link'} MITRE: {'id': 'T1586.002', 'name': 'Compromise Accounts: Email Accounts'} MITRE: {'id': 'T1036.005', 'name': 'Masquerading: Match Legitimate Name or Location'}

A Rocket Mortgage notification landed with polished branding, a property address, a loan number, and a "View now" button with a 24-hour deadline. The email looked like a routine mortgage document alert. The sender was an Australian consulting firm that has nothing to do with mortgage lending.

The account at positive-solutions[.]com[.]au had been compromised. DKIM passed for the sender's Microsoft 365 tenant. The attacker inherited the full authentication profile of a legitimate business, sending impersonation emails that looked authorized because they technically were.

A Compromised Account With Split Authentication

The message originated from a compromised mailbox and relayed through a Votiro content disarm and reconstruction (CDR) gateway at IP 44.206.213[.]130. SPF failed at the Votiro relay because the CDR service's IP was not in the sender domain's SPF record. DKIM passed for positivesolutionsbne.onmicrosoft[.]com, confirming the Microsoft 365 tenant signed the message. DMARC produced inconsistent results across hops: fail at one relay, pass at another.

This split creates a problem for gateways that evaluate authentication as a binary pass/fail. The DKIM pass is genuine. The SPF failure is an infrastructure artifact from the CDR relay, not evidence of spoofing. A gateway that weights DKIM pass over SPF fail will deliver the message. In this case, that is exactly what happened.

The email body carried Rocket Mortgage branding with a fabricated property address and loan number. The 24-hour deadline on the "View now" CTA added urgency calibrated to prevent verification. Recipients who manage active mortgages see transactional notifications regularly and are conditioned to act quickly on them.

Four Hops to Nowhere

The "View now" link did not go to Rocket Mortgage. It did not go to the compromised sender's domain either. The redirect chain traversed four distinct intermediaries:

  1. SafeLinks (Microsoft Defender URL rewriting)
  2. click.e.rocketmortgage[.]com (Rocket Mortgage's own email tracking infrastructure)
  3. link.edgepilot[.]com (EdgePilot URL defense)
  4. linklock.titanhq[.]com (TitanHQ LinkLock URL protection)

The final destination was afd-eg[.]org, a domain registered September 1, 2025, with no connection to mortgage services, real estate, or financial products.

Each intermediary in the chain is a legitimate security or marketing service. A URL rewriting scanner evaluating the first hop would see SafeLinks. The second hop would show Rocket Mortgage's own tracking domain. By the third and fourth hops, scanner fatigue and redirect depth limits often mean the final destination is never evaluated.

An Australian Consulting Firm Does Not Send Mortgage Notifications

Themis identified the sender-brand mismatch: an Australian consulting firm sending Rocket Mortgage notifications is a behavioral anomaly that authentication cannot assess. The compromised account's sending history showed no prior mortgage-related communications, and the redirect chain's termination at a nine-month-old domain unrelated to any financial service confirmed the impersonation.

The 24-hour urgency deadline, the fabricated loan details, and the four-hop redirect chain are all individually common in phishing. Together, layered on top of a compromised legitimate account, they represent a campaign designed to exploit every trust signal a gateway evaluates.

See Your Risk: Calculate how many threats your SEG is missing

Indicators of Compromise

TypeIndicatorContext
Sender EmailCompromised account at positive-solutions[.]com[.]auAustralian consulting firm, no mortgage affiliation
DKIM Domainpositivesolutionsbne.onmicrosoft[.]comMicrosoft 365 tenant, DKIM pass
Relay IP44.206.213[.]130Votiro CDR relay, SPF fail
Redirect Hop 1SafeLinks (Microsoft Defender)URL rewriting service
Redirect Hop 2click.e.rocketmortgage[.]comRocket Mortgage tracking infrastructure
Redirect Hop 3link.edgepilot[.]comEdgePilot URL defense
Redirect Hop 4linklock.titanhq[.]comTitanHQ LinkLock
Landing Domainafd-eg[.]orgRegistered Sep 1, 2025, no mortgage connection
Urgency24-hour deadline"View now" CTA pressure mechanism
Fabricated DetailsProperty address and loan numberAnonymized, used for trust-building

MITRE ATT&CK Mapping

TechniqueIDRelevance
Phishing: Spearphishing LinkT1566.002"View now" CTA through four-hop redirect chain
Compromise Accounts: Email AccountsT1586.002Compromised Australian consulting firm M365 account
Masquerading: Match Legitimate Name or LocationT1036.005Rocket Mortgage branding on unrelated sender
Email Attack of the Day is a daily series from IRONSCALES spotlighting real phishing attacks caught by Adaptive AI and our community of 35,000+ security professionals. Each post breaks down a real attack. What it looked like, why it worked, and what to do about it.

Related attacks

Attack What happened
How ARC Re-Signing and an IP Allow-List Turned Three Authentication Failures Into SCL -1A phishing email claiming to be a OneDrive share from an outlook.com address originated from a county government mail server.
The Phishing Link Lived on a Domain That Didn't Exist Nine Hours EarlierA compromised university student account sent a phishing email that passed SPF, DKIM, and DMARC.
SafeLinks Wrapped the Phishing URL With the Recipient's Name on ItMicrosoft SafeLinks rewrote a phishing URL and embedded the recipient's email address into the redirect chain.
The DocuSign Portal That Was Two Days Old and Spelled Wrong: Typosquat Credential Harvesting via SendGrid RedirectA fax notification impersonating DocuSign routed through SendGrid and AppRiver relays, failed SPF and DKIM.
Seven Days Old, Port 8443: The Throwaway Domain That Safe Links Couldn't StopA compromised university email account impersonated a known contact.