IP Library Granted Patent US 12,430,617
Granted Patent B2
US 12,430,617 · App. 18/395,400 · Granted Sep 30, 2025

Business email compromise detection system

Inventors: Umalatha Batchu (Cupertino, CA); Torsten Zeppenfeld (Emerald Hills, CA); Blake Darche (Finksburg, MD); Philip Syme (Ellicott City, MD)
Assignee: CLOUDFLARE, INC.
G06Q10/107G06F40/205G06N7/01G06Q30/018G06Q40/02H04L63/1416H04L63/1425
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,430,617
App. No.
18/395,400
Granted
Sep 30, 2025
Kind
B2
Abstract

An email is received that is from an email sender. From the email, the display name of the email sender, an email address of the email sender, and an email domain of the email sender, is extracted. A score is determined for the email based on at least: the extracted display name of the email sender, the extracted email address of the email sender, and the extracted email domain of the email sender, where the score indicates a probability that the email is from a legitimate sender. Message content of the email is input into multiple classifiers each corresponding to a particular message type. The message type of the email is determined based on output of the classifiers. Based on at least the determined score for the email and the determined message type of the email, a determination is made whether the email is associated with a BEC attack.

Claims (59)

1. A method, comprising:

receiving an email that is directed to an email recipient and is from an email sender;

extracting, from the email, a triple, the extracted triple including a display name of the email sender, an email address of the email sender, and an email domain of the email sender;

identifying a triple identifier associated with the extracted triple;

determining a name score for the email based on the triple identifier by accessing the name score for the triple identifier in a database, wherein the name score indicates a probability that the email is from a legitimate sender, and wherein the name score is updated based on frequency counting;

inputting message content of the email into a plurality of classifiers, wherein each of the plurality of classifiers is machine-learned to recognize a particular message type;

determining a message type of the email based on output of the plurality of classifiers; and

determining, based on at least the determined name score for the email, the determined message type of the email, and a reputation score associated with an IP address of the email sender, whether the email is associated with a business email compromise (BEC) attack.

2. The method of claim 1 , further comprising:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

modifying the email to include a status indicating that the email is associated with a BEC attack.

3. The method of claim 1 , further comprising:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is not associated with the BEC attack; and

modifying the email to include a status indicating that the email is not associated with a BEC attack.

4. The method of claim 1 , further comprising:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

blocking transmission of the email to the email recipient.

5. The method of claim 1 , wherein the message type of the email is one of: an invoice, a financial communication, a communication related to a banking account, and an automated clearinghouse (ACH) communication.

6. The method of claim 1 , wherein determining whether the email is associated with a BEC attack further is based on a reputation score associated with the email domain of the email sender.

7. A non-transitory computer-readable storage media comprising instructions which, when executed by one or more processors cause operations to be performed comprising:

receiving an email that is directed to an email recipient and is from an email sender;

extracting, from the email, a triple, the extracted triple including a display name of the email sender, an email address of the email sender, and an email domain of the email sender;

identifying a triple identifier associated with the extracted triple;

determining a name score for the email based on the triple identifier by accessing the name score for the triple identifier in a database, wherein the name score indicates a probability that the email is from a legitimate sender, and wherein the name score is updated based on frequency counting;

inputting message content of the email into a plurality of classifiers, wherein each of the plurality of classifiers is machine-learned to recognize a particular message type;

determining a message type of the email based on output of the plurality of classifiers; and

determining, based on at least the determined name score for the email, the determined message type of the email, and a reputation score associated with an IP address of the email sender, whether the email is associated with a business email compromise (BEC) attack.

8. The non-transitory computer-readable storage media of claim 7 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

modifying the email to include a status indicating that the email is associated with a BEC attack.

9. The non-transitory computer-readable storage media of claim 7 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is not associated with the BEC attack; and

modifying the email to include a status indicating that the email is not associated with a BEC attack.

10. The non-transitory computer-readable storage media of claim 7 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

blocking transmission of the email to the email recipient.

11. The non-transitory computer-readable storage media of claim 7 , wherein the message type of the email is one of: an invoice, a financial communication, a communication related to a banking account, and an automated clearinghouse (ACH) communication.

12. The non-transitory computer-readable storage media of claim 7 , wherein determining whether the email is associated with a BEC attack further is based on a reputation score associated with the email domain of the email sender.

13. A system comprising:

one or more processors; and

one or more non-transitory storage media storing instructions which, when executed by the one or more processors cause the system to perform operations including:

