Topic starter
25/10/2026 11:10 am
TL;DR: Email fraud still produces heavy SMB losses, with At-Bay putting the average at $286,000 per incident and noting a 55% rise in financial fraud since 2021. Payment approval flows need separate verification because inbox filters cannot prove a request is genuine.
Editorial analysis by NHI Mgmt Group, based on content published by At-Bay: “Fraud Defense Turns One”.
By the numbers:
- Since 2021, financial fraud frequency has jumped by 55%.
Key questions
Q: Why do lookalike domains and urgent payment requests create such high fraud risk?
A: Because they combine sender impersonation with time pressure, which reduces the chance that staff will challenge the request.
Q: What are the signs that email trust controls are failing?
A: Repeated replies to suspicious requests, high forward rates, weak reporting discipline, and inconsistent escalation around vendor changes are all warning signs.
Q: What should teams do first when email fraud is slipping past inbox security?
A: Start by adding an out-of-band verification step for any request that changes payment details, requests a wire transfer, or pressures staff to bypass normal checks.
Practitioner guidance
- Implement out-of-band verification for payment changes Require a second channel check for any new wire instruction, banking detail change, or high-value transfer request before approval is granted.
- Tune detection for lookalike and newly registered domains Prioritise domain similarity, registration age, reputation history, and sender impersonation rules for messages that request money movement or sensitive changes.
- Add behavioural review to executive impersonation alerts Flag urgent requests, off-hours sending, unusual reply-to addresses, and language that discourages verification as case-review triggers.
Bottom line: Email fraud remains effective because it targets human approval workflows, not just email infrastructure.
Glossary terms: Email Fraud, Lookalike Domain, Out-Of-Band Verification, Authorisation Layer Fraud Exposure
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
27/10/2026 7:17 pm
Email fraud is a trust governance problem, not just a mail security problem. The article shows that the message itself can be structurally valid while the business request is fraudulent. That shifts the control question from blocking mail to validating intent, sender legitimacy, and approval context. Practitioners should treat email fraud as a cross-functional identity and finance risk, not a helpdesk nuisance.
A few things that frame the scale:
- U.S. fraud losses are projected to reach $40 billion by 2027.
A question worth separating out:
A: Accountability should be shared but explicit. Finance owns payment verification, dual approval, and vendor change controls. Security owns monitoring, awareness training, and identity protections around email and financial systems. Operations should support documented escalation paths and incident reporting. When responsibilities are written down and rehearsed, organizations reduce the chance that a fraudulent request slips through a gap between teams.
👉 Read our full editorial: Email fraud outpaces legacy filters as SMB losses rise
This post was modified 7 days ago by NHI Mgmt Group