# US 2024/0205236 A1 · Systems and methods for identifying malicious cryptographic addresses

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

- Number: US 2024/0205236 A1
- Document ID: US20240205236A1
- Status: Published application
- Kind: A1
- Application number: 18/394,109
- Filed: 2023-12-22
- Published: 2024-06-20
- Earliest claimed: 2022-03-18
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Xiaoguang Zhu; Kevin Osborn; Samuel Rapowitz
- Web page: https://patentgrep.com/patent/US20240205236A1

## CPC

- H04L 63/14: {for detecting or protecting against malicious traffic}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for identifying malicious cryptographic wallet addresses are disclosed. The systems and methods can receive a first plurality of tokens and an indication of a potentially malicious cryptographic wallet address from a requesting user. The system can identify a plurality of associated wallet addresses, and compare the associated wallet addresses to a stored list of malicious cryptographic wallet addresses. The system can determine a subset of the identified associated cryptographic wallet addresses that are malicious and assign a maliciousness rating to the potentially malicious cryptographic wallet address. The system can provide the maliciousness rating to the requesting user.

## Claims

### Claim 1

(canceled)

### Claim 2

A system for identifying malicious cryptographic wallet addresses, the system comprising:
a plurality of distributed processors; and
a plurality of distributed non-transient memories in communication with the plurality of distributed processors and storing instructions, that when executed by the plurality of distributed processors are configured to cause the system to:
receive, from reporter cryptographic wallet addresses, a plurality of reports identifying malicious cryptographic wallet addresses;
receive, from a first cryptographic wallet address associated with a first cryptographic wallet, a first plurality of tokens and a validation request for a second cryptographic wallet address associated with a second cryptographic wallet;
query the plurality of reports to identify a subset of the malicious cryptographic wallet addresses that are associated with the second cryptographic wallet address based on the query of the subset;
assign a maliciousness rating to the second cryptographic wallet address;
provide the maliciousness rating to the first cryptographic wallet address; and
transmit at least a portion of the first plurality of tokens to at least a portion of the reporter cryptographic wallet addresses.

### Claim 3 (depends on 2)

The system of claim 2, wherein identifying the subset of the malicious cryptographic wallet addresses that are associated with the second cryptographic wallet address is further based on identifying a master public key associated with the second cryptographic wallet address.

### Claim 4 (depends on 2)

The system of claim 2, wherein the instructions are further configured to cause the system to:
receive, from second reporter cryptographic wallet addresses, a second plurality of reports indicating that the second cryptographic wallet address is malicious;
determine whether the second plurality of reports exceeds a threshold number of reports; and
responsive to determining the second plurality of reports exceeds the threshold number of reports:
validate the plurality of reports; and
transmit at least a portion of a second plurality of tokens to at least a portion of the second reporter cryptographic wallet addresses.

### Claim 5 (depends on 4)

The system of claim 4, wherein the maliciousness rating is based in part on a recency of the threshold number of second reports.

### Claim 6 (depends on 2)

The system of claim 2, wherein each token of the first plurality of tokens comprises a native token associated with a first blockchain implemented by the plurality of distributed processors.

### Claim 7 (depends on 6)

The system of claim 6, wherein the second cryptographic wallet address is associated with a second blockchain that is separate from the first blockchain.

### Claim 8 (depends on 7)

The system of claim 7, wherein the second blockchain is implemented by a second plurality of distributed processors different than the plurality of distributed processors.

### Claim 9 (depends on 2)

The system of claim 2, wherein the maliciousness rating is determined by a smart contract implemented by the plurality of distributed processors.

### Claim 10

A method for identifying malicious cryptographic wallet addresses, the method comprising:
receiving, from reporter cryptographic wallet addresses, a plurality of reports identifying malicious cryptographic wallet addresses;
receiving, from a first cryptographic wallet address associated with a first cryptographic wallet, a first plurality of tokens and a validation request for a second cryptographic wallet address associated with a second cryptographic wallet;
querying the plurality of reports to identify a subset of the malicious cryptographic wallet addresses that are associated with the second cryptographic wallet address based on the query of the subset;
assigning a maliciousness rating to the second cryptographic wallet address;
providing the maliciousness rating to the first cryptographic wallet address; and
transmitting at least a portion of the first plurality of tokens to at least a portion of the reporter cryptographic wallet addresses.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
receiving, from second reporter cryptographic wallet addresses, a second plurality of reports indicating that the second cryptographic wallet address is malicious;
determining whether the second plurality of reports exceeds a threshold number of reports; and
responsive to determining the second plurality of reports exceeds the threshold number of reports:
validating the plurality of reports; and
transmitting at least a portion of a second plurality of tokens to at least a portion of the second reporter cryptographic wallet addresses.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
receiving, from second reporter cryptographic wallet addresses, a second plurality of reports indicating that the second cryptographic wallet address is malicious;
determining that at least a first portion of the second plurality of reports are incorrect; and
responsive to determining that the first portion of the second plurality of reports are incorrect, transmit less than a second plurality of tokens to at least a portion of the second reporter cryptographic wallet addresses.

### Claim 13 (depends on 10)

The method of claim 10, wherein each token of the first plurality of tokens comprises a native token associated with a first blockchain.

### Claim 14 (depends on 13)

The method of claim 13, wherein the second cryptographic wallet address is associated with a second blockchain that is separate from the first blockchain.

### Claim 15 (depends on 10)

The method of claim 10, wherein the maliciousness rating is determined by a smart contract implemented by a plurality of distributed processors.

### Claim 16

A system for identifying malicious cryptographic wallet addresses, the system comprising:
a plurality of distributed processors; and
a plurality of distributed non-transient memories in communication with the plurality of distributed processors and storing instructions, that when executed by the plurality of distributed processors are configured to cause the system to:
receive, from a reporter cryptographic wallet address, a first report identifying malicious cryptographic wallet addresses;
receive, from a first cryptographic wallet address associated with a first cryptographic wallet, a first plurality of tokens and a validation request for a second cryptographic wallet address associated with a second cryptographic wallet;
identify a subset of the malicious cryptographic wallet addresses that are associated with the second cryptographic wallet address;
assign a maliciousness rating to the second cryptographic wallet address;
provide the maliciousness rating to the first cryptographic wallet address; and
transmit at least a portion of the first plurality of tokens to the reporter cryptographic wallet address.

### Claim 17 (depends on 16)

The system of claim 16, wherein the instructions are further configured to cause the system to:
receive, from a second reporter cryptographic wallet address, a second report indicating that the second cryptographic wallet address is malicious;
determine whether the second report exceeds a threshold number of received reports; and
responsive to determining the second report exceeds the threshold number of received reports:
validate the first report; and
transmit at least a portion of a second plurality of tokens to the second reporter cryptographic wallet address.

### Claim 18 (depends on 17)

The system of claim 17, wherein the maliciousness rating is based in part on a recency of the threshold number of received reports.

### Claim 19 (depends on 16)

The system of claim 16, wherein identifying the subset of the malicious cryptographic wallet addresses that are associated with the second cryptographic wallet address is based on identifying a master public key associated with the second cryptographic wallet address.

### Claim 20 (depends on 16)

The system of claim 16, wherein the instructions are further configured to cause the system to:
receive, from a second reporter cryptographic wallet address, a second report indicating that the second cryptographic wallet address is malicious;
determine that the second report is incorrect; and
responsive to determining the second report is incorrect, transmit less than a second plurality of tokens to the second reporter cryptographic wallet address.

### Claim 21 (depends on 16)

The system of claim 16, wherein the maliciousness rating is determined by a smart contract implemented by the plurality of distributed processors.
