# US 2024/0403413 A1 · Systems and methods for a runtime virtual barrier for fine grained execution control

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

- Number: US 2024/0403413 A1
- Document ID: US20240403413A1
- Status: Published application
- Kind: A1
- Application number: 18/693,608
- Filed: 2022-10-03
- Published: 2024-12-05
- Earliest claimed: 2021-10-03
- Assignees: Seraphic Algorithms Ltd.
- Applicants: Seraphic Algorithms Ltd.
- Inventors: Avihay Cohen
- Web page: https://patentgrep.com/patent/US20240403413A1

## CPC

- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/6245: {Protecting personal data, e.g. for financial or medical purposes}
- G06F 16/986: {Document structures and storage, e.g. HTML extensions}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/554: {involving event detection and direct action}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L 63/1491: {using deception as countermeasure, e.g. honeypots, honeynets, decoys or entrapment}
- G06F 2221/033: Test or assess software
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, methods, and non-transitory computer readable media including instructions for implementing a runtime virtual barrier for fine grained execution control are disclose. Implementing the runtime virtual barrier for fine grained execution control includes receiving, by an application capable of JavaScript execution, an executable code including an API invocation; intercepting, by a virtual barrier, the API invocation; determining that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event; based on the determination that the API invocation is an invocation for a native API configured for subsequent execution, recording an invocation source identifier; and upon occurrence of the trigger event: retrieving the invocation source identifier; and influencing execution of the native API based on the invocation source identifier.

## Claims

### Claim 1

A non-transitory computer readable medium containing instructions that when executed by at least one processor cause the at least one processor to perform operations, comprising:
receiving, by an application capable of JavaScript execution, an executable code including an API invocation;
intercepting, by a virtual barrier, the API invocation;
determining that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event;
based on the determination that the API invocation is an invocation for a native API configured for subsequent execution, recording an invocation source identifier; and
upon occurrence of the trigger event:
retrieving the invocation source identifier; and
influencing execution of the native API based on the invocation source identifier.

### Claim 2 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein determining that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event includes inspecting at least one argument of the API invocation, and identifying the at least one argument as a callback function.

### Claim 3 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the instructions are further executable by the at least one processor to cause the at least one processor to perform additional operations, comprising: prior to detecting the trigger event, generating a wrapped API and replacing the invocation for the native API with the wrapped API, wherein influencing execution of the native API includes executing the wrapped API in place of the native API.

### Claim 4 (depends on 3)

The non-transitory computer readable medium of claim 3, wherein replacing the invocation for the native API with the wrapped API imposes the virtual barrier between the executable code and the native API.

### Claim 5 (depends on 3)

The non-transitory computer readable medium of claim 3, wherein recording the invocation source identifier includes storing an association between the wrapped API, the native API, and the invocation source identifier.

### Claim 6 (depends on 5)

The non-transitory computer readable medium of claim 5, wherein the association is stored in a map accessible by the wrapped API and the native API.

### Claim 7 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein influencing execution of the native API based on the invocation source identifier includes modifying the execution when the invocation source identifier is determined to violate a security rule.

### Claim 8 (depends on 7)

The non-transitory computer readable medium of claim 7, wherein modifying the execution includes suspending the execution.

### Claim 9 (depends on 7)

The non-transitory computer readable medium of claim 7, wherein modifying the execution includes:
detecting an object having a size exceeding a predetermined threshold; and
in response to detecting an object having a size exceeding a predetermined threshold, decreasing the size of the object.

### Claim 10 (depends on 9)

The non-transitory computer readable medium of claim 9, wherein decreasing the size includes restoring an original size of the object.

### Claim 11 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the instructions are further executable by the at least one processor to cause the at least one processor to perform additional operations, comprising: inspecting at least one return value of the influenced execution of the native API.

### Claim 12 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the trigger event is a network request.

### Claim 13 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the trigger event is a Document Object Model (DOM) event.

### Claim 14 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the trigger event is a user input.

### Claim 15 (depends on 14)

The non-transitory computer readable medium of claim 14, wherein the user input is at least one of: a computer mouse gesture, a gesture on a touch screen, a cursor movement, or a key press.

### Claim 16 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the source identifier is a Uniform Resource Locator (URL).

### Claim 17 (depends on 1)

The non-transitory computer readable medium of claim 1, wherein the instructions are further executable by the at least one processor to cause the at least one processor to perform additional operations, comprising: recording an invocation sequence of invocations of the native API in the executable code and determining an asynchronous loop when the invocation sequence satisfies at least one invocation sequence pattern parameter.

### Claim 18

A method for performing cybersecurity operations for tracing an execution of an asynchronous Application Programming Interface (API), the method comprising:
receiving, by an application capable of JavaScript execution, an executable code including an API invocation;
intercepting, by a virtual barrier, the API invocation;
determining that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event;
based on the determination that the API invocation is an invocation for a native API configured for subsequent execution, recording an invocation source identifier;
upon detecting the trigger event:
retrieving the invocation source identifier; and
influencing execution of the native API based on the invocation source identifier.

### Claim 19 (depends on 18)

The method of claim 18, wherein influencing execution of the native API based on the invocation source identifier includes modifying the execution when the invocation source identifier is determined to be suspicious.

### Claim 20

A system for performing cybersecurity operations for tracing an execution of an asynchronous Application Programming Interface (API), the system comprising:
at least one processor configured to:
receive, by an application capable of JavaScript execution, an executable code including an API invocation;
intercept, by a virtual barrier, the API invocation;
determine that the API invocation is an invocation for a native API configured for subsequent execution in response to a trigger event;
based on the determination that the API invocation is an invocation for a native API configured for subsequent execution record an identifier for a source of the native API;
upon detecting the trigger event:
retrieve the invocation source identifier; and
influence execution of the native API based on the invocation source identifier.

### Claim at position 21

21-159. (canceled)
