# US 2026/0291989 A1 · Method and system for triggering remedial action on client device

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

- Number: US 2026/0291989 A1
- Document ID: US20260291989A1
- Status: Published application
- Kind: A1
- Application number: 19/461,149
- Filed: 2026-01-27
- Published: 2026-09-24
- Earliest claimed: 2025-03-18
- Assignees: Y.E. Hub Armenia LLC
- Applicants: Y.E. Hub Armenia LLC
- Inventors: Vasily ZIUZIN; Vitaly KALCHENKO; Zinovy NIS; Alexander ULYANOV
- Web page: https://patentgrep.com/patent/US20260291989A1

## CPC

- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, servers, client devices, systems and processors for triggering a remedial action on a client device are disclosed. The method includes, during a client-side phase: acquiring, using a browser, generating, using a client-side DSSM executed on the client device, a DSSM output based on the client-side webpage data, generating, using a client-side GB model, a client-side probability score based on the DSSM output and the client-side webpage data, and in response to the client-side probability score being above a pre-determined threshold, selectively triggering a server-side phase. The method includes, during a server-side phase: acquiring the DSSM output, acquiring server-side webpage data indicative of the webpage being accessed by the client device, generating, using a server-side GB model, a server-side probability score based on the DSSM output and the server-side webpage data, and in response to the server-side probability score being above an other pre-determined threshold, selectively triggering the remedial action.

## Claims

### Claim 1

A method of triggering a remedial action on a client device, the client device being communicatively coupled to a server, the method comprising:
during a client-side phase:
acquiring, using a browser application executed on the client device, client-side webpage data indicative of a webpage being accessed by the client device;
generating, using a client-side DSSM executed on the client device, a DSSM output based on the client-side webpage data,
the DSSM output being indicative of (i) features representing the webpage and (ii) a preliminary likelihood of that the webpage is a malicious webpage;
generating, using a client-side GB model executed on the client device, a client-side probability score based on the DSSM output and the client-side webpage data,
the client-side probability score being indicative of a client-side likelihood of the webpage is a malicious webpage; and
in response to the client-side probability score being above a pre-determined threshold, selectively triggering a server-side phase; and
during a server-side phase:
acquiring, by the server from the client device, the DSSM output;
acquiring, by the server, server-side webpage data indicative of the webpage being accessed by the client device;
generating, using a server-side GB model executed on the server, a server-side probability score based on the DSSM output and the server-side webpage data,
the server-side probability score being indicative of a server-side likelihood of the webpage is a malicious webpage; and
in response to the server-side probability score being above an other pre-determined threshold, selectively triggering the remedial action.

### Claim 2 (depends on 1)

The method of claim 1, wherein the method further comprises generating one or more client-side counters based on the client-side webpage data.

### Claim 3 (depends on 1)

The method of claim 1, wherein the client-side webpage data comprises a URL, a title, and other content of webpage.

### Claim 4 (depends on 1)

The method of claim 1, wherein the method further comprises generating one or more server-side counters based on the server-side webpage data.

### Claim 5 (depends on 1)

The method of claim 1, wherein the method further comprises the DSSM output comprises one or more embeddings indicative of features representing the webpage, and a preliminary probability score.

### Claim 6 (depends on 1)

The method of claim 1, wherein the method further comprises using a vision model to generate an other embedding indicative of visual features of a screenshot of the webpage generated by the browser application, and using the other embedding for generating the client-side probability score.

### Claim 7 (depends on 1)

The method of claim 1, wherein the selectively triggering the remedial action comprises triggering display of a visual element to a user using the browser application and indicative of that the webpage is a malicious webpage.

### Claim 8

A system for triggering a remedial action on a client device, the system comprising the client device communicatively coupled to a server, the system being configured to:
during a client-side phase:
acquire, using a browser application executed on the client device, client-side webpage data indicative of a webpage being accessed by the client device;
generate, using a client-side DSSM executed on the client device, a DSSM output based on the client-side webpage data,
the DSSM output being indicative of (i) features representing the webpage and (ii) a preliminary likelihood of that the webpage is a malicious webpage;
generate, using a client-side GB model executed on the client device, a client-side probability score based on the DSSM output and the client-side webpage data,
the client-side probability score being indicative of a client-side likelihood of the webpage is a malicious webpage; and
in response to the client-side probability score being above a pre-determined threshold, selectively trigger a server-side phase; and
during the server-side phase:
acquire, by the server from the client device, the DSSM output;
acquire, by the server, server-side webpage data indicative of the webpage being accessed by the client device;
generate, using a server-side GB model executed on the server, a server-side probability score based on the DSSM output and the server-side webpage data,
the server-side probability score being indicative of a server-side likelihood of the webpage is a malicious webpage; and
in response to the server-side probability score being above an other pre-determined threshold, selectively trigger the remedial action.

### Claim 9 (depends on 8)

The system of claim 8, wherein the system is further configured to generate one or more client-side counters based on the client-side webpage data.

### Claim 10 (depends on 8)

The system of claim 8, wherein the client-side webpage data comprises a URL, a title, and other content of webpage.

### Claim 11 (depends on 8)

The system of claim 8, wherein the system is further configured to generate one or more server-side counters based on the server-side webpage data.

### Claim 12 (depends on 8)

The system of claim 8, wherein the DSSM output comprises one or more embeddings indicative of features representing the webpage, and a preliminary probability score.

### Claim 13 (depends on 8)

The system of claim 8, wherein the system is further configured to use a vision model to generate an other embedding indicative of visual features of a screenshot of the webpage generated by the browser application, and to use the other embedding for generating the client-side probability score.

### Claim 14 (depends on 8)

The system of claim 8, wherein to selectively trigger the remedial action comprises the system configured to trigger display of a visual element to a user using the browser application and indicative of that the webpage is a malicious webpage.

### Claim 15

A method of triggering a remedial action on a client device, the client device being communicatively coupled to a server, the method comprising:
acquiring, by the server from the client device, an indication for triggering server-side classification of a webpage, the indication comprising a DSSM output,
the indication being acquired in response to a client-side classification of the webpage, the client-side classification being performed by a DSSM model and a GB model executed on the client device,
the DSSM model having been configured to generate the DSSM output based on browser webpage data, the DSSM output being indicative of (i) features representing the webpage and (ii) a preliminary likelihood of the webpage being a malicious webpage, and
the GB model having been configured to generate, based on the DSSM output and the browser webpage data, a client-side probability score indicative of a client-side likelihood of the webpage being a malicious webpage,
acquiring, by the server, server-side webpage data;
generating, using a server-side GB model executed on the server, a server-side probability score based on the DSSM output and the server-side webpage data,
the server-side probability score being indicative of a server-side likelihood of the webpage being a malicious webpage; and
in response to the server-side probability score being above a pre-determined threshold, selectively triggering the remedial action.
