# US 2004/0083408 A1 · Heuristic detection and termination of fast spreading network worm attacks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0083408 A1
- Document ID: US20040083408A1
- Status: Published application
- Kind: A1
- Application number: 10/280,586
- Filed: 2002-10-24
- Published: 2004-04-29
- Earliest claimed: 2002-10-24
- Assignees: Symantec Corporation
- Inventors: Mark Spiegel; Bruce McCorkendale; William Sobel
- Web page: https://patentgrep.com/patent/US20040083408A1

## CPC

- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, apparati, and computer program products for detecting and responding to fast-spreading network worm attacks include a network monitoring module (110), which observes (205) failed network connection attempts from multiple sources. A logging module (120) logs (220) the failed connection attempts. An analysis module (150) uses the logged data on the failed connection attempts to determine (225) whether a sources is infected with a worm using a set of threshold criteria. The threshold criteria indicate whether a source's failed connection attempts are non-normal. In one embodiment, a response module (160) responds (240) to the computer worm by, e.g., alerting a user or system administrator, terminating an infected process (20), or terminating the infected source's network access.

## Claims

### Claim 1

A computer-implemented method for detecting a worm infection on a set of sources coupled to a network, the method comprising the steps of:
observing a plurality of failed network connection attempts, each failed network connection attempt originating from one of the sources and directed to a destination network address; and
responsive to a source's failed network connection attempts during a period of time meeting at least one of a set of threshold criteria, declaring a presence of a worm.

### Claim 2 (depends on 1)

The method of claim 1, wherein at least one source is a process running on a network device.

### Claim 3 (depends on 2)

The method of claim 2, further comprising the step of:
responsive to a declaration of a worm, terminating the process associated with the declared worm.

### Claim 4 (depends on 1)

The method of claim 1, wherein at least one source is a network device coupled to a network.

### Claim 5 (depends on 4)

The method of claim 4, further comprising the step of:
responsive to a declaration of a worm, terminating network access of the network device associated with the declared worm.

### Claim 6 (depends on 1)

The method of claim 1, further comprising the step of:
responsive to a declaration of a worm, alerting a user.

### Claim 7 (depends on 1)

The method of claim 1, further comprising the step of:
responsive to a declaration of a worm, alerting a system administrator.

### Claim 8 (depends on 1)

The method of claim 1, wherein the threshold criteria comprise:
a number of failed network connection attempts; and
a diversity of destination network addresses associated with the failed network connection attempts.

### Claim 9 (depends on 1)

The method of claim 1, wherein the threshold criteria comprise a correlation with a prior DNS lookup having not been performed before an associated failed network connection attempt.

### Claim 10 (depends on 1)

The method of claim 1, wherein the threshold criteria comprise a weighting associated with at least one of the failed network connection attempts according to an attribute thereof.

### Claim 11 (depends on 1)

The method of claim 1, wherein a threshold criterion applied to a source depends on the source, and different threshold criteria are used for different sources.

### Claim 12 (depends on 1)

The method of claim 1, wherein the step of declaring a worm comprises excluding a source from the threshold criteria, whereby the source's failed network connection attempts do not cause a presence of a worm to be declared.

### Claim 13

A computer-implemented method for detecting a worm on a network device, the method comprising the steps of:
monitoring attempts to connect to a destination network address by any of a set of processes running on the network device;
logging the process and the destination network address associated with a set of failed connection attempts; and
responsive to the failed connection attempts associated with a process being determined non-normal, declaring a presence of a worm.

### Claim 14 (depends on 13)

The method of claim 13, further comprising the step of:
responsive to a declaration of a worm, terminating the process associated with the non-normal failed connection attempts.

### Claim 15 (depends on 13)

The method of claim 13, further comprising the step of:
responsive to a declaration of a worm, terminating network access of the network device.

### Claim 16 (depends on 13)

The method of claim 13, wherein the determination of non-normalcy is based at least in part on:
a number of failed network connection attempts; and
a diversity of destination network addresses associated with the failed network connection attempts.

### Claim 17 (depends on 13)

The method of claim 13, wherein the determination of non-normalcy is based at least in part on a correlation with a prior DNS lookup having not been performed before an associated failed network connection attempt.

### Claim 18

A computer-implemented method for detecting a worm on a network, the method comprising the steps of:
monitoring attempts to connect to a destination network address by any of a set of network devices coupled to the network;
logging the network device and the destination network address associated with a set of failed connection attempts; and
responsive to the failed connection attempts associated with a network device being determined non-normal, declaring a presence of a worm.

