# US 2023/0273996 A1 · Typo squatting, dependency confusion, and brandjacking detection

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

- Number: US 2023/0273996 A1
- Document ID: US20230273996A1
- Status: Published application
- Kind: A1
- Application number: 17/681,143
- Filed: 2022-02-25
- Published: 2023-08-31
- Earliest claimed: 2022-02-25
- Assignees: Micro Focus LLC
- Applicants: Micro Focus LLC
- Inventors: Alexander Hoole; Michael F. Angelo
- Web page: https://patentgrep.com/patent/US20230273996A1

## CPC

- G06F 21/563: {by source code analysis}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/568: {eliminating virus, restoring damaged files}
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A software build environment is scanned for one or more potentially malicious code paths. In response to scanning the software build environment for the one or more potentially malicious code paths, one or more potentially malicious code paths are identified. The identified one or more potentially malicious code paths comprise at least one of: a typo squat code path, a dependency confusion code path, and a brandjack code path. In response to identifying the one or more potentially malicious code paths a microprocessor does at least one of: generate a notification identifying the one or more potentially malicious code paths, automatically change and/or remove the one or more potentially malicious code paths and deny the start of a build process.

## Claims

### Claim 1

A system comprising:
a microprocessor; and
a computer readable medium, coupled with the microprocessor and comprising microprocessor readable and executable instructions that, when executed by the microprocessor, cause the microprocessor to:
scan a software build environment for one or more potentially malicious code paths;
in response to scanning the software build environment for the one or more potentially malicious code paths, identify the one or more potentially malicious code paths, wherein the identified one or more potentially malicious code paths comprise at least one of: a typo squat code path, a dependency confusion code path, and a brandjack code path; and
in response to identifying the one or more potentially malicious code paths the microprocessor does at least one of:
generate a notification identifying the one or more potentially malicious code paths;
automatically change and/or remove the one or more potentially malicious code paths; and
deny the start of a build process.

### Claim 2 (depends on 1)

The system of claim 1, wherein the microprocessor readable and executable instructions further cause the microprocessor to:
in response to scanning the software build environment for the one or more potentially malicious code paths:
identify one or more software components associated with the one or more potentially malicious code paths; and
compare hashes the for the or more software components to known hashes of legitimate versions of the one or more software components to validate whether the one or more software components are valid.

### Claim 3 (depends on 1)

The system of claim 1, wherein identifying the one or more potentially malicious code paths comprises the typo squat code path.

### Claim 4 (depends on 3)

The system of claim 3, wherein the typo squat code path is identified based on at least one of: keyboard keys next to each other, an extra character, a missing character, switched characters, a hidden character, other special characters, hyphenated strings, a spelling mistake, an alternate spelling, use of alternate character encoding standards, an incorrect domain ending, and a pluralization.

### Claim 5 (depends on 1)

The system of claim 1, wherein identifying the one or more potentially malicious code paths comprises the dependency confusion code path.

### Claim 6 (depends on 5)

The system of claim 5, wherein the dependency confusion code path is identified based on at least one of: an any version indicator, a less than version indicator, a less than or equal to version indicator, a greater than version indicator, a greater than or equal to version indicator, approximately equivalent to version indicator, a compatible with version indicator, and a range of version indicator.

### Claim 7 (depends on 1)

The system of claim 1, wherein identifying the one or more potentially malicious code paths comprises the brandjack code path.

### Claim 8 (depends on 1)

The system of claim 1, wherein at least one of the one or more potentially malicious code paths is based a second level or greater of a dependency tree.

### Claim 9 (depends on 1)

The system of claim 1, wherein the at least one of the one or more potentially malicious code paths is identified based on a hash of the one or more potentially malicious code paths.

### Claim 10

A method comprising:
scanning, by a microprocessor, a software build environment for one or more potentially malicious code paths;
in response to scanning the software build environment for the one or more potentially malicious code paths, identifying, by the microprocessor, the one or more potentially malicious code paths, wherein the identified one or more potentially malicious code paths comprise at least one of: a typo squat code path, a dependency confusion code path, and a brandjack code path; and
in response to identifying the one or more potentially malicious code paths the microprocessor does at least one of:
generating a notification identifying the one or more potentially malicious code paths;
automatically changing and/or removing the one or more potentially malicious code paths; and
denying the start of a build process.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
in response to scanning the software build environment for the one or more potentially malicious code paths:
identifying one or more software components associated with the one or more potentially malicious code paths; and
comparing hashes for the or more software components to known hashes of legitimate versions of the one or more software components to validate whether the one or more software components are valid.

### Claim 12 (depends on 10)

The method of claim 10, wherein identifying the one or more potentially malicious code paths comprises the typo squat code path.

### Claim 13 (depends on 12)

The method of claim 12, wherein the typo squat code path is identified based on at least one of: keyboard keys next to each other, an extra character, a missing character, switched characters, a hidden character, other special characters, hyphenated strings, a spelling mistake, an alternate spelling, use of alternate character encoding standards, an incorrect domain ending, and a pluralization.

### Claim 14 (depends on 10)

The method of claim 10, wherein identifying the one or more potentially malicious code paths comprises the dependency confusion code path.

### Claim 15 (depends on 14)

The method of claim 14, wherein the dependency confusion code path is identified based on at least one of: an any version indicator, a less than version indicator, a less than or equal to version indicator, a greater than version indicator, a greater than or equal to version indicator, approximately equivalent to version indicator, a compatible with version indicator, and a range of version indicator.

### Claim 16 (depends on 10)

The method of claim 10, wherein identifying the one or more potentially malicious code paths comprises the brandjack code path.

### Claim 17 (depends on 10)

The method of claim 10, wherein at least one of the one or more potentially malicious code paths is based a second level or greater of a dependency tree.

### Claim 18 (depends on 10)

The method of claim 10, wherein the at least one of the one or more potentially malicious code paths is identified based on a hash of the one or more potentially malicious code paths.

### Claim 19

A non-transient computer readable medium having stored thereon instructions that cause a processor to execute a method, the method comprising:
instructions to:
scan a software build environment for one or more potentially malicious code paths;
in response to scanning the software build environment for the one or more potentially malicious code paths, identify the one or more potentially malicious code paths, wherein the identified one or more potentially malicious code paths comprise at least one of: a typo squat code path, a dependency confusion code path, and a brandjack code path; and
in response to identifying the one or more potentially malicious code paths the microprocessor does at least one of:
generate a notification identifying the one or more potentially malicious code paths;
automatically change and/or remove the one or more potentially malicious code paths; and
deny the start of a build process.

### Claim 20 (depends on 19)

The non-transient computer readable of claim 19, wherein identifying the one or more potentially malicious code paths comprises the typo squat code path.
