How do you prove a payment request came from a fake lookalike email domain?
In May 2026 Singapore police described how staff at a commodity trading company received an email from a supplier’s domain that had been “subtly altered by transposing two letters”, and the next day wired US$6.6 million to an account abroad. The company reported to police on the day it discovered the fraud, and the money was traced and recovered. Many companies are not so fortunate, and the first hours matter.
If money has been paid, call your bank and the police first, because speed often decides whether it can be stopped. Then preserve the original emails in their native format and examine the full message headers, which show the sending domain, the servers that handled the message, authentication results (SPF, DKIM and DMARC) and any reply-to address that diverts answers elsewhere. Registration and DNS records for the lookalike domain may show when it was registered. Comparing the fake thread with the genuine one can show where the conversation was hijacked, and checking your own mailboxes, and the supplier’s with its cooperation, can show whether a real account was compromised first.
What was reported
In a release on 20 May 2026 about a multi-country operation against scams, the Singapore Police Force described a case in which, on 28 April, staff at a Singapore commodity trading firm received an email from a domain “subtly altered by transposing two letters” of a supplier’s name, and on 29 April transferred US$6.6 million to an account in Oman. On 30 April the real supplier said it had not changed its bank account, and the company reported to police that day. Working with authorities in the UAE and Oman and with the bank, police said the funds were “traced and fully recovered”.
The release did not describe how the lookalike domain was set up or whether any mailbox had been compromised, and we draw no conclusions on that.
What email forensics can show
- Headers. The real sending domain and servers, which a display name can hide.
- Authentication. SPF, DKIM and DMARC results, which show whether the message passed the checks for the domain it claims, though a lookalike domain can pass checks for itself.
- Reply-to tricks. A reply-to address that quietly sends answers to the fraudster.
- Domain records. When the lookalike domain was registered and what mail records it has.
- Thread hijack. How the fake thread compares with the genuine one, which can suggest whether the fraudster had seen real correspondence, for example through a compromised mailbox on either side.
Forwarded copies and printouts lose most of this. Preserve the original messages from the mailbox, or have them exported in native format.
If you have paid a fake invoice
Call your bank at once and ask it to recall or stop the payment, then report to the police. Do not reply to the fraudulent thread. Preserve the emails as they are, ask your IT provider to export mailbox sign-in and audit logs now, as some are kept only for days, check your own mailbox for rules that forward or hide messages (take screenshots before switching them off), change passwords and turn on multi-factor authentication, and tell the genuine supplier by phone using a number you already hold. Check whether cyber insurance requires early notice. If a mailbox was compromised, personal data may have been exposed: in Singapore a notifiable breach must be reported to the PDPC within 3 calendar days of assessing it as notifiable, and in Hong Kong, as at November 2026, there is no general legal duty under the PDPO to notify, although the PCPD encourages it; under Cap. 653 only designated critical infrastructure operators must report computer security incidents, within 12 hours of becoming aware of a serious incident and 48 hours of becoming aware of any other. Take advice promptly. For the future, confirm any change of bank details by calling a known number, never one in the email.
See email forensics and when an email platform is breached.
Sources
General commentary on public reports, not legal advice and not a finding about any organisation or person named in those reports. Facts are as reported at the time of writing.
Frequently asked questions
How do you prove a payment request came from a fake lookalike email domain?
If money has been paid, call your bank and the police first. Then preserve the original emails and have the full headers, authentication results and any reply-to address examined, check registration and DNS records for the lookalike domain and compare the fake thread with the genuine one; together these can support a finding that the request came from a lookalike domain.
What is a lookalike domain?
A domain registered to resemble a real one, for example by swapping two letters or replacing a letter with a similar-looking character, so that a fraudulent email looks as if it came from a known supplier.
Can money paid to a fraudster be recovered?
Sometimes, if the bank and police act before it is moved on. In the Singapore case, the company reported on the day it discovered the fraud and the funds were recovered. Delay makes recovery much less likely.
Does a forwarded email keep the evidence?
Usually not all of it. Forwarding and printing lose the original headers. Preserve the message in the mailbox or export it in native format.
How can we stop this happening again?
Confirm every change of bank details by calling a number you already hold, train staff to check sending domains, protect mailboxes with multi-factor authentication and consider registering obvious lookalikes of your own domain.
Facing something like this?
The first discussion is confidential and free, and usually changes what you decide to do next. Call +852 5808 1071 or use the case review form.