Case Library / Phishing / AFGlobal Corp. $480K CEO-impersonation wire fraud (2014)
Phishing Documented incident

AFGlobal Corp. $480K CEO-impersonation wire fraud (2014)

A fraudster posing as AFGlobal's CEO, backed by a fake KPMG "attorney," pressured the accounting director into wiring $480,000 to a Chinese bank; a follow-up $18M ask blew the scheme.

Share:

Social Engineering Examples·5 sources

What happened

In May 2014, AFGlobal alleged that its director of accounting received emails purporting to come from the company's CEO and assigning a "strictly confidential financial operation" tied to a supposed acquisition in China. The messages directed the employee to coordinate only with the CEO and a purported KPMG attorney and invoked SEC regulations to discourage discussion. According to the allegations reproduced by Krebs on Security, the purported attorney followed up by phone and email with instructions for a $480,000 transfer to an Agricultural Bank of China account. A later request for $18 million prompted suspicion and was not paid. AFGlobal filed an insurance claim, Federal Insurance denied coverage, and AFGlobal sued. The cited docket index records a dismissal with prejudice on February 6, 2017, but does not establish settlement terms, a payment, or a merits ruling. The attacker was not publicly identified in the cited reporting.

How it worked

The reported scheme used two claimed sources of authority: emails purporting to come from the CEO and phone and email communications from a purported outside attorney. The messages invoked authority, urgency, confidentiality, and SEC compliance to discourage independent verification. AFGlobal alleged that the imposter appeared familiar with company procedures and the existing relationship between the executive and accounting director; this remains a party allegation rather than proof of how the attacker obtained that knowledge.

The lure and the tell

Lure: an email from the "CEO" naming a confidential deal ("manage file T521"), directing the employee to work only with the CEO and a named attorney and to keep silent to avoid SEC issues, followed by phone-and-email wire instructions from the fake attorney. Tells: the demand for secrecy and single-channel communication (a deliberate block on verification), pressure and urgency around a large wire to a foreign bank, an unusual acquisition/due-diligence narrative, and ultimately the escalation to an implausible $18M request. Any of these should trigger independent, out-of-band verification of the executive and the payment.

Outcome

The $480,000 transfer was reported as unrecovered, while the later $18 million request was not paid. Federal Insurance denied AFGlobal's claim, disputing coverage under the cited policy provisions, and AFGlobal sued for breach of contract and bad faith. The cited docket index records termination on February 6, 2017 following a stipulation of dismissal with prejudice. That procedural disposition does not itself disclose a settlement, payment, or merits determination.

Why it matters

The case is a documented example of an employee-authorized BEC transfer followed by a coverage dispute. It illustrates two practical risks: social engineering can induce an authorized employee to initiate a transfer, and reimbursement depends on the terms and application of the relevant insurance policy. The dismissal with prejudice does not establish a judicial ruling on those coverage questions.

Defenses

Require out-of-band verification (a call-back to a known number, not one supplied in the email) for any wire request, especially urgent, confidential, or executive-initiated ones. Treat demands for secrecy and single-channel communication as red flags, not compliance. Enforce dual authorization and a callback threshold for large or foreign wires. Train finance staff that authority, urgency, and secrecy together are the classic BEC pattern, and that even a familiar executive's request must be verified. Use email authentication (SPF/DKIM/DMARC) and external-sender/look-alike-domain warnings. Confirm in advance which insurance policy, if any, covers social-engineering fraud, since standard cyber/crime coverage often excludes voluntarily-authorized transfers.

Sources

Provenance. The incident narrative relies on secondary press and legal analysis. The CourtListener RECAP docket index is cited directly for the February 6, 2017 termination and stipulation of dismissal with prejudice. The underlying stipulation and insurer denial letter were not independently retrieved in this pass.

Cite this case

Social Engineering Examples. “AFGlobal Corp. $480K CEO-impersonation wire fraud (2014)”. Accessed 3 November 2026. https://socialengineeringexamples.com/afglobal-ceo-fraud-bec-2014

Attack Chain & Defense
1Reconnaissance
What happened

The cited reporting does not establish how the attacker selected the company, identified the accounting director, or obtained contextual information.

The control that would have stopped it

Because the reconnaissance method is undisclosed, defenses should not depend on assumptions about how the target was selected. Payment controls should treat contextual familiarity as insufficient verification.

2Persona and pretext setup
What happened

Emails purported to come from AFGlobal's CEO, while a second person presented as a KPMG attorney in follow-up phone and email communications.

The control that would have stopped it

Flag external messages that claim to be from executives or professional advisers, and independently verify the sender before acting on payment instructions.

3Initial phishing contact
What happened

A message purporting to be from the CEO reached the accounting director, assigning him a "strictly confidential financial operation," invoking SEC-compliance secrecy, and instructing him to communicate only through that single channel, pre-emptively shutting down normal verification habits.

The control that would have stopped it

Train employees to treat any instruction demanding confidentiality and single-channel communication as a red flag rather than a legitimate compliance requirement, and require independent verification of unusual high-value or urgent requests regardless of the stated justification.

4Trust reinforcement via secondary impersonation
What happened

Shortly after, the fake KPMG attorney contacted the director by phone and email, corroborating the CEO's story and supplying specific wire instructions for a China-acquisition "due diligence fee," adding social proof and urgency on top of the initial authority pressure.

The control that would have stopped it

Mandate out-of-band verification, a callback to an independently sourced phone number, never one supplied in the suspect email or by the caller, for any payment instruction that arrives through or is corroborated by a third party claiming to act on an executive's behalf.

5Fraudulent wire execution
What happened

Under combined authority, urgency, and secrecy pressure, and with normal out-of-band verification discouraged by the pretext itself, the director wired $480,000 to an account at the Agricultural Bank of China.

The control that would have stopped it

Enforce dual authorization and a mandatory callback-verification threshold for large or first-time international wire transfers, so a single employee's authorization is never sufficient to release funds of this size.

6Outcome
What happened

The $480,000 transfer was reported as unrecovered, and a later request for $18 million prompted suspicion and was not paid.

The control that would have stopped it

Rapid detection and immediate bank notification can support a recall attempt, but prevention through independent verification and dual authorization remains the stronger control.

Quick Facts
Victim
AFGlobal Corporation, legally Ameriforge Group Inc., a Houston-based manufacturer
; the targeted employee was its director of accounting.
Company
AFGlobal Corporation
Location
Houston, Texas, USA
Date
2014-05-21
Impact
$480,000 was wired to an Agricultural Bank of China account and reported as unrecovered.
BasismeasuredWire amount and subsequent demand reported from AFGlobal's allegations in the coverage litigation
A subsequent request for $18,000,000 was not paid. The $480,000 loss became the subject of an insurance-coverage dispute.
Status
Documented incident
Case Type
Real-World Incident
Sector
Defense & Aerospace, Manufacturing & Industrial
Threat Actor
unknown
Explore more

Related Cases

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