IP Library Granted Patent US 12,652,289
Granted Patent B2
US 12,652,289 · App. 17/958,524 · Granted Jun 9, 2026

Web 3.0 object reputation

Inventors: Zoltan Balazs (Budapest, HU); Andras Tevesz (Győr, HU); Christian Kiss-Toth (Budapest, HU); Santeri Kangas (Espoo, FI)
Assignee: Cujo LLC
H04L63/1408G06F40/279H04L63/1441
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,652,289
App. No.
17/958,524
Granted
Jun 9, 2026
Kind
B2
Abstract

A method, apparatus, and a computer-readable medium for a web object reputation processing, especially in Web3. The method includes: intercepting data transmitted in a data connection related to a current decentralized application running in a user apparatus, wherein the current decentralized application comprises a frontend implementing a web user interface for a user of the user apparatus, and a backend implemented as a smart contract; determining a reputation of a web object related to the frontend of the current decentralized application; and in response to determining that the reputation of the web object is malicious, blocking the data connection.

Claims (60)

1 . A computer-implemented method comprising:

intercepting data transmitted in a data connection related to a current decentralized application running in a user apparatus, wherein the current decentralized application comprises a frontend implementing a web user interface for a user of the user apparatus, and a backend implemented as a smart contract;

searching the data to identify a keyword in the data;

determining, based on the keyword matching a keyword in a collection of keywords related to the current decentralized application, that the data relates to the current decentralized application;

in response to determining that the data relates to the current decentralized application, determining a reputation of a web object related to the frontend of the current decentralized application; and

in response to determining that the reputation of the web object is malicious, blocking the data connection.

2 . The method of claim 1 , further comprising:

detecting an address of the web object from the data, wherein the frontend is running in the web object associated with the address; and

wherein determining the reputation of the web object related to the frontend of the current decentralized application further comprises determining the reputation of the web object related to the frontend of the current decentralized application based on the address.

3 . The method of claim 2 , wherein the address comprises one or more of an internet protocol address, a fully qualified domain name, a universal resource locator, and a smart contract address.

4 . The method of claim 1 , wherein determining the reputation of the web object related to the frontend of the current decentralized application further comprises:

retrieving a retrieved reputation for the web object from a web object reputation database; and

setting the reputation of the web object related to the frontend of the current decentralized application based on the retrieved reputation.

5 . The method of claim 4 , further comprising:

continuously updating, by a supervised machine learning algorithm using a training set comprising malicious web objects and trustworthy web objects, the web object reputation database.

6 . The method of claim 5 , further comprising:

collecting the malicious web objects using an open source intelligence.

7 . The method of claim 1 , wherein determining the reputation of the web object related to the frontend of the current decentralized application further comprises:

inspecting the smart contract; and

in response to determining that the smart contract has been used to mint or buy one or more fungible tokens or non-fungible tokens with a past decentralized application, and that the current decentralized application is different from the past decentralized application, setting the reputation of the web object malicious.

8 . The method of claim 1 , further comprising:

subsequent to blocking the data connection, preventing a wallet connect request from the current decentralized application in the data to connect a cryptocurrency wallet of the user of the user apparatus to the web object related to the current decentralized application.

9 . The method of claim 1 , further comprising:

subsequent to blocking the data connection, preventing a sale transaction request from the current decentralized application in the data to sell a fungible token or a non-fungible token defined by the smart contract in a blockchain and accessible by a private key kept in a cryptocurrency wallet of the user of the user apparatus.

10 . The method claim 1 , further comprising:

in response to determining that the reputation of the web object is questionable, seizing the data connection; and

transmitting, to a cybersecurity application running in the user apparatus, a warning related to the data connection of the current decentralized application.

11 . The method of claim 10 , further comprising:

receiving a response from the cybersecurity application; and

based on the response, allowing the data connection or blocking the data connection.

12 . The method of claim 1 , further comprising:

in response to determining that the reputation of the web object is trustworthy, allowing the data connection.

13 . An apparatus comprising:

one or more memories; and

one or more processors coupled to the one or more memories configured to:

intercept data transmitted in a data connection related to a current decentralized application running in a user apparatus, wherein the current decentralized application comprises a frontend implementing a web user interface for a user of the user apparatus, and a backend implemented as a smart contract;

search the data to identify a keyword in data;

determine, based on the keyword matching a keyword in a collection of keywords related to the current decentralized application, that the data relates to the current decentralized application;

in response to determining that the data relates to the current decentralized application, determine a reputation of a web object related to the frontend of the current decentralized application; and

in response to determining that the reputation of the web object is malicious, block the data connection.