receiving an email that is directed to an email recipient and is from an email sender;

extracting, from the email, a triple, the extracted triple including a display name of the email sender, an email address of the email sender, and an email domain of the email sender;

identifying a triple identifier associated with the extracted triple;

determining a name score for the email based on the triple identifier by accessing the name score for the triple identifier in a database, wherein the name score indicates a probability that the email is from a legitimate sender, and wherein the name score is updated based on frequency counting;

inputting message content of the email into a plurality of classifiers, wherein each of the plurality of classifiers is machine-learned to recognize a particular message type;

determining a message type of the email based on output of the plurality of classifiers; and

determining, based on at least the determined name score for the email, the determined message type of the email, and a reputation score associated with an IP address of the email sender, whether the email is associated with a business email compromise (BEC) attack.

14. The system of claim 13 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

modifying the email to include a status indicating that the email is associated with a BEC attack.

15. The system of claim 13 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is not associated with the BEC attack; and

modifying the email to include a status indicating that the email is not associated with a BEC attack.

16. The system of claim 13 , wherein the operations further comprise:

wherein a result of the determining whether the email is associated with the BEC attack indicates that the email is associated with the BEC attack; and

blocking transmission of the email to the email recipient.

17. The system of claim 13 , wherein the message type of the email is one of: an invoice, a financial communication, a communication related to a banking account, and an automated clearinghouse (ACH) communication.

18. The system of claim 13 , wherein determining whether the email is associated with a BEC attack further is based on a reputation score associated with the email domain of the email sender.

Assignments (1)
SECURITY INTEREST Recorded May 20, 2024
From: CLOUDFLARE, INC.
To: CITIBANK, N.A.
Reel/Frame 067472/0246 →
Continuity (2)
Continuation 17150853 · Jan 15, 2021
Related Publication 20240144190A1 · May 2, 2024
References Cited (35)
US 9912677B2 · Chien · 2018 [cited by applicant]
US 10050998B1 · Singh · 2018 [cited by applicant]
US 10135766B2 · Ciancio-Bunch · 2018 [cited by applicant]
US 10277628B1 · Jakobsson · 2019 [cited by applicant]
US 10515214B1 · Vincent et al. · 2019 [cited by applicant]
US 10666676B1 · Hsu · 2020 [cited by examiner]
US 10834127B1 · Yeh · 2020 [cited by examiner]
US 10887330B2 · Christian · 2021 [cited by examiner]
US 10972484B1 · Swackhamer · 2021 [cited by applicant]
US 11049402B2 · Mondello et al. · 2021 [cited by applicant]
US 11050698B1 · Batchu et al. · 2021 [cited by applicant]
US 11102244B1 · Jakobsson · 2021 [cited by examiner]
US 11138565B2 · Nakamura · 2021 [cited by examiner]
US 11388188B2 · Ahluwalia · 2022 [cited by applicant]
US 11595435B2 · Singh · 2023 [cited by examiner]
US 11601440B2 · Pearce · 2023 [cited by examiner]
US 11647034B2 · Levin et al. · 2023 [cited by applicant]
US 20080134333A1 · Shipp · 2008 [cited by examiner]
US 20140052626A1 · Mitchell · 2014 [cited by examiner]
US 20160203531A1 · Teshima · 2016 [cited by examiner]
US 20180114277A1 · Whitmer · 2018 [cited by examiner]
US 20180278627A1 · Goutal · 2018 [cited by examiner]
US 20190349400A1 · Bruss · 2019 [cited by examiner]
US 20200014711A1 · Rego et al. · 2020 [cited by applicant]
US 20200036751A1 · Kohavi · 2020 [cited by examiner]
US 20200067861A1 · Leddy · 2020 [cited by examiner]
US 20200134566A1 · Benkreira · 2020 [cited by examiner]
US 20200351301A1 · Schweighauser · 2020 [cited by examiner]
US 20200366712A1 · Onut et al. · 2020 [cited by applicant]
US 20200396258A1 · Jeyakumar et al. · 2020 [cited by applicant]
US 20210058395A1 · Jakobsson · 2021 [cited by examiner]
US 20210281606A1 · Singh et al. · 2021 [cited by applicant]
US 20210295179A1 · Eyal et al. · 2021 [cited by applicant]
US 20220182345A1 · Birch · 2022 [cited by examiner]
Notice of Allowance, U.S. Appl. No. 17/150,853, filed Aug. 25, 2023, 18 pages. [cited by applicant]