Methods and apparatus to identify suspicious electronic communication based on communication history

1. An apparatus to process an electronic communication, the apparatus comprising:

an electronic communication receiver to receive the electronic communication from a first application;

a contact information controller to determine whether a sender of the electronic communication is stored within a contact datastore, the contact datastore including first known senders of communications corresponding to the first application and second known senders of communications corresponding to a second application;

a contact identifier to:

determine that a communication has not previously been sent from a recipient of the electronic communication to the sender of the electronic communication when the sender is not found in the contact datastore; and

after determining that the communication has not been previously sent, provide an alert message that the sender of the electronic communication is unknown; and

a user action determiner to, in response to a determination that a response to the electronic communication has been sent, store information corresponding to the sender of the electronic communication in the contact datastore.

2. The apparatus of claim 1 , further including a contact information initializer to:

obtain at least one of a communication history associated with an identified application on a user device or contacts associated with the identified application on the user device; and

store information associated with the at least one of the communication history or the contacts, wherein the at least one of the communication history or the contacts were utilized to send one or more communications from the user device.

3. The apparatus of claim 2 , wherein the identified application on the user device is the first application on the user device, and wherein the communication history is associated with at least the second application on the user device.

4. The apparatus of claim 1 , further including a new contact monitor to:

determine if a new contact is added to contacts associated with an application; and

after determining the new contact is added, store contact information associated with the new contact in the contact datastore.

5. The apparatus of claim 1 , further including a malicious content scanner to determine if the electronic communication includes a uniform resource locator (URL) or an attachment file.

6. The apparatus of claim 5 , further including the malicious content scanner to determine if the URL included in the electronic communication is malicious.

7. The apparatus of claim 5 , further including the malicious content scanner to determine if the attachment file included in the electronic communication is malicious.

8. At least one non-transitory computer readable storage medium comprising instructions that, when executed, cause at least one processor to at least:

receive an electronic communication from a first application;

determine whether a sender of the electronic communication is stored within a contact datastore, the contact datastore including first known senders of communications corresponding to the first application and second known senders of communications corresponding to a second application;

determine that a communication has not previously been sent from a recipient of the electronic communication to the sender of the electronic communication when the sender from the electronic communication is not found in the contact datastore;

after determining that the communication has not been previously sent, provide an alert message that the sender of the electronic communication is unknown; and

after determining that a response to the electronic communication has been sent, store information corresponding to the sender of the electronic communication in the contact datastore.

9. The at least one non-transitory computer readable storage medium of claim 8 , wherein the instructions, when executed, cause the at least one processor to:

obtain at least one of a communication history associated with an identified application on a user device or contacts associated with the identified application on the user device; and

store, in the contact datastore, information associated with the at least one of the communication history or the contacts, wherein the at least one of the communication history or the contacts were utilized to send one or more communications from the user device.

10. The at least one non-transitory computer readable storage medium of claim 9 , wherein the identified application on the user device is the first application on the user device, and wherein the communication history is associated with at least the second application on the user device.

11. The at least one non-transitory computer readable storage medium of claim 8 , wherein the contact datastore is accessible across a plurality of user devices.

12. The at least one non-transitory computer readable storage medium of claim 8 , wherein the instructions, when executed, cause the at least one processor to:

determine if a new contact is added to contacts associated with an application; and

after determining the new contact is added, store contact information associated with the new contact in the contact datastore.

13. The at least one non-transitory computer readable storage medium of claim 8 , wherein the instructions, when executed, cause the at least one processor to determine if the electronic communication includes a uniform resource locator (URL) or an attachment file.

14. The at least one non-transitory computer readable storage medium of claim 13 , wherein the instructions, when executed, cause the at least one processor to determine if the URL included in the electronic communication is malicious.

15. The at least one non-transitory computer readable storage medium of claim 13 , wherein the instructions, when executed, cause the at least one processor to determine if the attachment file included in the electronic communication is malicious.

16. A method to process an electronic communication, the method comprising:

receiving the electronic communication from a first application;

determining whether a sender of the electronic communication is stored within a contact datastore, the contact datastore including first known senders of communications corresponding to the first application and second known senders of communications corresponding to a second application;

determining that a communication has not previously been sent from a recipient of the electronic communication to the sender of the electronic communication when the sender from the electronic communication is not found in the contact datastore;

after determining that the communication has not been previously sent, providing an alert message that the sender of the electronic communication is unknown; and

after determining that a response to the electronic communication has been sent, storing information corresponding to the sender of the electronic communication in the contact datastore.

17. The method of claim 16 , further including:

obtaining at least one of a communication history associated with an identified application on a user device or contacts associated with the application on the user device; and

storing, in a datastore, information associated with the at least one of the communication history or the contacts, wherein the at least one of the communication history or the contacts were utilized to send one or more communications from the user device.

18. The method of claim 17 , wherein the identified application on the user device is the first application on the user device, and wherein the communication history is associated with at least the second application on the user device.

19. The method of claim 16 , wherein the contact datastore is accessible across a plurality of user devices.

20. The method of claim 16 , further including:

determining if a new contact is added to contacts associated with an application; and

after determining the new contact is added, storing contact information associated with the new contact in the contact datastore.