### Claim 19 (depends on 18)

The method of claim 18, further comprising the step of:
responsive to a declaration of a worm, terminating network access of the network device.

### Claim 20 (depends on 18)

The method of claim 18, wherein the determination of non-normalcy is based at least in part on:
a number of failed network connection attempts; and
a diversity of destination network addresses associated with the failed network connection attempts.

### Claim 21 (depends on 18)

The method of claim 18, wherein the determination of non-normalcy is based at least in part on a correlation with a prior DNS lookup having not been performed before an associated failed network connection attempt.

### Claim 22

A computer program product comprising a computer-readable medium containing computer program code for detecting a worm infection on a set of sources coupled to a network, the computer program code comprising instructions for performing the steps of:
observing a plurality of failed network connection attempts, each failed network connection attempt originating from one of the sources and directed to a destination network address; and
responsive to a source's failed network connection attempts during a period of time meeting at least one of a set of threshold criteria, declaring a presence of a worm.

### Claim 23 (depends on 22)

The computer program product of claim 22, wherein at least one source is a process running on a network device.

### Claim 24 (depends on 23)

The computer program product of claim 23, the instructions for further performing the step of:
responsive to a declaration of a worm, terminating the process associated with the declared worm.

### Claim 25 (depends on 22)

The computer program product of claim 22, wherein at least one source is a network device coupled to a network.

### Claim 26 (depends on 25)

The computer program product of claim 25, the instructions for further performing the step of:
responsive to a declaration of a worm, terminating network access of the network device associated with the declared worm.

### Claim 27 (depends on 22)

The computer program product of claim 22, wherein the threshold criteria comprise:
a number of failed network connection attempts; and
a diversity of destination network addresses associated with the failed network connection attempts.

### Claim 28 (depends on 22)

The computer program product of claim 22, wherein the threshold criteria comprise a correlation with a prior DNS lookup having not been performed before an associated failed network connection attempt.

### Claim 29

A computer program product comprising a computer-readable medium containing computer program code for detecting a worm on a network device, the computer program code comprising instructions for performing the steps of:
monitoring attempts to connect to a destination network address by any of a set of processes running on the network device;
logging the process and the destination network address associated with a set of failed connection attempts; and
responsive to the failed connection attempts associated with a process being determined non-normal, declaring a presence of a worm.

### Claim 30

A computer program product comprising a computer-readable medium containing computer program code for detecting a worm on a network, the computer program code comprising instructions for performing the steps of:
monitoring attempts to connect to a destination network address by any of a set of network devices coupled to the network;
logging the network device and the destination network address associated with a set of failed connection attempts; and
responsive to the failed connection attempts associated with a network device being determined non-normal, declaring a presence of a worm.

### Claim 31

A system for detecting a worm, the system comprising:
a network monitoring module configured to observe a plurality of failed network connection attempts, each failed network connection attempt originating from any of a set of sources and directed to a destination network address;
a logging module coupled to the network monitoring module for logging the failed attempts; and
an analysis module coupled to the logging module for declaring a presence of a worm responsive to a source's failed network connection attempts during a period of time meeting at least one of a set of threshold criteria.

### Claim 32 (depends on 31)

The system of claim 31, wherein the threshold criteria comprise:
a number of failed network connection attempts; and
a diversity of destination network addresses associated with the failed network connection attempts.

### Claim 33 (depends on 31)

The system of claim 31, wherein the threshold criteria comprise a correlation with a prior DNS lookup having not been performed before an associated failed network connection attempt.

### Claim 34 (depends on 31)

The system of claim 31, wherein the threshold criteria comprise a weighting associated with at least one of the failed network connection attempts according to an attribute thereof.

### Claim 35 (depends on 31)

The system of claim 31, further comprising:
a response module coupled to the analysis module, the response module configured to respond to the worm upon a declaration thereof.

### Claim 36 (depends on 35)

The system of claim 35, wherein the response module is configured to alert a user of a declared worm.

### Claim 37 (depends on 31)

The system of claim 31, wherein at least one source is a process running on a network device, and the response module is configured to terminate the process associated with a declared worm.

### Claim 38 (depends on 31)

The system of claim 31, wherein at least one source is a network device coupled to a network, and the response module is configured to terminate network access of the network device associated with a declared worm.

### Claim 39 (depends on 31)

The system of claim 31, wherein the analysis module is configured to exclude a source from the threshold criteria, whereby the source's failed network connection attempts do not cause the analysis module to declare a worm.