14 . The method of claim 1 , wherein the collection of keywords is used by a JavaScript framework related to the current decentralized application.

15 . The apparatus of claim 13 , wherein the one or more processors coupled to the one or more memories further configured to:

detect an address of the web object from the data, wherein the frontend is running in the web object associated with the address; and

wherein to determine the reputation of the web object related to the frontend of the current decentralized application further comprises to determine the reputation of the web object related to the frontend of the current decentralized application based on the address.

16 . The apparatus of claim 15 , wherein the address comprises one or more of an internet protocol address, a fully qualified domain name, a universal resource locator, and a smart contract address.

17 . The apparatus of claim 13 , wherein to determine the reputation of the web object related to the frontend of the current decentralized application further comprises:

to inspect the smart contract; and

in response to determining that the smart contract has been used to mint or buy one or more fungible tokens or non-fungible tokens with a past decentralized application, and that the current decentralized application is different from the past decentralized application, to set the reputation of the web object malicious.

18 . A non-transitory computer-readable medium comprising a computer program with instructions which, when executed by an apparatus, cause the apparatus to:

intercept data transmitted in a data connection related to a current decentralized application running in a user apparatus, wherein the current decentralized application comprises a frontend implementing a web user interface for a user of the user apparatus, and a backend implemented as a smart contract;

search the data to identify a keyword in data;

determine, based on the keyword matching a keyword in a collection of keywords related to the current decentralized application, that the data relates to the current decentralized application;

in response to determining that the data relates to the current decentralized application, determine a reputation of a web object related to the frontend of the current decentralized application; and

in response to determining that the reputation of the web object is malicious, block the data connection.

19 . The medium of claim 18 , wherein the apparatus is further caused to:

detect an address of the web object from the data, wherein the frontend is running in the web object associated with the address; and

wherein to determine the reputation of the web object related to the frontend of the current decentralized application further comprises to determine the reputation of the web object related to the frontend of the current decentralized application based on the address.

20 . The medium of claim 18 , wherein to determine the reputation of the web object related to the frontend of the current decentralized application further comprises:

to inspect the smart contract; and

in response to determining that the smart contract has been used to mint or buy one or more fungible tokens or non-fungible tokens with a past decentralized application, and that the current decentralized application is different from the past decentralized application, to set the reputation of the web object malicious.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2022
From: BALAZS, ZOLTAN; TEVESZ, ANDRAS; KISS-TOTH, CHRISTIAN; KANGAS, SANTERI
To: CUJO LLC
Reel/Frame 061348/0766 →
Continuity (1)
Related Publication 20240114038A1 · Apr 4, 2024
References Cited (20)
US 6862629B1 · Hericourt · 2005 [cited by examiner]
US 10915641B2 · Smith et al. · 2021 [cited by applicant]
US 20060253584A1 · Dixon · 2006 [cited by examiner]
US 20110023096A1 · Xiao et al. · 2011 [cited by applicant]
US 20150163236A1 · Niemela · 2015 [cited by examiner]
US 20150227897A1 · Loera · 2015 [cited by examiner]
US 20170193513A1 · Zand-Biglari · 2017 [cited by applicant]
US 20190386969A1 · Verzun et al. · 2019 [cited by applicant]
US 20210019827A1 · Kim · 2021 [cited by examiner]
US 20210110047A1 · Fang · 2021 [cited by applicant]
US 20210334371A1 · Ke · 2021 [cited by examiner]
US 20220067738A1 · Fang et al. · 2022 [cited by applicant]
US 20220067752A1 · Fang et al. · 2022 [cited by applicant]
US 20230401571A1 · Lee · 2023 [cited by examiner]
CN 109978517A · 2019 [cited by applicant]
CN 113327108A · 2021 [cited by applicant]
Author Unknown, “Machine Learning and Real-Time Fraud Detection in Web3 Demystified,” AnChain.AI, https://anchain.ai/blog/ml-and-real-time-fraud-detection-in-web3/, Jul. 11, 2017, 6 pages. [cited by applicant]
Extended European Search Report for EP Patent Application No. 22199452.8, mailed Mar. 13, 2023, 9 pages. [cited by applicant]
Gore, Ari, “Hello, Web3 Firewall!,” https://zengo.com/hello-web3-firewall, Aug. 23, 2022, 11 pages. [cited by applicant]
Fiszer, Michael-David, “Introducing Clearsign: The Web3 Firewall to Secure your Assets,” https://zengo.com/introducing-clearsign-the-web3-firewall-to-secure-your-assets, Jun. 23, 2022, 9 pages. [cited by applicant]