Case Library / Phishing / Medidata Solutions $4.8M CEO-Fraud Wire Transfer (2014)
Phishing Confirmed

Medidata Solutions $4.8M CEO-Fraud Wire Transfer (2014)

Spoofed emails impersonating Medidata's president, backed by a fake "lawyer" caller.

Share:

Social Engineering Examples·5 sources

What Happened

In summer 2014, Medidata told its finance team to be ready to help with urgent transactions tied to a possible acquisition. On September 16, 2014, an accounts payable employee (Alicia Evans) received an email that appeared to come from Medidata's president, complete with his name, email address, and photo in the "From" field. It said an acquisition was near, that it was strictly confidential, and that an attorney named "Michael Meyer" would contact her.

Meyer then phoned her demanding an urgent wire transfer. When Evans said she needed presidential authorization plus sign-off from a VP and the director of revenue, a follow-up group email, again appearing to come from the president, instructed all three to process and approve the payment. Evans entered the payee details Meyer supplied into Chase's online banking system, and the two executives approved it; $4,770,226 was wired to an overseas (Chinese) bank account.

On September 18, "Meyer" requested a second transfer; the VP (Ho Chin) grew suspicious of the reply-to address, contacted the real president directly, and learned he had never made the requests. Medidata contacted the FBI and outside counsel. Investigators found the emails had been spoofed: an unknown actor embedded code so the messages displayed the president's identity while masking the true sender.

Medidata disclosed the roughly $4.8M loss in a September 2014 SEC Form 8-K. This is a fully documented, real incident, confirmed by the company's own SEC filing and multiple federal court opinions.

How the Attack Worked

The scheme layered three pressures. First, authority and impersonation: emails were crafted so Medidata's Gmail-hosted system displayed the president's name, address, and photo, making them look genuinely internal. Second, a fake external "attorney" added legitimacy and a live, insistent human voice by phone, a classic BEC pattern of pairing a spoofed email with a corroborating caller.

Third, secrecy and urgency: the "confidential acquisition" framing discouraged the employee from openly verifying, and the same-day timeline pressured fast action. Crucially, the attackers had context: finance staff had been pre-warned to expect urgent acquisition-related transfers, so the fraudulent request fit an expected pattern. When the employee's control (needing executive sign-off) kicked in, the fraudsters simply produced another spoofed "presidential" email to satisfy it, turning the internal check into part of the con.

The Lure & the Tell

Lure: a spoofed email appearing to be from the company president announcing a confidential, urgent acquisition and directing the employee to cooperate fully with an outside "attorney," reinforced by that attorney's phone call demanding a wire. Tells: the request bypassed normal process (wire demanded because a check would be "too slow"), leaned on secrecy to prevent verification, and originated from addresses that did not truly match the executive.

The scam unraveled only when an executive independently examined a suspicious reply-to address and confirmed the request out-of-band with the real president, the single step that would have caught it earlier.

Outcome

The first $4.77M wire was lost; the second attempt was blocked after an executive's suspicion prompted out-of-band verification. Medidata filed an insurance claim under its $5M Chubb/Federal Insurance "Federal Executive Protection" crime policy; Federal denied coverage, arguing no hacking occurred and that employees transferred the funds voluntarily.

Medidata sued (S.D.N.Y., 1:15-cv-00907). In July 2017 the district court granted summary judgment for Medidata under the policy's computer-fraud and funds-transfer-fraud provisions, awarding about $5.8M. The Second Circuit affirmed on July 6, 2018, holding the spoofing was a covered computer fraud and the proximate cause of the loss. No perpetrators were publicly identified or charged.

Why It Matters

This is a landmark early business email compromise (BEC) case and a foundational cyber-insurance precedent. It shows that no malware or system breach is needed: manipulating what recipients see in the "From" field, plus social pressure, is enough to move millions. It also crystallized a legal question that shaped how crime and cyber policies are written and litigated: whether "computer fraud" coverage extends to spoofing-driven wire fraud where employees themselves push the button.

The court's answer ("larceny by trick is still larceny") helped establish that authorized-but-deceived transfers can still be covered fraud, influencing later BEC coverage disputes.

Defenses

Require out-of-band verification (a known phone number or in-person confirmation) for any wire transfer or change of payee, especially "urgent" or "confidential" executive requests; verification must be independent of the request channel. Treat secrecy demands that discourage checking as a red flag, not a reason to skip controls. Enforce dual-authorization that is genuinely independent (approvers should confirm with the executive directly, not rely on another email).

Deploy email authentication (SPF, DKIM, DMARC) and external-sender/lookalike-domain warnings, and flag reply-to addresses that differ from the display sender. Pre-briefing finance staff to expect urgent transfers, as happened here, can backfire; pair any such heads-up with a mandatory verification protocol.

Sources
Cite this case

Social Engineering Examples. “Medidata Solutions $4.8M CEO-Fraud Wire Transfer (2014)”. Accessed 19 September 2026. https://socialengineeringexamples.com/medidata-solutions-ceo-fraud-wire-2014

Attack Chain & Defense
1Reconnaissance and target profiling
What happened

The court record shows the fraudsters knew Medidata's finance department had been told internally to expect urgent, confidential acquisition-related transfers, and knew the specific names, roles, and email-address format (first-initial-lastname@mdsol.com) of the president plus the accounts-payable clerk, the VP, and the director of revenue. This level of detail is consistent with, though not confirmed in the court opinions as arising from, typical OSINT against a public SEC-reporting company: corporate site, press releases, LinkedIn, and prior monitoring of email traffic patterns.

The control that would have stopped it

