Method and system for detecting two-factor authentication

1 . A method comprising:

identifying, by a web browser extension executing on a client device, an account associated with the client device, wherein the account is managed by an organization computing system;

detecting, by the web browser extension, that the client device visited a web page hosted by a third party web server;

injecting, by the web browser extension and after detecting that the client device visited the web page, code into a script of the web page to enable the web browser extension to monitor whether the client device is engaged in multi-factor authentication, wherein the injected code runs side-by-side with the code in the script of the web page;

monitoring, by the web browser extension and via the injected code, the web page to identify one or more components of the web page;

detecting, by the web browser extension, one or more identifiers, on the one or more components of the web page, associated with the multi-factor authentication;

based on the detecting, determining, by the web browser extension, that the client device does not have a multi-factor authentication functionality enabled with the third party web server; and

prompting, by the web browser extension and via an application programming interface, the organization computing system to update a fraud metric associated with the account based on the determination that the client device does not have the multi-factor authentication functionality enabled with the third party web server, wherein the update to the fraud metric includes increasing a sensitivity of a fraud algorithm configured to analyze one or more transactions between the account and the third party web server to detect potentially fraudulent activity.

2 . The method of claim 1 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining, by the web browser extension, that a type of website is a website associated with a financial institution; and

increasing, by the web browser extension, the sensitivity of the fraud algorithm associated with the account by a first amount.

3 . The method of claim 1 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining, by the web browser extension, that a type of website is a website not associated with a financial institution; and

prompting, by the web browser extension, the organization computing system to increase the sensitivity of the fraud algorithm with the account by a first amount that is less than an amount associated with a financial institution website.

4 . The method of claim 1 , further comprising:

receiving, at the web browser extension, a message from the organization computing system to be transmitted to the client device, the message comprising a suggestion to opt into the multi-factor authentication functionality; and

prompting, by the web browser extension, a user of the client device to opt into the multi-factor authentication functionality.

5 . The method of claim 4 , further comprising:

detecting, by the web browser extension, that the client device has opted into the multi-factor authentication functionality following receipt of the message; and

prompting, by the web browser extension, the organization computing system to further update the fraud metric associated with the account.

6 . The method of claim 5 , wherein, prompting, by the web browser extension, the organization computing system to further update the fraud metric associated with the account, comprises:

decreasing the sensitivity of the fraud algorithm associated with the account.

7 . The method of claim 1 , wherein determining, by the web browser extension, that the client device does not have the multi-factor authentication functionality enabled comprises:

analyzing the script of the web page for one or more fields associated with a multi-factor authentication protocol.

8 . One or more non-transitory computer readable media comprising one or more sequences of instructions, which, when executed by one or more processors, causes a computing system to perform operations, comprising:

identifying, by a web browser extension executing on a client device, an account associated with the client device;

detecting, by the web browser extension, that the client device visited a web page hosted by a third party web server;

injecting, by the web browser extension and after detecting that the client device visited the web page, code into a script of the web page to enable the web browser extension to monitor whether the client device is engaged in multi-factor authentication;

detecting, by the web browser extension and using the injected code, one or more components, of the web page, associated with the multi-factor authentication;

based on the detecting, determining, by the web browser extension, that the client device does not have a multi-factor authentication functionality enabled with the third party web server; and

prompting, by the web browser extension and via an application programming interface, an organization computing system to update a fraud metric associated with the account based on the determination that the client device does not have the multi-factor authentication functionality enabled with the third party web server, wherein the update to the fraud metric includes increasing a sensitivity of a fraud algorithm associated with the account.

9 . The one or more non-transitory computer readable media of claim 8 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining that a type of website is a website associated with a social media institution; and

increasing the sensitivity of the fraud algorithm associated with the account by a first amount.

10 . The one or more non-transitory computer readable media of claim 8 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining that a type of website is a website not associated with a social media institution; and

increasing the sensitivity of the fraud algorithm with the account by a first amount that is less than an amount associated with a financial institution website.

11 . The one or more non-transitory computer readable media of claim 8 , further comprising:

receiving, at the web browser extension, a message from the organization computing system to be transmitted to the client device, the message comprising a suggestion to opt into the multi-factor authentication functionality; and

prompting, by the web browser extension, a user of the client device to opt into the multi-factor authentication functionality.

12 . The one or more non-transitory computer readable media of claim 11 , further comprising:

detecting, by the web browser extension, that the client device has opted into the multi-factor authentication functionality following receipt of the message; and

prompting, by the web browser extension, the organization computing system to further update the fraud metric associated with the account.

13 . The one or more non-transitory computer readable media of claim 12 , wherein prompting, by the web browser extension, the organization computing system to further update the fraud metric associated with the account, comprises:

decreasing the sensitivity of the fraud algorithm associated with the account.

14 . The one or more non-transitory computer readable media of claim 8 , wherein determining, by the web browser extension, that the client device does not have the multi-factor authentication functionality enabled comprises:

analyzing a document object model of the web page to identify one or more fields associated with a multi-factor authentication protocol.

15 . A system, comprising:

a processor; and

a memory having programming instructions stored thereon, which, when executed by the processor, causes the system to perform operations comprising:

identifying, by a web browser extension executing on a client device, an account associated with the client device;

detecting, by the web browser extension, that the client device visited a web page;

injecting, by the web browser extension, code into a script of the web page to enable the web browser extension to monitor whether the client device is engaged in multi-factor authentication;

detecting, by the web browser extension, one or more identifiers, on the web page, associated with the multi-factor authentication;

based on the detecting, determining, by the web browser extension, that the client device does not have a multi-factor authentication functionality enabled; and

prompting, by the web browser extension and via an application programming interface, an organization computing system to update a fraud metric associated with the account based on the determination that the client device does not have the multi-factor authentication functionality enabled, wherein the update to the fraud metric includes increasing a sensitivity of a fraud algorithm associated with the account.

16 . The system of claim 15 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining that a type of website is a website associated with an email service institution; and

increasing the sensitivity of the fraud algorithm associated with the account by a first amount.

17 . The system of claim 15 , wherein increasing the sensitivity of the fraud algorithm associated with the account, comprises:

determining that a type of website is a website not associated with an email service institution; and

increasing the sensitivity of the fraud algorithm with the account by a first amount that is less than an amount associated with a financial institution website.

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

receiving, by the web browser extension, a notification from the organization computing system, the notification including a recommendation for the client device to enable the multi-factor authentication functionality; and

displaying, by the web browser extension, the recommendation to the client device via a user interface of the client device.

19 . The system of claim 18 , wherein the operations further comprise:

detecting, by the web browser extension, that the client device has enabled the multi-factor authentication functionality in response to the displayed recommendation; and

transmitting, by the web browser extension to the organization computing system, an indication that the client device has enabled the multi-factor authentication functionality.

20 . The system of claim 15 , wherein determining, by the web browser extension, that the client device does not have the multi-factor authentication functionality enabled comprises:

parsing a document object model of the web page to identify one or more elements associated with a multi-factor authentication process.