Table of Contents
Most phishing tries to look like it belongs. This one did not bother. The message that landed in a shared customer-service mailbox at a hospitality brand arrived with SPF failing, no DKIM signature, no DMARC record at all, an empty Return-Path, and a Message-ID that claimed to originate from localhost. By every transport signal a mail server can read, it was a forged injection from an unauthenticated host, not some benign relay quirk. It reached the inbox anyway. And it carried instructions to wire roughly 300 million Korean won to a Shinhan Bank account, split across two transfers, under a DocuSign-branded veneer.
The distance between how obviously fake the envelope was and how far the payload was willing to reach is the whole point of this case.
An Envelope With Nothing Behind It
The sending IP, 136[.]0[.]82[.]150, was not a recognized email gateway. It announced itself with a HELO of [127[.]0[.]0[.]1], the loopback address, which no legitimate mail host would ever present to the outside world. The Return-Path was empty, and the Message-ID referenced localhost. Sender Policy Framework (SPF) failed because that IP is authorized for nothing. Domain Keys Identified Mail (DKIM) was simply absent, so there was no signature to verify. With neither passing, Domain-based Message Authentication, Reporting and Conformance (DMARC) had nothing to align, and no published policy to enforce.
In other words, this was not a subtle spoof that slipped through on a technicality. It was a raw, hand-forged injection that failed every check we have. The only thing dressing it up was the content: DocuSign styling, an OPEN DOCUMENT call to action, and Korean-language wire-transfer instructions naming a specific bank and beneficiary. The authentication layer told the truth. The pixels lied.
The Google Maps Detour
The OPEN DOCUMENT button did not point at a phishing page directly. It pointed at Google. The click ran through Google Maps redirector URLs on Google country domains (hxxps://maps.google[.]it[.]ao/url?q=... and a companion maps.google[.]co[.]ao variant), which then forwarded the browser onward. Open redirectors on trusted, recognized hosts are attractive precisely because the first thing a hover or a link scanner sees is a Google address. The malicious destination sits one hop past the part everyone trusts.
That destination was inifdborivali[.]webhop[.]me, a dynamic-DNS subdomain with public phishing-abuse history, hosted on an AWS EC2 instance (52[.]26[.]213[.]3) whose reverse DNS did not match. None of that is visible at the moment of the click. The reader sees Google, trusts Google, and lands somewhere Google never sent them.
The Attachment That Already Knew You
Riding alongside the link was a small HTML attachment, ck#...[.]html, just over two kilobytes. Open it and it renders locally in the browser. Inside was hex and XOR obfuscated JavaScript that, per static analysis, decodes to a redirect toward a second host, trsnell[.]com. There is no
Related attacks
| Attack | What happened |
|---|---|
| The Procore Footer Was Real. The Document Was Not. | Every link scanner called the Procore and ExxonMobil URLs clean. |
| A Pixel-Perfect Sephora Delivery Notice Shows Why Email Authentication Alone Can't Protect You | A fully authenticated Sephora delivery notification passed SPF, DKIM, and DMARC with perfect scores. |
| The Email That Passed Every Security Check (Because Adobe Sent It) | A phishing campaign targeting school district staff used Adobe's own sending infrastructure, real DKIM signatures. |
| The Phishing Infrastructure Was Canva. The Delivery Mechanism Was Canva. The Authentication Was Canva. | An attacker signed up for Canva, built a phishing lure as a design, and used the platform's own sharing feature to deliver it. |
| When the Sender Domain Is Also the Phishing Kit Host: Dual-Purpose Domain Compromise | An attacker compromised a legitimate manufacturing company domain and used it two ways at once: as the authenticated sending address and as the host for... |
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.