	US 12,088,572 B2
	Email verification using injected tokens for message authentication
George Albero, Charlotte, NC (US); Maharaj Mukherjee, Poughkeepsie, NY (US); and Benjamin D. Moores, Ventura, CA (US)
Assigned to Bank of America Corporation, Charlotte, NC (US)
Filed by Bank of America Corporation, Charlotte, NC (US)
Filed on Sep. 22, 2021, as Appl. No. 17/481,674.
Prior Publication US 2023/0086249 A1, Mar. 23, 2023
Int. Cl. H04L 9/40 (2022.01); G06F 40/40 (2020.01); H04L 51/224 (2022.01)

CPC H04L 63/08 (2013.01) [G06F 40/40 (2020.01); H04L 51/224 (2022.05); H04L 63/126 (2013.01)]

17 Claims

1. A computing platform comprising:

at least one processor;

a communication interface communicatively coupled to the at least one processor; and

memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

receive a message from an electronic messaging server, wherein the message is sent by a first device and directed to a second device;

generate a message encryption score for the message, wherein generating the message encryption score for the message comprises applying the following model:

the message encryption score (d)=a+b+c; and

if d is greater than or equal to 0.6, generate authentication token, wherein:

if number of matching keywords exceeds 3, a=0.3; if the number of matching keywords exceeds 1 but not 3, a=0.15, otherwise a=0,

if message recipient matches, b=1, otherwise b=0, and

if message context matches, b=0.5;

compare the message encryption score to a message encryption threshold; based on identifying that the message encryption score exceeds the message encryption threshold, identify that an authentication token should be injected into the message, wherein identifying that the authentication token should be injected into the message comprises identifying that a number of hops involved in a transmission path of the message exceeds a predetermined number of hops;

verify, based on message sender details, an identity of a sender of the message;

generate, after verifying the identity of the sender of the message, the authentication token for the message;

inject the authentication token into the message;

route, to the electronic messaging server and after injecting the authentication token into the message, the message;

receive, from the second device, a request to validate the message, wherein the request includes the authentication token and details of the message;

identify, using the authentication token and the details of the message, that the message is authenticated; and

send, to the second device, a message authentication notification and one or more commands directing the second device to display the message authentication notification along with the message, wherein sending the one or more commands directing the second device to display the message authentication notification along with the message causes the second device to display the message authentication notification along with the message.