how it happened
- whofraudstersconvincing requests
- the gapwire transferslooked legitimate
- the result~$60M lostno systems breached
what everyone assumed
There is a quiet confidence that wire fraud is a problem for the inattentive: small firms without controls, people who do not check. A large public company with finance staff and approval chains feels insulated by its own size. The belief is reasonable, because the people who process payments are skilled and the process exists for exactly this reason. What the belief misses is that a convincing instruction does not need to break the process. It only needs to ride inside it.
what happened
Here the span was short, measured in the transfers themselves rather than in months of silent access. According to Orion’s SEC filing, an employee, described as not a named executive officer, was deceived by a criminal scheme into making multiple unauthorized wire transfers to accounts controlled by third parties. Each transfer was an ordinary action by someone doing their job. There was no intrusion to detect, no malware, no unusual login. The thing that moved the money was a person following what looked like a legitimate request, which is why nothing flagged until the money was already gone.
step by step
- an employee receives what looks like a real requestPart of a criminal scheme.
- multiple wire transfers are madeEach an ordinary action by someone doing their job.the assumption breaks here
- no intrusion, no malware, no odd loginSo nothing flags it until the money is gone.
- 2024a charge of about 60 million dollarsDisclosed in Orion's SEC filing.
how it surfaced
When the scheme came to light, the total stood at roughly 60 million dollars. The company disclosed that it expected to record a one-time pre-tax charge of about that amount for the unrecovered transfers, said it found no evidence of unauthorized access to its data or systems, and that operations were not disrupted. The loss was not a breach in the usual sense. It was a sequence of authorized payments that should never have been authorized.
Wire fraud does not test your firewall.
It tests whether a believable request can travel from inbox to bank without a step that confirms the request is real. Size does not supply that step, and skilled staff acting in good faith are exactly who the scheme is built for.
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersThe employee makes several transfers, each one an ordinary task.what it costs youThe money is gone before anyone realises the request was fake.
- or it goes like thisit happenedArup deepfake fraud, 2024howA video call full of deepfaked executives asks for urgent transfers.what leavesmoney, in several transfers in one daywho ends up with itfraudsters who built the call
- or it goes like thisit happenedFacebook and Google, 2019howInvoices arrive in a real supplier's name with new bank details.what leavesmonths of supplier paymentswho ends up with ita fraudster abroad
sources
- The Record, "Carbon black supplier Orion loses $60 million in business email compromise scam" ,
- The Register, "Orion SA says scammers conned company out of $60 million" ,
- Help Net Security, "Scammers dupe chemical company into wiring $60 million" ,
- Infosecurity Magazine, "Manufacturing Firm Loses $60m in BEC Scam" ,
your turn
what you can do about it
this week
Check what your process requires before a large or unusual transfer leaves: whether a change of bank details or a new payee triggers a verification on a known channel, separate from the message that asked, and whether that step is mandatory rather than a courtesy a busy day can skip.
Someone in your finance function will get a payment instruction this week that looks legitimate and carries some urgency, and acting on it is the job. The Orion loss turned on payments that were authorized but never independently confirmed.
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
