Method, system, storage medium and server for detecting malicious digital signatures

Abstract

The present invention provides a method, system, storage medium and server for detecting malicious digital signatures, the method comprising the following steps: receiving signature data uploaded by a user end; the signature data comprising a signature feature identifier; judging whether the interpretation information corresponding to the signature data is stored in the current database according to the signature feature identifier, and if so, returning the interpretation information corresponding to the signature data to the user end. In this way, each time before the user needs to send the signature data to a third party, the user can first upload the signature data to the server, and after obtaining the signature data uploaded by the user end, the server will retrieve the interpretation information corresponding to the signature data and send it to the user end. The user can clearly know the purpose of the current signature data by interpreting the returned interpretation information, thereby effectively preventing the occurrence of asset losses due to malicious signatures without knowing it.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a method, system, storage medium and server for detecting malicious digital signatures. Background Art

[0002] With the development of blockchain technology, people's demand for the application of digital signatures continues to increase. A digital signature is a set of hash values ​​calculated based on the user's unique key and the data to be signed. By calculating the digital signature, the legitimacy and uniqueness of the transaction can be guaranteed. However, taking the digital currency application scenario as an example, users cannot predict the purpose of each signature data in the page interacting with the digital wallet. Due to the lack of effective detection, users can easily sign malicious signature data inadvertently, resulting in frequent losses of digital currency funds.

[0003] Therefore, if a signature verification mechanism can be provided so that users can clearly understand the meaning behind each signature data when interacting with digital currency applications, it will be of great help in minimizing the occurrence of asset losses caused by users signing malicious signatures. Summary of the invention

[0004] Therefore, it is necessary to provide a technical solution for detecting malicious digital signatures to solve the problem that users cannot predict the purpose of each signature data and are prone to signing malicious signatures, resulting in their own property losses.

[0005] To achieve the above object, in a first aspect, a method for detecting a malicious digital signature comprises the following steps:

[0006] Receiving signature data uploaded by a user terminal; the signature data includes a signature feature identifier;

[0007] It is determined whether the interpretation information corresponding to the signature data is stored in the current database according to the signature feature identifier, and if so, the interpretation information corresponding to the signature data is returned to the user terminal.

[0008] Furthermore, the database is obtained according to the following method:

[0009] Capture multiple smart contract functions on the blockchain and perform signature calculations to obtain signature data corresponding to each smart contract function;

[0010] Add explanatory information to the signature data corresponding to each smart contract function, and store the explanatory information and the signature data corresponding to each smart contract function in the database.

[0011] Furthermore, the database includes a function signature information table and a function interpretation information table, the function signature information table is used to store the signature data corresponding to each smart contract function, and the function interpretation information table is used to store the interpretation information corresponding to each signature data.

[0012] Furthermore, the database also includes an unknown signature information table, and the unknown signature information table is used to store unknown signature data, and the unknown signature data is signature data for which corresponding interpretation information has not yet been stored in the current function interpretation information table.

[0013] Furthermore, the method further comprises:

[0014] When it is determined that the interpretation information corresponding to the signature data is not stored in the current database, adding marking information to the unknown signature data and storing it in the unknown signature information table;

[0015] Periodic polling is performed to detect whether new tag information appears in the unknown signature information table. If so, the unknown signature data corresponding to the tag information is retrieved and sent to the processing terminal for processing.

[0016] Furthermore, the method further comprises:

[0017] The receiving and processing terminal interprets the unknown signature data, adds the interpretative information of the unknown signature data to a function interpretation information table, and adds the processed unknown signature data to the function signature information table.

[0018] Furthermore, the method further includes: when it is determined that the interpretation information corresponding to the signature data is not stored in the current database, returning risk warning information to the user terminal.

[0019] In a second aspect, the present invention further provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed, the method described in the first aspect of the present invention is implemented.

[0020] In a third aspect, the present invention further provides a server, comprising:

[0021] A storage medium, which is the storage medium described in the second aspect of the present invention;

[0022] A processor is electrically connected to the storage medium and is used to execute the computer program stored in the storage medium to implement the method as described in the first aspect of the present invention.

[0023] In a fourth aspect, the present invention provides a system for detecting malicious digital signatures, comprising:

[0024] The server is the server described in the third aspect of the present invention;

[0025] The client terminal is connected to the server for communication and is used to upload the signature data to the server and receive feedback results from the server.

[0026] Different from the prior art, the present invention has the following characteristics:

