IP Library › Granted Patent US 9,473,528
Granted Patent B2
US 9,473,528 · App. 14/596,055 · Granted Oct 18, 2016

Identification of malware sites using unknown URL sites and newly registered DNS addresses

Inventors: Nir Zuk (Menlo Park, CA); Renzo Lazzarato (Pleasanton, CA); Huagang Xie (Pleasanton, CA)
Assignee: Palo Alto Networks, Inc.
H04L63/145G06F21/57H04L63/1408H04L63/168G06F2221/034G06F2221/2111
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 9,473,528
App. No.
14/596,055
Filed
Jan 13, 2015
Granted
Oct 18, 2016
Kind
B2
Art Unit
2431
USPC
726/23
Abstract

In some embodiments, identification of malware sites using unknown URL sites and newly registered DNS addresses includes performing a heuristic analysis for information associated with a network site; and assigning a score based on the heuristic analysis, in which the score indicates whether the network site is potentially malicious. In some embodiments, the system includes a security appliance that is in communication with the Internet. In some embodiments, the network site is associated with a network domain and/or a network uniform resource locator (URL). In some embodiments, performing a heuristic analysis for information associated with a network site further includes determining if a network site has recently been registered. In some embodiments, performing a heuristic analysis for information associated with a network site further includes determining if a network site is associated with recently changed DNS information. In some embodiments, performing a heuristic analysis for information associated with a network site further includes determining geographical information as well as an IP network location associated with the network site.

Claims (79)

1. A system, comprising:

a processor configured to:

perform a heuristic analysis for information associated with a network site, wherein performing the heuristic analysis for information associated with the network site further comprises:

determine whether the network site has recently been registered, wherein in the event that the network site has been recently registered, the network site has been registered within the last 9 months;

determine whether the network site has a change in domain name system (DNS) information, the change in DNS information including a change in domain name, a change in ownership of a network uniform resource locator (URL), a new IP address outside of the same subnet, or any combination thereof;

determine source information associated with the network site, wherein the source information includes geographical information associated with the network site and IP network related source information; and

generate a list of potentially malicious network sites based on whether the network site has recently been registered, whether the network site has a change in DNS information, and the source information associated with the network site; and

assign a score based on the heuristic analysis, wherein the score indicates whether the network site is potentially malicious, wherein the assigning of the score comprises to assign the score based on whether the network site has recently been registered, whether the network site has a change in DNS information, and the source information associated with the network site; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1 , wherein the system includes a security appliance that is in communication with the Internet, and wherein the network site is associated with a network domain and/or the URL.

3. The system recited in claim 1 , wherein the system includes a security cloud service that is in communication with the Internet, and wherein the network site is associated with a network domain and/or the URL.

4. The system recited in claim 1 , wherein assigning the score based on the heuristic analysis further comprises:

compare the score with a predefined threshold; and

in the event that the score exceeds the predefined threshold, determine that the network site is potentially malicious.

5. The system recited in claim 1 , wherein performing the heuristic analysis for information associated with the network site further comprises:

perform an analysis of links between pages of the same network site to measure navigability of the network site;

perform an analysis of links to and from other network sites to identify links to and from suspicious network sites;

perform an analysis of an amount of plain text, script, hypertext markup language (HTML) content, and/or uniform resource locator (URL) suitable for human navigation of the network site;

or perform any combination thereof.

6. The system recited in claim 1 , wherein performing the heuristic analysis for information associated with the network site further comprises:

in the event that the DNS information of the network site has changed, determine when the change in the DNS information occurred.

7. The system recited in claim 1 , wherein performing the heuristic analysis for information associated with the network site further comprises:

determine whether an IP address related to the network site is periodically unavailable based on DNS presence information.

8. The system recited in claim 1 , wherein determining source information associated with the network site further comprises:

determine the source information based on a regional Internet registry (RIR), a border gateway protocol (BGP) table, or any combination thereof.

9. The system recited in claim 1 , wherein the processor is further configured to:

generate a list of DNS changes for a plurality of network sites; and

store the list of DNS changes.

10. The system recited in claim 1 , wherein the score indicates that the network site is potentially malicious, wherein the system includes a security cloud service that is in communication with the Internet, wherein the network site is associated with a network domain and/or the URL, and wherein the processor is further configured to:

publish the network site to a security appliance for blocking access to/from the network site.

11. The system recited in claim 1 , wherein the score indicates that the network site is potentially malicious, wherein the system includes a security appliance that is in communication with the Internet, wherein the network site is associated with a network domain and/or the URL, and wherein the processor is further configured to:

block access to/from the network site.

12. The system recited in claim 1 , wherein the score indicates that the network site is potentially malicious, wherein the system includes a security appliance that is in communication with the Internet, wherein the network site is associated with a network domain and/or the URL, and wherein the processor is further configured to:

monitor access to/from the network site to determine whether the network site is a botnet site.

