DYNAMIC PHISHING PROTECTION IN INSTANT MESSAGING

• US 20090006532A1
• Filed: 06/28/2007
• Published: 01/01/2009
• Est. Priority Date: 06/28/2007
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Sinn, Richard, Libbey, Miles, Jiang, Linlong
• Application Number:
  US11/770,490
• Publication Number:
  US 20090006532A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/1483 service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

Method, apparatus, and systems are directed to phishing detection and prevention in Instant Messaging (IM) environments. A variety of sources provide phishing data to a client phishing engine (CAE). The CAE may receive data from various applications local to the client device, from sources external to the client device, user input, and data from a plurality of other client devices. The CAE may employ the data to block access to a site and/or provide a warning message. At least some of the phishing data is provided to a centralized anti-phishing server (CAS) from a plurality of client devices. The CAS then attempts to use the received phishing data to search for the originator of the phishing site, and prevent future messages associated with the site. CAS will provide information about the detected phishing sites to a filtering application, such that the phishing site may be appropriately blocked.

Claims

1. A client device for detecting phishing over a network, comprising:

a transceiver for receiving and sending information over the network;

a processor in communication with the display and the transceiver; and

a memory in communication with the processor and for use in storing data and machine instructions that causes the processor to perform a plurality of actions, including;

receiving weighted phishing data collected from a plurality of other client devices;

receiving a text message having a link to a webpage;

employing the weighted phishing data to determine whether the link is suspected or known as a phishing link;

if the link is determined to be a suspected phishing link, displaying a warning message to a user of the client device indicating that the link is suspect; and

if the link is determined to be a known phishing link, blocking access to the link by the user.

2. The client device of claim 1, wherein the plurality of actions further comprising:

collecting phishing data from at least one application or operating system component within the client device; and

sending the collected phishing data to a centralized anti-phishing service, wherein the centralized anti-phishing service is configured to perform actions, including;

receiving phishing data from the plurality of other client devices;

weighting the received phishing data from the client device and the plurality of other client devices based in part on a number of other client devices providing phishing data associated with a similar link; and

sending the weighted phishing data to the client device.

3. The client device of claim 2, wherein the centralized anti-phishing service performs actions, further comprising:

determining if the weighted phishing data indicates a link to be to a known phishing site based on a number of different client devices reporting the link exceeding a defined number; and

if the link is determined to be to a known phishing site, employing the received phishing data to locate a source of the phishing site.

4. The client device of claim 2, wherein the centralized anti-phishing service is configured to perform actions, further comprising:

employing the received phishing data to locate a source of a known phishing site and to perform actions directed to inhibiting additional phishing activity from the phishing site.

5. The client device of claim 1, wherein determining whether the link is suspect or known further comprises:

if a number of different client devices reporting the link is below a defined number, but greater than zero, indicating the link to be a suspected phishing link; and

if the number of different client devices reporting the link is at or above the defined number, indicating the link to be a known phishing link.

6. A processor readable storage medium having computer-executable instructions, wherein the execution of the computer-executable instructions provides for managing a phishing attack by enabling actions, including:

receiving from a plurality of client devices, phishing data associated with a possible phishing site;

weighting the received phishing data based, in part, on a number of different client devices reporting the possible phishing site, wherein the weighting is arranged to classify the possible phishing site into one of a suspected phishing site or a known phishing site; and

providing the weighting to at least one client device within the plurality of client devices, wherein the at least one client device is configured to perform actions, including employing the weighted phishing data to determine whether to display a warning message or block access to the phishing site identified by a link within a received text message.

7. The processor readable storage medium of claim 6, wherein the phishing data further comprises at least one of a network address to the phishing site, a time when each reporting client device detected the phishing site, a network address of each reporting client device, a client application identifier associated with detecting the phishing site, a geographic location of the client device reporting the detected phishing site, a frequency of times the reporting client device detected the phishing site, or a communication mechanism in which a link to the phishing site was received by the reporting client device.

8. The processor readable storage medium of claim 6, wherein the computer-executable instructions enable actions, further comprising:

if the phishing site is determined to be a known phishing site, performing actions, including;

modifying a blocking filter to block text messages to the plurality of client devices that include a link to the known phishing site;

employing the received phishing data to identify at least one of a domain registrar or host server associated with the known phishing site; and

performing at least one action directed to inhibiting a future phishing activity to be performed by the known phishing site.

9. The processor readable storage medium of claim 6, wherein classifying the possible phishing site as a suspected phishing site further comprises classifying the site based on a small population size of different client devices.

10. The processor readable storage medium of claim 6, wherein classifying the phishing data is performed based on a number of different client devices reporting the phishing site being

11. The processor readable storage medium of claim 6, wherein the computer-executable instructions enable actions, further comprising:

providing the received phishing data from the plurality of client devices to at least one other service configured to perform blocking of phishing sites.

12. A network device for detecting a phishing attack, comprising:

a transceiver to send and receive data over a network; and

a processor that is operative to perform actions, including;

receiving from a plurality of client devices, phishing data associated with a possible phishing site, wherein the received phishing data is based on at least one of a user detected phishing site or detection based on a client application or client operating system;

classifying the possible phishing site based, in part, on a defined relatively small number of different client devices reporting the possible phishing site, wherein the possible phishing site is classified as one of a suspected phishing site or a known phishing site;

providing the classification to at least one client device within the plurality of client devices, for use in determining whether to display a warning message or block access to the phishing site identified by a link within a client received text message; and

if the phishing site is classified as a known phishing site, performing at least one action directed to inhibiting a future phishing activity from the known phishing site.

13. The network device of claim 12, wherein the defined relatively small number of different client devices is a number less than about twenty-five.

14. The network device of claim 12, wherein the phishing data further comprises at least one of a network address to the phishing site, a time when each reporting client device detected the phishing site, a network address of each reporting client device, a client application identifier associated with detecting the phishing site, a geographic location of the client device reporting the detected phishing site, a frequency of times the reporting client device detected the phishing site, or a communication mechanism in which a link to the phishing site was received by the reporting client device.

15. The network device of claim 12, wherein the processor is operative to perform actions, further including:

if the possible phishing site is classified as a known phishing site, employing a filter to block or modify a text message that includes a link to the known phishing site.

16. The network device of claim 12, wherein at least one client device is configured to receive additional phishing information from at least one other source, including, a third party content data source.

17. A method of managing a phishing attack over a network, comprising:

receiving, from a plurality of client devices, phishing data associated with a plurality of possible phishing sites, wherein the received phishing data is based on at least one of a user detected phishing site or detection based on a client application or client operating system;

classifying the phishing sites based, in part, on a defined number of different client devices reporting the possible phishing sites, wherein the possible phishing sites are classified as one of a suspected phishing site or a known phishing site;

providing the classifications to at least one client device within the plurality of client devices, for use in determining a response to a text message received by the at least one client device having a link to a webpage; and

if a possible phishing site is classified as a known phishing site, performing at least one action directed to inhibiting a future phishing activity from the known phishing site.

18. The method of claim 17, wherein the at least one client device is configured to receive phishing data from at least one other non-client device source.

19. The method of claim 17, wherein phishing data includes information identifying a source of the phishing sites, a network address for the reporting client device, or a time of the detection.

20. A modulated data signal configured to include program instructions for performing the method of claim 17.