Table of Contents
The recipient saw a professional mortgage company email with a login prompt, a familiar-looking URL, and a signature block with an NMLS number. The visible URL pointed to 9168050941.lombard[.]finance, which looked like a legitimate internal application. It did not resolve in DNS. The actual click path traveled through two security vendor URL rewriting services before landing on a credential harvesting page hosted on entirely different infrastructure.
The Identity That Didn't Match Itself
The message was sent from sch.sisconthosting[.]com via Amazon SES at IP 54[.]240[.]7[.]39. SPF passed. DKIM passed for both sch.sisconthosting[.]com and amazonses.com. The domain was registered in 2020 through PublicDomainRegistry with a Peruvian registrant.
The visible signature displayed hr@lombard[.]finance as the sender's contact. But the underlying HTML mailto: pointed to fortunato@carpenterhomeloans[.]com, a completely different domain. Anyone clicking the email address in the signature would compose a reply to a domain the attacker controlled, not the one displayed. This display-action mismatch extended to the authority claim: the message included "NMLS # 9168050941" to project regulatory credibility, but no linkage existed between that number and lombard[.]finance.
Two Security Vendors in the Redirect Chain
The "Login and complete tasks" button did not point to lombard[.]finance. The click path was:
linklock.titanhq[.]com(TitanHQ LinkLock, a URL rewriting gateway)url-shield.securence[.]com(Securence URL Shield, another URL rewriting service)sch.sisconthosting[.]com/docs/index.html(final landing: credential harvesting page)
Both TitanHQ and Securence are legitimate email security products that rewrite URLs to scan them. Their presence in the redirect chain meant the link appeared to have been vetted by not one but two security tools. If either service scanned the destination at rewrite time and found it clean (perhaps because the harvesting page was not yet live, or because it served benign content to known scanner IPs), the rewritten URL would carry their domain in the path, lending false credibility.
The final destination at sch.sisconthosting[.]com/docs/index.html presented a login form with the text "Login and complete tasks." A 1x1 tracking pixel in the email body confirmed the recipient opened the message before they clicked anything.
What Made It Visible
IRONSCALES flagged the non-resolving displayed URL, the credential harvesting landing page classification, and the display-mailto mismatch in the signature block. The security vendor domains in the redirect chain did not suppress the behavioral signals that the final destination was malicious.
See Your Risk: Calculate how many threats your SEG is missing
Indicators of Compromise
| Type | Indicator | Context |
|---|---|---|
| Sending Domain | sch.sisconthosting[.]com | Amazon SES relay, Peruvian registrant |
| Sending IP | 54[.]240[.]7[.]39 | Amazon SES eu-west-1 |
| Displayed URL | 9168050941.lombard[.]finance | Non-resolving subdomain |
| Display Signature | hr@lombard[.]finance | Visible identity |
| Actual Mailto | fortunato@carpenterhomeloans[.]com | Hidden reply destination |
| Redirect Hop 1 | linklock.titanhq[.]com | TitanHQ URL rewriting |
| Redirect Hop 2 | url-shield.securence[.]com | Securence URL Shield |
| Landing Page | sch.sisconthosting[.]com/docs/index.html | Credential harvesting form |
| Tracking | 1x1 remote image | Open-tracking pixel |
MITRE ATT&CK Mapping
| Technique | ID | Relevance |
|---|---|---|
| Phishing: Spearphishing Link | T1566.002 | Credential harvesting URL delivered via redirect chain |
| Masquerading: Match Legitimate Name or Location | T1036.005 | Non-resolving lombard.finance URL and fabricated NMLS number |
| Stage Capabilities: Link Target | T1608.005 | Attacker staged credential harvesting page on sisconthosting.com |
Related attacks
| Attack | What happened |
|---|---|
| The HubSpot Account Suspension That Came From Flodesk | An account suspension email claimed to be from the HubSpot Team but was sent from a personal domain via Amazon SES. |
| The Hotel Reservation That Hid a Cloaked Link Behind a Real Booking | A reservation confirmation from nobuhotels.com contained a legitimate booking, a clean PDF attachment, and dozens of real hotel links. |
| Three Google Domains, One Redirect Chain, and a Turkish Landing Page | A phishing email routed its CTA through three Google-owned domains before landing on an unrelated Turkish website. |
| The DocuSign Portal That Was Two Days Old and Spelled Wrong: Typosquat Credential Harvesting via SendGrid Redirect | A fax notification impersonating DocuSign routed through SendGrid and AppRiver relays, failed SPF and DKIM. |
| How ARC Re-Signing and an IP Allow-List Turned Three Authentication Failures Into SCL -1 | A phishing email claiming to be a OneDrive share from an outlook.com address originated from a county government mail server. |
Explore More Articles
Say goodbye to Phishing, BEC, and QR code attacks. Our Adaptive AI automatically learns and evolves to keep your employees safe from email attacks.