13. The system recited in claim 1 , wherein the score indicates that the network site is potentially malicious, wherein the system includes a security appliance that is in communication with the Internet, wherein the network site is associated with a network domain and/or the URL, and wherein the processor is further configured to:

apply a security policy based on the determination that the network site is potentially malicious; and

report that the network site is a potential malware site.

14. The system recited in claim 1 , wherein the score indicates that the network site is potentially malicious, wherein the system includes a security cloud service that is in communication with the Internet, wherein the network site is associated with a network domain and/or the URL, and wherein the processor is further configured to:

determine that the network site is a malware site if a virus sample attempts to connect to the network site.

15. The system recited in claim 1 , wherein the system includes a security cloud service that is in communication with the Internet, and wherein the processor is further configured to:

receive a plurality of network sites from one or more security appliances that are each associated with a subscription to the security cloud service, wherein the security cloud service performs the heuristic analysis for information associated with each of the network sites to identify which, if any, of the network sites is potentially malicious.

16. The system recited in claim 1 , wherein the system includes a security cloud service that is in communication with the Internet, and wherein the processor is further configured to:

receive a plurality of botnet reports; and

aggregate the plurality of botnet reports to correlate potentially suspicious botnet behavior to determine whether the network site is potentially malicious.

17. A method, comprising:

performing a heuristic analysis for information associated with a network site using a processor of a device in communication with a network, wherein performing the heuristic analysis for information associated with the network site further comprises:

determining whether the network site has recently been registered, wherein in the event that the network site has been recently registered, the network site has been registered within the last 9 months;

determining whether the network site has a change in domain name system (DNS) information, the change in DNS information including a change in domain name, a change in ownership of a network uniform resource locator (URL), a new IP address outside of the same subnet, or any combination thereof;

determining source information associated with the network site, wherein the source information includes geographical information associated with the network site and IP network related source information; and

generating a list of potentially malicious network sites based on whether the network site has recently been registered, whether the network site has a change in DNS information, and the source information associated with the network site; and

assigning a score based on the heuristic analysis, wherein the score indicates whether the network site is potentially malicious, wherein the assigning of the score comprises assigning the score based on whether the network site has recently been registered, whether the network site has a change in DNS information, and the source information associated with the network site.

18. The method recited in claim 17 , wherein assigning the score based on the heuristic analysis further comprises:

comparing the score with a predefined threshold; and

in the event that the score exceeds the predefined threshold, determining that the network site is potentially malicious.

19. The method recited in claim 17 , wherein performing the heuristic analysis for information associated with the network site further comprises:

performing an analysis of links between pages of the same network site to measure navigability of the network site;

performing an analysis of links to and from other network sites to identify links to and from suspicious network sites;

performing an analysis of an amount of plain text, script, hypertext markup language (HTML) content, and/or uniform resource locator (URL) suitable for human navigation of the network site;

or performing any combination thereof.

20. The method recited in claim 17 , wherein performing the heuristic analysis for information associated with the network site further comprises:

in the event that the DNS information of the network site has changed, determining when the change in the DNS information occurred.

21. The method recited in claim 17 , wherein performing the heuristic analysis for information associated with the network site further comprises:

determining whether an IP address related to the network site is periodically unavailable based on DNS presence information.

22. The method recited in claim 17 , wherein determining source information associated with the network site further comprises:

determining the source information based on a regional Internet registry (RIR), a border gateway protocol (BGP) table, or any combination thereof.

23. The method recited in claim 17 , further comprising:

generating a list of DNS changes for a plurality of network sites; and

storing the list of DNS changes.

24. The method recited in claim 17 , wherein the score indicates that the network site is potentially malicious, wherein the network site is associated with a network domain and/or the URL, and wherein the method further comprises:

publishing the network site to a security appliance for blocking access to/from the network site.

25. The method recited in claim 17 , wherein the score indicates that the network site is potentially malicious, wherein the network site is associated with a network domain and/or the URL, and wherein the method further comprises:

blocking access to/from the network site.

26. The method recited in claim 17 , wherein the score indicates that the network site is potentially malicious, wherein the network site is associated with a network domain and/or the URL, and wherein the method further comprises:

monitoring access to/from the network site to determine whether the network site is a botnet site.

27. The method recited in claim 17 , wherein the score indicates that the network site is potentially malicious, wherein the network site is associated with a network domain and/or the URL, and wherein the method further comprises:

applying a security policy based on the determination that the network site is potentially malicious; and

reporting that the network site is a potential malware site.

28. The method recited in claim 17 , wherein the score indicates that the network site is potentially malicious, wherein the network site is associated with a network domain and/or the URL, and wherein the method further comprises:

determining that the network site is a malware site if a virus sample attempts to connect to the network site.

Continuity (2)
Continuation 13115014 · May 24, 2011
Related Publication 20150195291A1 · Jul 9, 2015