A European subsidiary of Toyota parts maker Toyota Boshoku transferred up to about 4 billion yen (~$37M) to criminals in August 2019 after acting on fraudulent payment instructions; the audited accounts later booked a 3,393 million yen loss.
Social Engineering Examples·12 sources
On 14 August 2019, a European subsidiary of Toyota Boshoku Corporation was tricked into transferring funds to an attacker-controlled bank account on the basis of what the company called "fraudulent payment directions from a malicious third party." The parent company disclosed the incident in a first-party press release on 6 September 2019, giving a maximum expected loss of about 4 billion yen (roughly $37.5 million). That figure is an announced ceiling set three weeks after the event, not a settled loss: the audited accounts for the year ended 31 March 2020 booked 3,393 million yen for the incident in other expenses. The release did not name the subsidiary, but Nikkei and Nikkan Kogyo Shimbun both identified it on disclosure as Toyota Boshoku Europe N.V. of Zaventem, Belgium, the group's Europe and Africa regional headquarters, a role the company's own securities report confirms. Toyota Boshoku and the subsidiary recognized the payment directions were fraudulent shortly after the funds left, assembled a team of legal professionals, reported the loss to local investigating authorities, and began efforts to secure and recover the money. The release promised to disclose any amendment to the March 2020 earnings forecast "if this incident makes such revision necessary"; the narrower condition that revision turned on funds not being recovered appears only in secondary coverage. Citing the confidentiality of the ongoing criminal investigation, Toyota Boshoku released no technical details about the attacker's entry vector, whether a mailbox was hijacked or an identity impersonated, how many transfers were involved, or how much (if any) was ultimately recovered. The English and Japanese releases date the estimate differently, 5 September and 6 September respectively.
The BEC and email labels are press characterization, not company disclosure. Toyota Boshoku never said email: both releases describe only fraudulent payment directions from a malicious third party. Nikkei xTECH, which raised BEC first, was explicit that the method was undisclosed and that BEC was one possibility. The classification is still the right one on the facts that are public: an apparently authoritative, routine-looking instruction to move funds that a staffer with payment authority accepted as genuine. Public disclosures do not specify whether the attackers hijacked a legitimate mailbox or impersonated a trusted party (e.g. an executive or supplier), nor whether existing account details were changed. No malware exploit or system takeover was reported as the cause; the leverage was social engineering of a person, not a technical breach. Nikkei reported the company's statement that no employee was involved.
Lure: a payment instruction that looked legitimate and routine to a finance staffer, exploiting trust in an apparently authoritative sender. Tells (general to BEC, not confirmed specifics of this case): a request to change existing bank/account details, pressure to act quickly, and instructions that bypass normal verification, any of which should trigger an out-of-band callback to a known contact before money moves.
Up to about 4 billion yen (~$37.5M) transferred out before the fraud was caught, the maximum the company announced on 6 September 2019. The audited figure is lower: 3,393 million yen, recognized in other expenses for the year ended 31 March 2020 in both the results release and the annual securities report for the 95th term. Toyota Boshoku never explained the gap between ceiling and booked charge, and never disclosed a recovery amount. The booked figure does not track progressive recovery: the cumulative charge was 3,333 million yen at the half year, rose to 3,414 million yen at nine months, and settled at 3,393 million yen at year end, a path consistent with retranslating a euro-denominated amount rather than clawing money back. The line stands at nil the following year, with no recovery income recorded anywhere in those accounts. The company reported the loss to local authorities, opened a criminal investigation, engaged legal professionals, and pursued fund recovery; it warned of a possible earnings-forecast revision. It later stood up a recurrence-prevention committee under the president, revised transaction and business flows, made system changes, ran staff training, and sent repeated fraud-warning emails to every manager and to overseas accounting heads. No perpetrator identification has been made public.
A loss of roughly $37M at a subsidiary of a major, sophisticated multinational shows BEC succeeds through people and process gaps, not necessarily technical defenses. Large distributed enterprises are especially exposed at foreign subsidiaries where payment approval, verification norms, and reporting lines can be looser. The case is a benchmark example of BEC scale and of the value of segregation of duties and independent verification on payment changes.
Require out-of-band verification (callback to a pre-known number) for any new payee or change to existing bank details. Enforce segregation of duties and multi-person approval for large transfers so no single employee can initiate and authorize a payment. Set escalating thresholds for wire approvals. Train finance and AP staff to treat account-change requests as high-risk regardless of apparent sender authority. Harden email against account takeover (MFA, anti-phishing at the mail gateway, external-sender and lookalike-domain flags). Pre-establish an incident playbook including immediate bank/law-enforcement notification (e.g. IC3 in the US) to maximize the chance of freezing/recovering funds.
Social Engineering Examples. “Toyota Boshoku European Subsidiary $37M BEC (2019)”. Accessed 3 November 2026. https://socialengineeringexamples.com/toyota-boshoku-europe-bec-37m-2019
BEC operators typically research a target company's corporate structure, subsidiaries, suppliers, and finance staff using sources like LinkedIn, company websites, business registries, and prior data breaches or leaked email traffic, looking for a plausible existing payment relationship (a real vendor, a real internal approval chain) to imitate. No technical detail on this stage was disclosed in Toyota Boshoku's case, so this is inferred from how BEC schemes of this kind are typically built, not confirmed fact of this specific incident.
Public corporate and staff information (subsidiary structure, finance-team roles on LinkedIn) is very hard to eliminate at enterprise scale; the realistic control assumes attackers can find it and hardens the payment-approval process it gets used against, rather than trying to hide it.
Attackers typically prepare the delivery mechanism, commonly a compromised or spoofed mailbox, or a look-alike domain resembling a real supplier or executive's address, so the fraudulent instruction arrives through a channel the finance team already trusts. Toyota Boshoku did not disclose whether a mailbox was hijacked or an identity was spoofed.
Harden email against account takeover with MFA and anti-phishing controls at the mail gateway, and configure automated flags for external-sender and lookalike-domain messages so a spoofed or hijacked source is more likely to be caught before it reaches finance staff.
The European subsidiary received what the company described as fraudulent payment directions from a malicious third party, consistent with a BEC message instructing finance staff to redirect an existing payment or change bank account details for a transaction that looked routine and authoritative.
Train finance and accounts-payable staff to treat any request to change existing bank or account details as inherently high-risk, regardless of how authoritative or routine the sender appears.
A staffer with payment authority accepted the instruction as genuine without an independent, out-of-band check against a previously known contact or number, the single point of failure common to nearly all successful BEC losses of this scale.
Require mandatory out-of-band verification, a callback to a pre-known, independently sourced number, for any new payee or any change to existing bank details, with no exception for apparent seniority or urgency.
The subsidiary transferred funds to a bank account controlled by the attackers, completing the fraud before the company recognized the directions were false. Toyota Boshoku announced a maximum expected loss of about 4 billion yen (~$37.5M) three weeks later and booked 3,393 million yen for the year ended 31 March 2020. It never disclosed how many transfers were involved or over what period.
Enforce segregation of duties and multi-person approval with escalating thresholds for large wires, so no single employee can both initiate and authorize a payment of this size.
Once received, BEC proceeds are typically moved rapidly through a chain of mule or intermediary accounts to frustrate freezing and recovery; Toyota Boshoku did not disclose how much, if any, of the transferred funds were ultimately recovered.
Pre-establish an incident playbook with immediate bank and law-enforcement notification (e.g. IC3 in the US, or the equivalent local authority) so a bank freeze can be requested within the narrow window before funds are laundered out of reach; this was reflected in Toyota Boshoku's actual response of promptly engaging legal counsel and local investigators.
Browse by what this case has in common with others in the library.
A phishing email tricked Unatrac's CFO into surrendering his Office365 credentials on a fake Microsoft login page; the attacker then…
Fraudsters posing as Tecnimont's group CEO, other executives, and a fictitious Swiss lawyer used spoofed emails and a staged series…
A 12-person ring watched hacked inboxes for big payments, then redirected them with fake emails. Trial evidence put losses above…
Target's 2013 breach began with malware emailed to a small HVAC contractor. 40M cards and 70M records exposed. What's known,…
Advance Machine Company's West Coast sales manager repeatedly rifled Tennant Company's sealed, covered dumpster in California to steal sales leads.
A small Columbus, Ohio public materials manufacturer disclosed in a February 2026 SEC 8-K that it lost $898,325 to an…
Impostors posing as Scoular's CEO and a senior figure at its audit firm convinced the controller a secret China acquisition…
Fraudsters swapped a former MP's number in his company's phone but kept his photo, then ordered Rs 7.68 crore in…
A fake email posing as DTC gave JE Cleantech false wire instructions for its 2026 dividend, diverting US$794,934 and delaying…
Target's 2013 breach began with malware emailed to a small HVAC contractor. 40M cards and 70M records exposed. What's known,…
A fraudster posing as AFGlobal's CEO, backed by a fake KPMG "attorney," pressured the accounting director into wiring $480,000 to…
Google found PROMPTFLUX, a dropper that asks Gemini for antivirus-evasion code mid-run. Its self-rewrite feature was switched off and it…
Attackers made Microsoft's own Azure Monitor send a fake $459.90 Windows Defender bill that passed SPF, DKIM and DMARC. A…
SCE reported $131,464 collected by scammers across its 2025 customer fraud complaints. Its warnings describe immediate-disconnection and meter-removal threats as…
A fraudster impersonating the company's chief executive tricked a Pivotal employee into emailing back affected employees' W-2 tax data.
Argan's Fiscal 2024 cybersecurity disclosure described fraudulently induced outbound wire transfers in March 2023 and reported $2.7 million of loss,…
Spoofed emails impersonating Medidata's president, backed by a fake "lawyer" caller, tricked finance staff into wiring $4.8M to an overseas…