Summary
- 01What happened
At a US subsidiary, a payment meant for a genuine contractor was sent to a third-party account (company disclosure).
- 02What was found
The company says it uses industry-standard practices for its technology and payment systems. Neither the method nor the stage at which the payment was pointed at another account has been disclosed.
- 03Why it got through
Even when a payment rests on a genuine transaction, it goes to another account unless someone checks that the destination account belongs to that vendor.
A pre-execution check means matching the destination account to the vendor's registered account before paying, and keeping a record. Detection means noticing the diversion after the payment. The payment date and the date of discovery have not been disclosed. The date shown is the company's disclosure.
About £700K went to a third-party account
What got through
- What got through
- A transfer carried out as a payment to a contractor. It went to a third-party account; about £700,000 was sent (Zephyr Energy disclosure).
- What reached the paying side
- In general, the side making a payment sees the vendor’s name, the amount and the destination account. If the account has been swapped but the name and amount match a real transaction, the contents cannot tell it apart.
- Not disclosed
- The method and the route of intrusion. The payment date and the date of discovery. The names of the contractor and of the receiving account. Which subsidiary. Whether any funds were recovered. Whether any data was taken. The company describes the incident as “highly sophisticated”.
Pre-execution check
Whatever the route, the condition for telling them apart is checking the destination account against the vendor’s registered account before paying.
Before paying, check the destination account against the vendor's registered account, not the payment request or invoice.
- Who approves
- The vendor. When an account is newly registered or changed, it approves that account through its registered contact (not a contact written in the payment request or invoice).
- Where it is checked
- The approval step before the payment is carried out. Whether the destination account belongs to the vendor is checked separately from the contents (name and amount). A payment whose account cannot be matched to the registered account is held.
- What is recorded
- Which payment went to which account, and how it was checked, so you can show what was checked before paying for recovery, investigation or insurance.
The diversion was noticed only after the payment had gone through. Similar cases, where a payment to a genuine vendor went to another account, are the Portland Water Bureau (it acted on a request to change a vendor’s bank account) and the City of Liberty, Texas (it paid a request from a lookalike vendor domain).
What Lemma does
Lemma builds the pre-execution check into the side that pays vendors. It does not look for intrusions; it confirms, before the payment, that the destination account is one that could be matched to the vendor’s registered account.
Industries and operations to watch
- IndustrySupply chain
- Organisations that pay substantial single amounts to subsidiaries’ or sites’ contractors.
- OperationBank account changes
- Registering and changing vendors’ bank accounts (whether a change request was involved here has not been disclosed).
- OperationApproval
- Approving payments to contractors.
Current controls vs Lemma
The route in this case is the destination account of a contractor payment. At what stage the account was swapped (an invoice, an account-change request, or inside the payment system) has not been disclosed, so the table has a single column.
| Control | Destination account of a contractor payment |
|---|---|
| Checking the payment’s contents (name and amount) | Not effective |
| Recovery through banks and law enforcement | Partial |
| Lemma (pre-execution check) | Effective |
Checking the contents does not settle it, because the payment was for a genuine contractor and the name and amount cannot tell it apart. Recovery through banks and law enforcement is under way, but it acts after the payment, and whether any funds were recovered has not been disclosed. Lemma checks the destination account, not the contents, against the vendor’s registered account before paying.
Note: Lemma’s check works only when it is built into the approval step before payment, and the vendor’s registered account and contact are managed apart from the payment request or invoice. If the registered account or contact itself has been altered, the check can pass. The table compares what each control checks; it does not show whether this incident would have been stopped. Lemma does not detect or prevent intrusions.
Three things to confirm about payments to vendors
- When a vendor’s account is registered or changed, do you confirm it with the vendor through the registered contact?
- Do you have a step that stops, before execution, a payment whose destination differs from the registered account?
- If a diversion is found after payment, is there a set procedure to contact the bank immediately?
Facts and timeline
- Party
- Zephyr Energy plc, a UK oil and gas company listed on the London Stock Exchange’s AIM. One of its US subsidiaries was targeted.
- What happened
- A single payment meant for a contractor was diverted, and about £700,000 was sent to a third-party account. The company calls it a “highly sophisticated” cybersecurity incident.
- Company practices
- The company says it uses industry-standard practices for its technology and payment systems.
- Company systems
- A leading cybersecurity consultant assessed its IT systems; the company says the incident is contained and operations continue as normal.
- Impact
- The board says the company has more than sufficient working capital and does not expect this isolated matter to affect ongoing operations.
Glossary
RNS — The London Stock Exchange's regulatory news service, used by listed companies to disclose information that may affect their share price.
Payment diversion — A payment meant for its intended recipient is sent to a different account. The method (altered invoice, hijacked correspondence and so on) varies by case.
Timeline
- Payment date (not disclosed)
- A single payment to a contractor is sent to a third-party account.
- Discovery date (not disclosed)
- The company notices the diversion and notifies law enforcement.
- 2026-04-09
- The company discloses the incident through a London Stock Exchange regulatory announcement (RNS 7163Z).
The facts rely on Zephyr Energy’s disclosure (primary). Press coverage (TechCrunch, The Register) repeats the disclosure; we found no further facts. Statements in the coverage that an invoice’s bank details were altered, or that this was a typical business email compromise, are inferences. The company has not disclosed the method. What has not been disclosed does not mean there were no controls.
After disclosure
- Zephyr Energy: Says it notified law enforcement immediately on discovery and is working with the corresponding banks and consultants to recover the diverted funds. It says it has added further security layers (details not disclosed). Its consultants continue to monitor its systems.
Sources
- Primary, regulatory announcementZephyr Energy plc “Cybersecurity incident” (RNS 7163Z, 2026-04-09)
2 more (reporting, analysis)
- PressTechCrunch “Hacker stole £700,000 from U.K. energy company by redirecting payment”
- PressThe Register “Zephyr Energy loses £700K to contractor payment fraud”
References: “The last layer left in AI-era cyber defense”