← All Insights

Family Office Wire Fraud: Ubiquiti's $46 Million Email

· 8 min read

Family office wire fraud rarely involves a break-in. It involves a message that appears to come from the principal, a lawyer, or a bank, a payment instruction that sounds entirely plausible, and a staff member who does what authority appears to have asked. The defence is not better software. It is a written rule that no email, from anyone, can move money on its own.

In 2015, Ubiquiti Networks,1 a publicly traded maker of networking equipment,2 disclosed that its finance staff had sent $46.7 million6 out of a Hong Kong subsidiary to overseas accounts,1 after receiving requests that appeared to come from company executives and an outside lawyer. The company's investigation found no evidence that its systems had been penetrated.1 Nobody stole a password. Someone studied who gave orders, imitated the tone, asked for transfers, and the instructions were followed. About $8 million came back quickly3 and a further sum was frozen by court order;1 most of it was still being pursued when shareholders were told.

A family office is the same shape of target, only smaller and quieter: one or two people release payments, the principal travels, instructions arrive by email, and a property closing or a tax estimate is large enough that one unusual wire does not look unusual. The weeks after a sale sharpen that shape further — a big cash balance, a thin team, and a stream of legitimate-looking payments to people the office has never paid before. The questions below are for whoever moves the money, including the principal.

Who can actually release a wire, and can any one person do it alone?

A good answer names the people and separates the roles: one person prepares a payment, a different person releases it, and above a stated amount a principal confirms on a channel that is not the email. Crucially, the bank's own settings enforce the split — two logins, two approvals — rather than a sentence in the office handbook. In a team of two or three, the second pair of eyes is designed on purpose: the principal plus one staff member, or the bank's second-approval feature.

A weak answer sounds like loyalty. "The controller handles it." "I approve everything myself." "The principal can always override." A single pair of hands is exactly what the Ubiquiti fraud exploited, and a rule that lives only in a document is a suggestion, not a control.

The difference is the whole fraud. If one person can receive an instruction and execute it, the attacker only has to persuade one person — and headcount alone will never create the second check. The rule has to.

How does the office confirm a new account, or a change to an existing one?

A good answer refuses to treat the message as evidence. New bank details are never accepted from the email that delivers them. Someone calls the recipient on a number the office already held — not one in the signature block, not one the caller supplies — and reads the digits back. Who was reached, and when, gets written down. On a large first payment, a small test amount goes first and its arrival is confirmed before the balance follows.

A weak answer checks the document against itself. "The instructions were on letterhead." "We replied on the thread and they confirmed." Letterhead is a PDF, and a reply that travels down the same channel as the fraud is an echo, not a check.

This matters because most of these schemes are not exotic. They are a vendor with updated banking details, a title company with a new account for a closing, a tax payment with fresh routing numbers. The change is the attack, and a changed account number deserves to be treated as a brand-new relationship until a voice confirms it.

What is the rule when the request is urgent, confidential, and comes from the principal?

This is the question principals rarely ask, because the answer feels like an insult. A good answer is that the office slows down anyway. Urgency plus secrecy — "I'm closing something, keep it quiet, send it today" — is the standard script precisely because it mimics how founders genuinely behave. Staff call back on a known number first, and the principal has said in advance, in writing, that the call is expected and a delayed wire will never be punished.

A weak answer flatters speed. "They know my voice." "We don't embarrass the founder by checking." An office where staff fear questioning the principal has, in effect, authorised anyone who can imitate them.

The forged Ubiquiti instructions were not clumsy. They described confidential deal activity and directed the recipient to an outside lawyer.4 Rank, and the instruction not to widen the circle, were the mechanism. An instruction that cannot survive a two-minute phone call should not move the cash.

Whose numbers are on the callback list, and when was that list written?

A good answer is a short page written in the calm before a transaction, not assembled from the correspondence asking for money: a number for each principal, the lawyers, the bank's wire desk, the title company, the counterparty — each collected in person or from a relationship that predates the deal. A changed number is confirmed on the old one first. Some offices add a code word agreed face to face, for the day a voice on the phone is no longer proof on its own. The list is refreshed whenever a sale, a refinancing, or a large gift is about to create new payees.

