# US 2021/0344708 A1 · Utilizing clustering to identify ip addresses used by a botnet

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

- Number: US 2021/0344708 A1
- Document ID: US20210344708A1
- Status: Published application
- Kind: A1
- Application number: 16/864,350
- Filed: 2020-05-01
- Published: 2021-11-04
- Earliest claimed: 2020-05-01
- Assignees: Adobe Inc.
- Applicants: Adobe Inc.
- Inventors: Portase NICUSOR-SORIN; Cristian-Aurel OPINCARU; Manole CATALIN-TEODOR
- Web page: https://patentgrep.com/patent/US20210344708A1

## CPC

- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1433: {Vulnerability analysis}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 2463/144: Detection or countermeasures against botnets
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems are provided for identifying suspect Internet Protocol (IP) addresses, in accordance with embodiments described herein. In particular, embodiments described herein include obtaining a set of login pairs comprising login identifiers (e.g., user identifiers) and IP addresses used in attempts to login to a source. A set of IP clusters is generated using the set of login pairs. Each IP cluster can include one or more IP addresses identified as related based on a login identifier being used to attempt to login to the source via multiple IP addresses or an IP address being used to attempt to login to the source via multiple login identifiers. Thereafter, it is determined that a particular IP cluster exceeds a threshold amount of IP addresses. Each of the IP addresses within the particular IP cluster is designated as a suspect IP address.

## Claims

### Claim 1

A computer-implemented for identifying suspect Internet Protocol (IP) addresses, the method comprising:
obtaining a set of login pairs comprising user identifiers and IP addresses used in attempts to login to a source;
generating a set of IP clusters using the set of login pairs, wherein each IP cluster includes one or more IP addresses identified as related based on a user identifier being used to attempt to login to the source via multiple IP addresses or an IP address being used to attempt to login to the source via multiple user identifiers;
determining that a particular IP cluster exceeds a threshold amount of IP addresses; and
designating each of the IP addresses within the particular IP cluster as a suspect IP address based on the particular IP cluster exceeding the threshold amount of IP addresses.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, wherein the source comprises a website or an application.

### Claim 3 (depends on 1)

The computer-implemented method of claim 1, wherein the set of IP clusters is generated by:
generating a user mapping that maps user identifiers to corresponding IP addresses;
generating an IP mapping that maps IP addresses to corresponding users; and
alternately traversing between the user mapping and the IP mapping to generate the set of IP clusters.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the threshold amount of IP addresses is predetermined as a number of IP addresses that indicates a botnet.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1 further adding each of the IP addresses within the particular IP cluster to an IP blacklist.

### Claim 6 (depends on 5)

The computer-implemented method of claim 5, wherein the IP blacklist is used to provide secure logins to the source.

### Claim 7 (depends on 1)

The computer-implemented method of claim 1 further comprising:
detecting a subsequent login attempt made via one of the suspect IP addresses; and
initiating a multi-factor authentication based on the subsequent login attempt being made via the one of the suspect IP addresses.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1 further comprising:
detecting a subsequent login attempt made via one of the suspect IP addresses; and
initiating a challenge-response authentication based on the subsequent login attempt being made via the one of the suspect IP addresses.

### Claim 9

One or more computer-readable media having a plurality of executable instructions embodied thereon, which, when executed by one or more processors, cause the one or more processors to perform a method for identifying suspect Internet Protocol (IP) addresses, the method comprising:
obtaining a set of login pairs, each login pair comprising login identifiers and IP addresses used in attempts to login to a source;
generating an IP mapping and a login mapping using the set of login pairs, the IP mapping associating each IP address to corresponding login identifiers used for source login attempts and the login mapping associating each login identifier to corresponding IP addresses used for source login attempts;
generating an IP cluster having a plurality of related IP addresses by traversing the IP mapping and the login mapping to identify the plurality of related IP addresses, wherein the plurality of related IP addresses includes a first IP address and a second IP address that are related based on being used in association with a particular login identifier or based on third IP address being related to the first IP address and the second IP address;
determining that the IP cluster exceeds a threshold amount of IP addresses; and
enhancing login security for a subsequent login attempt made in association with an IP address of the IP cluster based on the determination that the IP cluster exceeds the threshold amount of IP addresses.

### Claim 10 (depends on 9)

The media of claim 9, wherein the IP mapping and the login mapping are alternately traversed to identify the plurality of related IP addresses.

### Claim 11 (depends on 9)

The media of claim 9, wherein the third IP address is in a first IP cluster with the first IP address and is in a second IP cluster with the second IP address.

### Claim 12 (depends on 9)

The media of claim 9, wherein the third IP address is in a first IP cluster with the first IP address and is in a second IP cluster with the second IP address, and wherein the first IP cluster and the second IP cluster are aggregated to generate the IP cluster based on the third IP address being in the first IP cluster and the second IP cluster.

### Claim 13 (depends on 9)

The media of claim 9, wherein enhancing login security comprises initiating a multi-factor authentication.

### Claim 14 (depends on 9)

The media of claim 9, wherein enhancing login security comprises initiating a challenge-response authentication.

### Claim 15 (depends on 9)

The media of claim 9 further comprising adding the plurality of related IP addresses to an IP blacklist.

### Claim 16 (depends on 9)

The media of claim 9 further comprising identifying the plurality of related IP addresses as a botnet.

### Claim 17

A computing system comprising:
one or more processors; and
one or more non-transitory computer-readable storage media, coupled with the one or more processors, having instructions stored thereon, which, when executed by the one or more processors, cause the computing system to provide:
means for detecting a botnet by clustering IP addresses related to one another based on a user identifier being used to attempt to login to a source via multiple IP addresses or an IP address being used to attempt to login to the source via multiple user identifiers; and
means for assessing risk of login attempts based on use of the clustered IP addresses associated with the botnet.

### Claim 18 (depends on 17)

The system of claim 17 further comprising means for enhancing security of login attempts.

### Claim 19 (depends on 17)

The system of claim 17, wherein the assessing risk of login attempts comprises determining whether a particular IP address used to access the source is in an IP blacklist.

### Claim 20 (depends on 18)

The system of claim 18, wherein the security of login attempts is enhanced via a multi-factor authentication or a challenge-response authentication.