[0027] The present invention provides a method, system, storage medium and server for detecting malicious digital signatures, the method comprising the following steps: receiving signature data uploaded by a user end; the signature data comprising a signature feature identifier; judging whether the interpretation information corresponding to the signature data is stored in the current database according to the signature feature identifier, and if so, returning the interpretation information corresponding to the signature data to the user end. In this way, each time before the user needs to send the signature data to a third party, the user can first upload the signature data to the server, and after obtaining the signature data uploaded by the user end, the server will retrieve the interpretation information corresponding to the signature data and send it to the user end. The user can clearly know the purpose of the current signature data by interpreting the returned interpretation information, thereby effectively preventing the occurrence of asset losses due to malicious signatures without knowing it. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 This is a flow chart of a method for detecting malicious digital signatures according to a first embodiment of the present invention;

[0029] Figure 2 This is a flow chart of a method for detecting malicious digital signatures according to a second embodiment of the present invention;

[0030] Figure 3 A flowchart of a method for detecting malicious digital signatures according to a third embodiment of the present invention;

[0031] Figure 4 A flowchart of a method for detecting malicious digital signatures according to a fourth embodiment of the present invention;

[0032] Figure 5 A flowchart of a method for detecting malicious digital signatures according to a fifth embodiment of the present invention;

[0033] Figure 6 This is a flow chart of a method for detecting malicious digital signatures according to a sixth embodiment of the present invention;

[0034] Figure 7 A schematic diagram of a server involved in an embodiment of the present invention;

[0035] Figure 8 A schematic diagram of a system for detecting malicious digital signatures according to an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to explain in detail the possible application scenarios, technical principles, specific schemes that can be implemented, and the purposes and effects that can be achieved, the following is a detailed description of the specific embodiments listed in conjunction with the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical solutions of the present application, and are therefore only used as examples, and cannot be used to limit the scope of protection of the present application.

[0037] Reference to "embodiment" herein means that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment of the present application. The term "embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment, nor does it particularly limit its independence or association with other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, the various technical features mentioned in the embodiments can be combined in any way to form a corresponding implementable technical solution.

[0038] Unless otherwise defined, the technical terms used in this document have the same meanings as those generally understood by those skilled in the art to which this application belongs; the use of relevant terms in this document is only for describing specific embodiments and is not intended to limit this application.

[0039] In the description of this application, the term "and / or" is an expression used to describe the logical relationship between objects, indicating that three relationships may exist, for example, A and / or B, which means: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this article generally indicates that the objects before and after are in an "or" logical relationship.

[0040] In the present application, terms such as “first” and “second” are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship of quantity, priority or sequence between these entities or operations.

[0041] Without further limitations, in this application, the words "include", "comprises", "has" or other similar expressions used in sentences are intended to cover non-exclusive inclusion. These expressions do not exclude the presence of additional elements in the process, method or product including the elements, so that the process, method or product including a series of elements may include not only those limited elements, but also other elements not explicitly listed, or also include elements inherent to such process, method or product.