A weak answer lives in the signature block. "Everyone's mobile is on the email." "Caller ID showed the law firm." Displayed numbers can be manipulated, and confirming a fraud on a number the fraud supplied is the same mistake made out loud.

Which outsiders could be impersonated here, and has anyone rehearsed refusing them?

A good answer lists the roles rather than the names: the estate attorney, the property lawyer at a closing, the private banker, the accountant sending tax instructions, the fund administrator issuing a capital call — the notice asking investors to send money they already committed. Each is a plausible source of a large, legitimate request. The list also includes requests that merely look official, from a bank or a government agency, because the same reflex that pays a lawyer hands over family documents to an authority nobody wants to obstruct. Staff have a sentence they are permitted to use — "I'll call you back on the number we already have" — and once a year someone sends the office a convincing fake, with the principal's knowledge, to see whether the rule holds.

A weak answer draws the circle too small. "We've worked with them for years." "A message from a government domain is safe to answer." Familiarity makes the fraud easier, not harder, because an email matching an established pattern is read less carefully. Long tenure is what the attacker is counting on.

What has the bank been asked to do that it is not doing by default?

A good answer is that the office deliberately switched on the protections the bank already offers: a daily ceiling on outgoing wires, a mandatory bank call-back above a set amount, named individuals who alone may initiate, and an instant alert to the principal's phone for every payment that leaves. These are standard services, available on request, and most offices never turn them on.

A weak answer is "the bank would flag anything suspicious." A wire sent by the office's own authorised employee, on apparent instruction, is not suspicious to the bank — processing it is the job. The bank will help, but it has to be asked, in writing, before anything goes wrong.

If the money left ten minutes ago, who gets called first?

A good answer is a short list kept on paper, not in an inbox: the bank's wire-fraud desk on a direct line, with the amount, the time, the receiving bank and the account number ready and a recall requested; then law enforcement, including the FBI's Internet Crime Complaint Center at ic3.gov;5 then counsel and the insurer. Recovery is a race measured in hours, not weeks — once funds are split across onward accounts, the trail goes cold. The list also names who may make those calls when the principal is unreachable, because the fraud will be timed for exactly that moment.

A weak answer postpones the hour. "The banker will sort it out Monday." "Insurance covers it." "IT will check whether we were hacked." Hunting for a break-in can burn the window on the wrong question entirely, and crime policies often treat a payment the office itself sent quite differently from a breached network.

How to use this list

These seven questions fit on one page: who may move money, how a new account is confirmed, what urgency does not excuse, who to call if a wire has already gone. Owners in this position should work through them in a single sitting with whoever releases funds, and write the answers down. Any shrug, any "they know me," any "the bank would have caught it," marks the point of entry. The fix in almost every case is a phone call to a number the office already has — the cheapest control in finance, and the one $46.7 million once depended on.

Sources

Figures marked with a superscript were checked against these sources on November 20, 2026.

  1. Ubiquiti Networks, Inc. Form 8-K sec.gov — In 2015, Ubiquiti Networks disclosed that its finance staff had sent roughly $46.7 million out of a Hong Kong subsidiary to overseas accounts.
  2. Ubiquiti - Wikipedia en.wikipedia.org — Ubiquiti Networks is a publicly traded maker of networking equipment.
  3. Ubiquiti Networks Says It Was Victim of $47 Million Cyber Scam nbcnews.com — About $8 million of the fraudulently transferred funds came back quickly.
  4. UBIQUITI NETWORKS, INC. - FORM correspondence sec.gov — The forged Ubiquiti instructions described confidential deal activity and directed the recipient to an outside lawyer.
  5. About - Internet Crime Complaint Center (IC3) ic3.gov — The FBI's Internet Crime Complaint Center is located at ic3.gov.
  6. How A Tech Billionaire's Company Misplaced $46.7 Million And Didn't Know It - Forbes forbes.com — $46.7 million