how it happened
- whofraudsterposed as a real supplier
- the gapaccounts payablefamiliar name, believable bill
- the result$120M+ sentfrom two companies
what everyone assumed
Accounts-payable runs on a reasonable shorthand: a bill from a vendor you recognize, referencing work you actually contracted, is almost certainly real. That is how the volume gets handled at all, and it is how the controls are designed, with the supplier’s identity standing in for a deeper check. The belief held perfectly well for every genuine invoice that ever came through, which is exactly why the fake ones moved with it.
what happened
Between 2013 and 2015, Evaldas Rimasauskas ran the same play over and over. He registered a company in Latvia using the name of Quanta Computer, the real hardware supplier the two companies worked with, then sent invoices, contracts, and letters that matched what a legitimate Quanta bill would look like, complete with forged corporate stamps and signatures. The payments went out to bank accounts he controlled in Latvia, Cyprus, and elsewhere, then moved on again. There was no break-in and no malware, just a familiar name on a believable invoice, repeated patiently until the totals were enormous. Each payment, on its own, looked exactly like the routine ones around it.
step by step
- 2013a Latvian company registered as Quanta ComputerThe name of a real supplier both companies used.
- invoices that look exactly like the real onesForged stamps and signatures on believable bills.the assumption breaks here
- 2013 to 2015payments flow to accounts he controlsMore than USD 120 million: about 99 million from Facebook, 23 million from Google.
- 2017 to 2019arrest, guilty plea, 60 monthsMuch of the money is recovered.
how it surfaced
By the time it surfaced, the scheme had induced the two companies to wire out more than USD 120 million, with about USD 99 million coming from Facebook and about USD 23 million from Google. Rimasauskas was arrested in Lithuania in 2017, extradited, and pleaded guilty to wire fraud in March 2019. In December 2019 a federal court in Manhattan sentenced him to 60 months in prison and ordered forfeiture and restitution. Much of the money was recovered, which is the unusual part. The ordinary part is how far a real supplier’s name traveled before anyone questioned it.
A familiar name on an invoice is not proof of who sent it.
The only thing that confirms a payment instruction is a check that runs outside the message, against a channel the sender does not control.
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 mattersA fraudster sends invoices in the supplier's name with new bank details.what it costs youYou keep paying for months before anyone notices the real supplier was never paid.
- 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 happenedOrion, 2024howAn employee gets a convincing request and sends several wires.what leavesmoney that is not recoveredwho ends up with ita criminal scheme
sources
- U.S. Department of Justice, Southern District of New York, [Lithuanian Man Sentenced To 5 Years In Prison For Theft Of Over $120 Million In Fraudulent Business Email Compromise Scheme]
- FBI, [Ringleader of Business Email Compromise Scheme Sentenced]
- CNBC, [How this scammer used phishing emails to steal over $100 million from Google and Facebook]
your turn
what you can do about it
this week
Take your largest recurring vendor payment and check what would actually stop a forged invoice or a changed bank account: is there a verification step that does not depend on the incoming message itself.
An invoice is sitting in your approval queue right now from a supplier you recognize, and that recognition is doing most of the verifying, which is why nobody is pausing on it. The question the quiet months ask is whether a single believable email could move real money before anyone called a known number to confirm. The Facebook and Google gap lived for two years inside exactly that missing step.
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 →
