Case Library / Phishing / SEC Section 21(a) Report on Nine Issuers' Business Email Compromise Losses
Phishing Documented incident

SEC Section 21(a) Report on Nine Issuers' Business Email Compromise Losses

The SEC's 2018 Section 21(a) report detailed how fake-executive and fake-vendor BEC emails caused nearly $100 million in combined losses at nine public companies and examined how internal accounting controls should account for cyber-related fraud.

Share:

Social Engineering Examples·2 sources

What happened

On October 16, 2018, the U.S. Securities and Exchange Commission issued Release No. 34-84429, a Report of Investigation under Section 21(a) of the Securities Exchange Act of 1934, describing business email compromise frauds that had struck nine unnamed public companies in the technology, machinery, real estate, energy, financial, and consumer-goods sectors. The Commission determined not to pursue enforcement actions against the issuers based on the conduct and activities known at that time. Each issuer lost at least $1 million, two lost more than $30 million, and combined losses approached $100 million, almost all of which was unrecovered. The frauds involved fake-executive schemes using spoofed executive identities and fake-vendor schemes using compromised foreign-vendor email accounts. The report explains that internal accounting controls should account for these cyber-related risks, while expressly stating that victimization by such a scam does not by itself mean an issuer violated the federal securities laws.

How it worked

Fake-executive variant: attackers spoofed the email domain or address of a company executive, typically the CEO, and emailed finance personnel with time-sensitive instructions to wire funds. The messages directed personnel to coordinate with a purported outside attorney using real law-firm and attorney names, who supplied instructions for foreign accounts controlled by the perpetrators. The messages emphasized secrecy and sometimes contained spelling or grammatical errors or false references to government oversight. Fake-vendor variant: perpetrators compromised foreign vendors' email accounts, inserted illegitimate payment requests into communications concerning otherwise legitimate transactions, corresponded with issuer personnel to obtain purchase-order and invoice information, and supplied doctored invoices or fraudulent bank changes. The report found that the frauds succeeded at least in part because responsible personnel did not sufficiently understand existing controls or did not recognize signs that the electronic instructions were unreliable.

The lure and the tell

The lure: an email that looked like it came from the company's own CEO or a real, currently-corresponding vendor, wrapped in urgency and, in the fake-executive cases, secrecy from other company employees. The tell, in hindsight: out-of-domain or spoofed sender addresses that a careful header check would have caught; requests to bypass or reinterpret established dual-authorization / authorization-matrix controls; wire instructions to newly designated foreign accounts with no independent verification call placed; in some fake-executive emails, spelling/grammar errors or oddly specific but false invocations of SEC/government process; and, in fake-vendor cases, an invoice or bank-change request arriving with no advance notice inside an otherwise-legitimate thread, discoverable only when the genuine vendor separately complained about a past-due bill that had, unbeknownst to them, already been "paid" to the wrong account.

Outcome

The Commission determined not to pursue enforcement actions against the nine issuers based on the conduct and activities known to it at the time. It issued the Section 21(a) report to alert issuers and market participants that spoofed or manipulated electronic communications should be considered when devising and maintaining internal accounting controls. Almost all of the nearly $100 million lost across the nine issuers was unrecovered. The report expressly states that an issuer is not necessarily in violation of the internal-accounting-controls requirements merely because it becomes the victim of a cyber-related scam.

Why it matters

The report shows that cyber-related fraud can implicate the design and operation of internal accounting controls even when perpetrators use spoofed or compromised communications rather than intruding into an issuer's own systems. It emphasizes that controls depend on the personnel who implement and follow them, and that issuers should reassess controls as risks evolve. It also cautions that victimization alone does not establish a securities-law violation and leaves issuers to develop controls suited to their operational needs and risks.

Defenses

Practical defenses consistent with the report's findings include: (1) enforce appropriate authorization requirements for outgoing payments; (2) train responsible personnel to understand authorization policies and recognize unreliable electronic instructions; (3) independently verify vendor bank-detail changes using established contact information; (4) review unusual payment requests, including those involving secrecy, urgency, or foreign accounts; (5) strengthen account reconciliation and outgoing-payment notifications to improve detection; and (6) periodically reassess internal accounting controls against evolving cyber-related fraud risks. The report notes that the issuers enhanced payment authorization, vendor-change verification, reconciliation, notification, and training after the frauds.

Sources
Cite this case

Social Engineering Examples. “SEC Section 21(a) Report on Nine Issuers' Business Email Compromise Losses”. Accessed 3 November 2026. https://socialengineeringexamples.com/sec-21a-report-nine-issuers-bec-2018

Attack Chain & Defense
1Reconnaissance
What happened

the SEC report does not describe how the perpetrators researched their targets. It establishes that fake-executive schemes used real law-firm and attorney names and contacted finance personnel, while fake-vendor perpetrators corresponded with issuer personnel to obtain information about actual purchase orders and invoices.

