Diverted payments and BEC fraud: what the case teaches
A diverted payment can turn into a major loss: here is why business email compromise remains effective and which controls are needed.
A single diverted payment can cause immediate damage, block financial flows and open a broader operational problem. In processes where suppliers, accounting departments and banks work together, a change that is invisible in the payee’s data is enough to turn a legitimate invoice into a direct loss.
This case shows how important it is to protect not only accounts, but also the point where a payment is authorised, routed and reconciled. For organisations with branches, contractors and recurring payment volumes, the attack surface includes people, email, ERP systems and bank controls.
How payment diversion happens
The most common pattern is simple in logic but effective in execution: an attacker gains access to a mailbox or an administrative environment and intercepts the moment when a payment is about to be executed. At that point, they replace bank details, payee references or routing information with data they control.
The risk grows when payment processes rely on quick approvals, poor segregation of duties or weak manual checks. If the finance office has no independent controls over changes to vendor master data, the fraud can pass as a normal treasury operation.
Why business email compromise remains effective
Business email compromise campaigns remain among the most profitable techniques because they exploit trust, urgency and routine. Sophisticated malware is not always needed: often an initial access obtained through phishing, reused credentials or abuse of already compromised accounts is enough.
Once inside, the attacker observes the workflows and waits for the best moment to intervene. The strength of this approach lies in hitting existing processes, without having to interrupt operations or draw immediate attention.
Impact on treasury, compliance and business continuity
The financial loss is only the first consequence. An incident of this kind requires fund recovery work, forensic analysis, a review of controls and possible impact on audit and internal governance. Even when operations remain active, the management cost can be significant.
For those leading finance or IT functions, the event highlights a key point: payment security is not only a technical issue, but a process control involving purchasing, finance, legal and security.
Priority countermeasures to reduce risk
The most effective protection combines prevention, detection and independent verification. No single control is enough on its own, especially in contexts with many transactions and distributed suppliers.
- Out-of-band verification for every change to an IBAN, routing number or account holder.
- Segregation of duties between who enters, approves and releases the payment.
- Controls on email and accounts with MFA, alerts and monitoring of anomalous access.
- Limits and thresholds for high-value payments or payments to new beneficiaries.
- Fast reconciliation to identify diversions before funds leave the recoverable circuit.
For companies that make payments to third parties, the priority is to reduce the implicit trust placed in data received by email or in unverified changes to master data. Investing in targeted controls costs far less than a loss in the six figures.