[0042] Similar to the understanding in the Examination Guidelines, in this application, expressions such as "greater than", "less than", "exceed" and the like are understood to exclude the number itself; expressions such as "above", "below", "within" and the like are understood to include the number itself. In addition, in the description of the embodiments of this application, "multiple" means more than two (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups", "multiple times", etc., unless otherwise clearly and specifically limited.

[0043] like Figure 1 As shown, in a first aspect, the present invention provides a method for detecting a malicious digital signature, the method comprising the following steps:

[0044] First, enter step S101 to receive signature data uploaded by the user; the signature data includes a signature feature identifier;

[0045] Then, the process proceeds to step S102 to determine whether the interpretation information corresponding to the signature data is stored in the current database according to the signature feature identifier;

[0046] If the determination result of step S102 is yes, the process proceeds to step S103 to return the explanation information corresponding to the signature data to the user terminal.

[0047] In this embodiment, the signature data is digital currency signature data, which is a set of hash strings calculated based on smart contract functions and user data during digital currency transaction applications, preferably a 16-bit hash value. The signature feature identifier is a mark that distinguishes different types of hash values. The server can determine the type of signature data uploaded by the current user by parsing the specific number of bits of the hash value.

[0048] In this embodiment, the database is a database set in the server and can be used to store information corresponding to each signature data. The interpretation information refers to the functional interpretation corresponding to the signature data. For example, a pop-up window can be displayed to the user end to prompt "this signature data is used for xxx function" so that the user end can clearly know the purpose of the signature data before authorizing the signature data to a third party, thereby avoiding the loss of user assets due to malicious signatures. The functional uses of signature data include authorization, transfer, locking, etc.

[0049] Through the above solution, each time the user needs to send the signature data to a third party, he can upload the signature data to the server first. After obtaining the signature data uploaded by the user, the server will retrieve the interpretation information corresponding to the signature data and send it to the user. The user can clearly know the purpose of the current signature data by interpreting the returned interpretation information, thereby effectively preventing the loss of assets due to malicious signatures without knowing it.

[0050] like Figure 2 As shown, the database is obtained according to the following method:

[0051] First, enter step S201 to capture multiple smart contract functions on the blockchain and perform signature calculations to obtain signature data corresponding to each smart contract function;

[0052] Then proceed to step S202 to add explanatory information to the signature data corresponding to each smart contract function, and store the explanatory information and the signature data corresponding to each smart contract function in the database.

[0053] In this embodiment, a smart contract refers to a computer program running on a replicable and shared ledger, which has the functions of processing, receiving, storing and sending information. A smart contract function refers to a function program that implements the smart contract function. In actual application, multiple smart contract functions on the blockchain can be captured and analyzed by automated tools, and explanatory information of the signature data corresponding to each smart contract function can be added accordingly. The explanatory information can be used to explain the functions and uses of each smart contract function, thereby completing the establishment of the initial database.

[0054] In some embodiments, the database includes a function signature information table and a function interpretation information table, wherein the function signature information table is used to store the signature data corresponding to each smart contract function, and the function interpretation information table is used to store the interpretation information corresponding to each signature data.

[0055] Preferably, the database further includes an unknown signature information table, and the unknown signature information table is used to store unknown signature data, and the unknown signature data is signature data for which corresponding interpretation information has not yet been stored in the current function interpretation information table.

[0056] By capturing and analyzing multiple smart contract functions on the blockchain, the signature data after adding the explanation information can be stored in the function signature information table, and the explanation information of each item stored (added to the function signature information table) can be stored in the function explanation information table. One explanation information in the function explanation information table corresponds to one signature data in the function signature information table. In this way, when the signature data uploaded by the user end received by the service end is consistent with any signature data in the function signature information table (that is, the two have the same signature feature identifier), the explanation information corresponding to the signature data uploaded by the user end can be retrieved from the function explanation information table and returned to the user end.

[0057] On the contrary, if Figure 4As shown, if the current database does not store the interpretation information corresponding to the signature data, the process can proceed to step S401 to return the risk warning information to the user end. After receiving the risk warning information, the user end can know that the signature data currently prepared for authorization to the third party has not been stored in the database and needs to be confirmed again before authorization is granted, thereby effectively preventing the occurrence of erroneous authorization due to the user not knowing the function of the current signature data.

[0058] Subsequent processing of signature data that has not been stored in the database, such as Figure 3 As shown, the method also includes:

[0059] First, enter step S301, when it is determined that the interpretation information corresponding to the signature data is not stored in the current database, add mark information to the unknown signature data and store it in the unknown signature information table;

[0060] Then, step S302 is entered to periodically poll and detect whether new marking information appears in the unknown signature information table. If so, the unknown signature data corresponding to the marking information is retrieved and sent to the processing terminal for processing.

[0061] Furthermore, the method also includes: receiving interpretation information of the unknown signature data from the processing terminal, adding the interpretation information of the unknown signature data to a function interpretation information table, and adding the processed unknown signature data to the function signature information table.

[0062] In short, the signature data that has not been stored will be marked first and then stored in the unknown signature information table. The server has a corresponding process to monitor the unknown signature information table. Once unknown signature data with new marking information is found to be entered, it will be sent to the processing terminal for processing in a timely manner. The processing terminal can be a handheld terminal of the backend R&D personnel. The R&D personnel can add explanation information to some unknown signature data through the processing terminal, so that the corresponding explanation information can be returned to the user terminal in a timely manner when the same type of signature data is received next time.

[0063] In a second aspect, the present invention further provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed, the method described in the first aspect of the present invention is implemented.

[0064] In the third aspect, Figure 7 As shown, the present invention also provides a server 10 (such as the server described above), including a storage medium 102 and a processor 101, the storage medium 102 is the storage medium as described in the second aspect; the processor 101 is electrically connected to the storage medium 102, and is used to execute the computer program stored in the storage medium to implement the method described in the first aspect.

[0065] In the fourth aspect, Figure 8 As shown, the present invention also provides a system for detecting malicious digital signatures, including a server 10 and a user terminal 20, wherein the server 10 is the server as described in the third aspect of the present invention; the user terminal 20 is communicatively connected with the server 10, and is used to upload signature data to the server 10 and receive feedback results from the server 10.

[0066] Preferably, the server 10 and the client 20 can be both electronic devices, and the electronic devices can be computer devices, including but not limited to: personal computers, servers, general-purpose computers, special-purpose computers, network devices, embedded devices, programmable devices, smart mobile terminals, smart home devices, wearable smart devices, vehicle-mounted smart devices, etc. Storage media include but are not limited to: RAM, ROM, disks, tapes, optical disks, flash memory, USB flash drives, mobile hard disks, memory cards, memory sticks, network server storage, network cloud storage, etc. Processors include but are not limited to CPU (central processing unit), GPU (graphics processing unit), MCU (microprocessor), etc.

[0067] like Figure 5 As shown, in some application scenarios, the method for detecting malicious digital signatures involved in the present invention includes: the user terminal initiates a signature data parsing request to the server, and after the server's API interface receives the request, the request is forwarded to the server's data storage service thread for processing, and the data storage service thread accesses the database according to the signature feature identifier, and determines whether the database stores the function description corresponding to the signature data, and if so, returns the function description to the user terminal. The database in the server can be obtained through the collection and filtering service thread, which is specifically generated by analyzing the various contract function signatures on the blockchain.

[0068] like Figure 6 As shown, when the polling detection thread on the server finds that there is unknown signature data in the database, it will call the unknown signature data to the analysis thread on the server. The analysis thread analyzes the function signature data to be processed and receives feedback results from other processing terminals (the feedback results include explanation information). Then, the data query entry thread on the server enters the feedback results into the database so that the next time a similar request from the user end is received, the corresponding explanation information can be obtained from the database in a timely manner for the user end.

[0069] The present invention can detect the content of blockchain digital currency signatures, identify various risky signature contents, and return detailed functional descriptions, including the purpose of the signature, possible risks, etc. to the user. Through the method designed by the present invention, users do not need to master complex function signature recognition, but only need to upload the signature data to be detected, so as to effectively detect the digital currency signature, know the purpose of the signature data, and avoid malicious signatures due to misoperation.

[0070] Although the above embodiments have been described, once those skilled in the art know the basic creative concepts, they can make additional changes and modifications to these embodiments. Therefore, the above are only embodiments of the present invention and do not limit the patent protection scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the specification and drawings of the present invention, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for detecting malicious digital signatures, characterized in that: The method comprises the following steps: Receive signature data uploaded by the user; the signature data includes a signature feature identifier, which is a mark for distinguishing different types of hash values, and determines the type of the signature data uploaded by the current user by parsing a specific number of bits of the hash value; Determine whether the interpretation information corresponding to the signature data is stored in the current database according to the signature feature identifier, and if so, return the interpretation information corresponding to the signature data to the user terminal, wherein the interpretation information includes the function interpretation corresponding to the signature data; The database is obtained according to the following method: Capture multiple smart contract functions on the blockchain and perform signature calculations to obtain signature data corresponding to each smart contract function; Add explanatory information to the signature data corresponding to each smart contract function, and store the explanatory information and the signature data corresponding to each smart contract function in the database; The database includes a function signature information table and a function interpretation information table, wherein the function signature information table is used to store signature data corresponding to each of the smart contract functions, and the function interpretation information table is used to store interpretation information corresponding to each signature data; The database further includes an unknown signature information table, wherein the unknown signature information table is used to store unknown signature data, wherein the unknown signature data is signature data for which corresponding interpretation information has not been stored in the current function interpretation information table; The method further comprises: When it is determined that the interpretation information corresponding to the signature data is not stored in the current database, adding marking information to the unknown signature data and storing it in the unknown signature information table; Periodic polling is performed to detect whether new tag information appears in the unknown signature information table. If so, the unknown signature data corresponding to the tag information is retrieved and sent to the processing terminal for processing.

2. The method for detecting malicious digital signatures according to claim 1, characterized in that: The method further comprises: The receiving and processing terminal interprets the unknown signature data, adds the interpretative information of the unknown signature data to a function interpretation information table, and adds the processed unknown signature data to the function signature information table.

3. The method for detecting malicious digital signatures according to claim 1 or 2, characterized in that: The method further comprises: When it is determined that the interpretation information corresponding to the signature data is not stored in the current database, risk warning information is returned to the user terminal.

4. A storage medium, characterized in that: The storage medium stores a computer program, which implements the method according to any one of claims 1 to 3 when executed.

5. A server, characterized in that: include: The storage medium is the storage medium as claimed in claim 4; A processor, electrically connected to the storage medium, and configured to execute a computer program stored in the storage medium to implement the method according to any one of claims 1 to 3.

6. A system for detecting malicious digital signatures, characterized in that: include: The server is the server according to claim 5; The client terminal is connected to the server for communication and is used to upload the signature data to the server and receive feedback results from the server.

Images