The control that would have stopped it

because the report does not establish the perpetrators' reconnaissance methods, controls should focus on independently validating sensitive payment instructions rather than assuming familiarity with real executives, attorneys, vendors, or transactions establishes authenticity.

2Infrastructure setup
What happened

for the fake-executive variant, per the report, attackers needed only to create an email address or domain that superficially mimicked the executive's identity, described in the report as technologically unsophisticated. For the fake-vendor variant, the report describes a more technically involved step: attackers first gained unauthorized access to a real foreign vendor's actual email account or system before impersonating anyone.

The control that would have stopped it

commercial domain-monitoring and lookalike-domain detection services can flag newly registered spoofed executive domains; the fake-vendor path is a security failure at the vendor, outside the issuer's direct control, so the practical countermeasure shifts to how the issuer verifies incoming payment instructions regardless of the vendor's own security, covered at Stage 5.

3Initial contact and pretext delivery
What happened

fake-executive emails typically went to midlevel personnel who rarely communicated with the spoofed executive and described time-sensitive transactions requiring secrecy. Fake-vendor perpetrators used compromised vendor accounts, inserted illegitimate payment requests into communications for otherwise legitimate transactions, and corresponded with issuer personnel to obtain purchase-order and invoice information.

The control that would have stopped it

spoofed-domain filtering can help flag some fake-executive messages. Messages from compromised vendor accounts may appear legitimate, so payment and bank-change verification remains necessary even when the sender address is familiar.

4Redirect to a fraudulent payment channel
What happened

fake-executive emails directed staff to coordinate with a purported outside attorney, using real law-firm and attorney names, who then supplied wiring instructions to foreign accounts the perpetrators controlled. Fake-vendor schemes instead inserted a doctored invoice or a bank-detail change request into the hijacked thread, redirecting payment on an otherwise-legitimate outstanding invoice.

The control that would have stopped it

staff training, specifically the awareness training the SEC report itself recommends, keyed to these two exact pretexts, so personnel treat unsolicited secrecy framing, a newly introduced outside attorney, or any bank-detail change request as a red flag requiring escalation rather than compliance.

5Authorization and verification weaknesses
What happened

the report found that the frauds succeeded at least in part because responsible personnel did not sufficiently understand existing controls or did not recognize indications that the emailed instructions were unreliable. Examples included bypassing a dual-authorization requirement, misreading an authorization matrix, and processing vendor banking changes based on compromised communications.

The control that would have stopped it

enforce appropriate authorization for wire transfers and require out-of-band verification, using independently established contact information, for unusual payment instructions or vendor bank-detail changes. The report says issuers enhanced payment-authorization procedures and vendor-information verification after the frauds.

6Sustained extraction
What happened

attackers repeated the pattern to maximize proceeds before anyone noticed. The report's two detailed examples: one company made 14 wire payments to the fake executive's instructions over several weeks, losing more than $45 million, and another paid eight fraudulent invoices totaling $1.5 million over several months.

The control that would have stopped it

strengthen account reconciliation and outgoing-payment notification processes so fraudulent payments can be detected more promptly, as the investigated issuers did after the incidents.

7Payout and objective completion
What happened

funds were moved into foreign bank accounts controlled by the perpetrators; per the report, almost none of the nearly $100 million lost across the nine issuers was ever recovered, and the schemes were typically uncovered only through a third party, such as an alert foreign bank or the real vendor complaining about a past-due invoice, rather than through the victim company's own controls.

The control that would have stopped it

establish rapid escalation procedures involving financial institutions and law enforcement after suspected fraudulent payments. The report shows that third-party alerts from foreign banks or law enforcement helped uncover some protracted schemes, but almost all aggregate losses remained unrecovered.

Quick Facts
Victim
Nine unnamed U.S. public companies
(aggregate), spanning technology, machinery, real estate, energy, financial, and consumer-goods sectors
Location
United States
(nine unnamed U.S. public companies across technology, machinery, real estate, energy, financial, and consumer-goods sectors, listed on national exchanges)
Date
2018-10-16 (SEC report release date; underlying frauds occurred in prior years)
Impact
Aggregate losses across the nine issuers were nearly $100 million.
BasismeasuredAggregate and per-issuer bands stated in the SEC's own Section 21(a) report
Per the SEC report: each of the nine issuers lost at least $1 million; two lost more than $30 million each; one lost more than $45 million; almost all losses were unrecovered. The report's two detailed examples: a fake-executive scheme with 14 wire payments over several weeks causing over $45 million in losses, and a fake-vendor scheme with eight fraudulent invoices totaling $1.5 million paid over several months.
Status
Documented incident
Case Type
Real-World Incident
Sector
Cross-Sector / Multiple Industries
Threat Actor
unknown
Explore more

Related Cases

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