Close
Updated:

What Is Business Email Compromise?

Business Email Compromise (BEC) is a sophisticated cybercrime that targets businesses and individuals performing legitimate transfer-of-funds requests. Attackers employ tactics such as email spoofing, phishing, and social engineering to impersonate trusted entities—like executives, vendors, or legal representatives—to deceive victims into transferring money or sensitive information.

Common BEC Techniques

  • Email Spoofing: Crafting emails that appear to originate from trusted sources
  • Account Compromise: Gaining unauthorized access to legitimate email accounts to send fraudulent messages
  • Social Engineering: Manipulating individuals into divulging confidential information or performing actions that compromise security
  • Malware Deployment: Using malicious software to infiltrate networks and monitor communications

Impact

According to the FBI, between October 2013 and December 2023, BEC scams have resulted in over $55 billion in reported losses globally, with more than $20 billion attributed to victims in the United States alone.

State and Federal Legal Actions

1. U.S. v. Erick Jason Victoria-Brito (Southern District of New York, 2025)

In January 2025, Erick Jason Victoria-Brito was extradited from the Dominican Republic to face charges related to a $60 million BEC scheme. The operation targeted entities including a professional sports team, a healthcare company, and a nonprofit organization. The conspirators created thousands of fake businesses and bank accounts to deceive victims into transferring funds, which were then laundered through international banks.

2. U.S. v. Animashaun Adebo, et al. (Eastern District of New York, 2024)

In June 2024, four individuals were charged for their roles in BEC and related romance scams that led to over $50 million in losses. The defendants allegedly used compromised email accounts and fraudulent representations to misappropriate funds, which were laundered through shell companies and unsuspecting intermediaries.

3. Studco Building Systems US, LLC v. 1st Advantage Federal Credit Union (Eastern District of Virginia, 2023)

In a landmark civil case, a Virginia federal court held that 1st Advantage Federal Credit Union was liable under the Uniform Commercial Code Article 4A for failing to act on alerts about discrepancies in wire transfers resulting from a BEC incident. The court awarded Studco damages for the full amount of the diverted funds, setting a precedent for financial institutions’ responsibilities in monitoring and responding to potential fraud.

4. Asset Forfeiture Actions in Connecticut (2024)

The U.S. Attorney’s Office in Connecticut successfully recovered approximately $2.28 million through civil asset forfeiture actions related to two separate BEC scams. In these cases, perpetrators impersonated legitimate parties in financial transactions, redirecting funds to their own accounts. The swift reporting by victims enabled law enforcement to trace and seize the stolen assets.

5. Seizure of $3.5 Million in BEC Scam (District of Connecticut, 2024)

In November 2024, authorities seized approximately $3.5 million linked to a BEC scam where attackers impersonated a party in a legitimate transaction, altering payment details to divert funds. The victim’s prompt reporting facilitated the tracing and freezing of the fraudulent accounts.

Legal/Financial Implications

These cases underscore the evolving legal landscape surrounding BEC incidents. Courts are increasingly holding financial institutions accountable for failing to detect and prevent fraudulent transactions, especially when internal alerts are ignored. Moreover, the successful recovery of funds through asset forfeiture demonstrates law enforcement’s commitment to combating cyber-enabled financial crimes.


BEC Prevention Strategies

1. Email Security Controls

  • Implement SPF, DKIM, and DMARC to prevent domain spoofing
  • Use email authentication and encryption services (e.g., Microsoft Defender, Mimecast)
  • Flag external emails with a banner (“This email is from outside your organization”)

2. Employee Training

  • Regularly train staff on phishing awareness
  • Conduct simulated phishing attacks
  • Encourage verbal verification for sensitive or unusual financial requests (i.e., “call before you wire” policy)

3. Multi-Factor Authentication (MFA)

  • Especially critical for email accounts and financial systems
  • Prevents access even if credentials are compromised

4. Segregation of Duties

  • Require multiple approvals for fund transfers
  • Limit who can initiate, approve, or confirm payments

5. Behavioral Analytics & AI Tools

  • Use AI-driven software to monitor for anomalies in email usage or financial activity (e.g., Abnormal Security, Darktrace)

Legal Recourse if You’re a Victim

1. Report Immediately

  • Local Law Enforcement: File a police report
  • FBI’s Internet Crime Complaint Center (IC3)
    • Include all details: emails, wire transfer information, IP addresses
    • See www.ic3.gov
  • Bank Notification: Immediately contact your financial institution to initiate a SWIFT recall or Fraudulent Wire Recall
  • Cyberinsurance Carrier: Immediately contact your cyberinsurance carrier to determine coverage

2. Consider a Lawsuit

  • Against your bank (if it failed to follow reasonable commercial standards under UCC Article 4A)
  • Against the receiving bank or intermediary institutions if they failed to perform Know Your Customer (KYC) due diligence
  • Against third parties (e.g., hackers, mules, vendors who had security lapses)

Legal claims may include:

  • Negligence
  • Breach of contract
  • Fraud, deceit, misrepresentation
  • Conversion (unlawful taking of funds)

Case Example: Studco v. 1st Advantage Federal Credit Union

  • Studco sued after a $600,000 wire was fraudulently diverted to third parties
  • The court found the credit union liable for ignoring system flags about inconsistencies in account ownership
  • This case sets a legal precedent for financial institutions’ responsibility to act on red flags

Case Analysis Tips

What to Look For:

  • Was a legitimate email account compromised?
  • Were fraudulent emails well-written or riddled with errors?
  • Was any internal protocol bypassed (e.g., no verbal confirmation)?
  • Did the bank or counterparty fail to catch red flags (e.g., new payee account with mismatched names)?

Common Red Flags:

  • Changes to bank account details mid-transaction
  • High-pressure or urgent payment requests
  • Slight alterations in email addresses (e.g., john.doe@yourc0mpany.com instead of john.doe@yourcompany.com)
Contact Us