Employee-facing OSINT exposure (names, roles, internal heads-up emails about upcoming deals) is very hard to eliminate at enterprise scale for a public company; the realistic control assumes attackers can gather this and hardens the payment process it later gets used against, at Stages 5 and 6, rather than trying to hide it.

2Spoofing infrastructure and technique
What happened

The fraudsters crafted emails using code that exploited how Google's Gmail platform matched an incoming sender address to an internal contact profile, so forged messages displayed the real president's name, email address, and photo in the "From" field, per the district court's factual findings, a display-spoofing technique rather than a look-alike domain registration.

The control that would have stopped it

Deploy and enforce SPF, DKIM, and DMARC, and configure mail platforms not to auto-populate a trusted contact's name and photo based solely on address-matching for externally originating mail; add clear external-sender banners so a message that looks internal cannot pass as such by display tricks alone.

3Initial lure to a finance employee
What happened

A spoofed email, apparently from the president, told accounts-payable employee Alicia Evans that a confidential acquisition was imminent and that an outside attorney ("Michael Meyer") would be in touch, priming her to cooperate and to keep the matter quiet.

The control that would have stopped it

Train staff, especially finance, that a request framed around secrecy or confidentiality is itself a reason to escalate and verify, not a reason to stay quiet; make "don't tell anyone" instructions in a financial request a mandatory trigger for manager or security review.

4Live voice reinforcement
What happened

The fake attorney called Evans directly, demanded an urgent wire transfer, and dismissed a physical check as "too slow," a classic BEC pairing of a spoofed email with a corroborating live caller to add pressure and legitimacy.

The control that would have stopped it

Treat any wire instruction delivered or reinforced by an unverified phone caller, especially a newly introduced outside party like an "attorney," as requiring an independent callback to a previously known number for that person or firm, never a number the caller supplies.

5Defeating the internal control
What happened

When Evans said she needed presidential authorization plus sign-off from the VP and the director of revenue, the attackers produced a second spoofed group email, again appearing to be from the president, instructing all three to process and approve the payment, turning the intended safeguard into a step in the fraud.

The control that would have stopped it

Make dual-authorization genuinely independent of the request channel: approvers should confirm directly with the purported requesting executive through a known-good channel (in person or a previously verified phone number), never by relying on a second email that could be forged the same way as the first.

6Fraudulent transaction execution
What happened

Evans entered the attacker-supplied bank details into Chase's online banking system, and the VP and director of revenue, believing the instruction was genuine, logged in and approved the transfer through the same online system, completing the company's multi-approval process without anyone contacting the president directly.

The control that would have stopped it

Require out-of-band, callback verification for any new or changed wire payee or bank details before funds move, applied as a standing rule rather than only after suspicion arises; this is the same class of check that ultimately caught the second attempted transfer here, just applied too late to stop the first.

7Payout and objective completion
What happened

$4,770,226 was wired to a Chinese bank account on September 16, 2014. A follow-up request for a second wire two days later was stopped only when the VP noticed a suspicious reply-to address and verified out-of-band with the real president, confirming the fraud after the first payout had already succeeded.

The control that would have stopped it

Once funds clear to an overseas account, recovery is largely outside the victim's control (none were recovered directly in this case); the practical fallback demonstrated here is carrying crime and cyber insurance with computer-fraud and funds-transfer-fraud coverage broad enough to respond, and being prepared to litigate a wrongful denial, which is what ultimately made Medidata whole.

Quick Facts
Victim
Medidata Solutions, Inc. (cloud-based clinical trial software company, then NASDAQ-listed under ticker MDSO)
Company
Medidata Solutions, Inc.
Location
New York, NY, USA (litigated in U.S. District Court, S.D.N.Y.)
Date
2014-09-16
Impact
$4.8 million transferred and lost (first wire of $4,770,226 completed, a second attempted wire was stopped).
Medidata later recovered the loss through litigation against its insurer, winning a $5.8M judgment (damages plus interest), affirmed on appeal in 2018.
Status
Confirmed
Case Type
Real-World Incident
Sector
Healthcare, Technology & Software
Explore more

Related Cases

Browse by what this case has in common with others in the library.

Main Line Health W-2 Executive-Spoof Phishing Breach

A spoofed email impersonating a company executive tricked a Main Line Health employee into emailing all ~11,000 staff W-2s to…

Incident 2016Read →

Evaldas Rimasauskas defrauds Google and Facebook of ~$120M with fake "Quanta Computer" vendor invoices

Evaldas Rimasauskas ran a five-year, $120M fraud against Google and Facebook using forged Quanta Computer invoices.

Incident 2013Read →

Doorstep Dispensaree: Unsecured Patient Records Found in a Pharmacy's Back Yard Trigger the ICO's First GDPR Fine (2019)

An unrelated MHRA search warrant found care-home patient prescription and NHS records rotting in unlocked crates and bin bags at…

Incident 2018Read →

Alkem Laboratories: Ascend Laboratories Impersonation BEC and Enzene Biosciences Email Compromise

Fraudsters impersonating named Ascend Laboratories executives convinced an Alkem Laboratories treasury manager to wire Rs 51.30 crore to a fake…

Incident 2023Read →

Anthem health-insurer breach (78.8M records)

A single phishing email opened by an Anthem subsidiary employee in Feb 2014 seeded a nation-state intrusion that stole data…

Incident 2014Read →

OpenAI's "ScopeCreep": Russian-Speaking Actor Used Disposable ChatGPT Accounts to Build C2-Enabled Windows Malware Distributed via a Trojanized "Crosshair-X" Gaming Tool

A Russian-speaking threat actor used disposable, one-conversation ChatGPT accounts to iteratively build and debug a Go-based Windows malware family.

Incident 2025Read →