TL;DR An email sent via Amazon SES from sch.sisconthosting[.]com passed SPF and DKIM. The message displayed a professional mortgage company identity with a visible URL at 9168050941.lombard[.]finance, but that subdomain did not resolve in DNS. The actual click path routed through linklock.titanhq.com (TitanHQ) and url-shield.securence.com (Securence) before landing on sch.sisconthosting[.]com/docs/index.html, a credential harvesting page. The visible email signature showed hr@lombard[.]finance while the underlying HTML mailto pointed to fortunato@carpenterhomeloans[.]com, a display-action mismatch. The message included a fabricated NMLS number, a tracking pixel, and personalized greeting. Two security vendor URL rewriting services in the redirect chain gave the final URL an appearance of having been scanned and cleared.
Severity: High Credential Harvesting Url Rewriting Abuse Redirect Chain MITRE: {'id': 'T1566.002', 'name': 'Phishing: Spearphishing Link'} MITRE: {'id': 'T1036.005', 'name': 'Masquerading: Match Legitimate Name or Location'} MITRE: {'id': 'T1608.005', 'name': 'Stage Capabilities: Link Target'}

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:

  1. linklock.titanhq[.]com (TitanHQ LinkLock, a URL rewriting gateway)
  2. url-shield.securence[.]com (Securence URL Shield, another URL rewriting service)
  3. 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

TypeIndicatorContext
Sending Domainsch.sisconthosting[.]comAmazon SES relay, Peruvian registrant
Sending IP54[.]240[.]7[.]39Amazon SES eu-west-1
Displayed URL9168050941.lombard[.]financeNon-resolving subdomain
Display Signaturehr@lombard[.]financeVisible identity
Actual Mailtofortunato@carpenterhomeloans[.]comHidden reply destination
Redirect Hop 1linklock.titanhq[.]comTitanHQ URL rewriting
Redirect Hop 2url-shield.securence[.]comSecurence URL Shield
Landing Pagesch.sisconthosting[.]com/docs/index.htmlCredential harvesting form
Tracking1x1 remote imageOpen-tracking pixel

MITRE ATT&CK Mapping

TechniqueIDRelevance
Phishing: Spearphishing LinkT1566.002Credential harvesting URL delivered via redirect chain
Masquerading: Match Legitimate Name or LocationT1036.005Non-resolving lombard.finance URL and fabricated NMLS number
Stage Capabilities: Link TargetT1608.005Attacker staged credential harvesting page on sisconthosting.com
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
The HubSpot Account Suspension That Came From FlodeskAn 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 BookingA 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 PageA 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 RedirectA 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 -1A 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.