CN108650645B - Method and related device for preventing malicious fee deduction - Google Patents

Abstract

The invention discloses a method for preventing malicious deduction, comprising: receiving first verification information input for an identity verification interface on a terminal; when the first user identifier corresponding to the first verification information is determined to be a restricted user, Detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; and preventing the malicious deduction operation if there is a malicious deduction operation corresponding to the first user identifier on the terminal. Correspondingly, the present invention also provides a device for preventing malicious deduction. By adopting the present invention, malicious deduction triggered by limited users can be prevented, and the function of the terminal can be enhanced.

Description

A method and related device for preventing malicious deduction

technical field

The present invention relates to the field of electronic technology, and in particular, to a method and related device for preventing malicious deduction.

Background technique

At present, many entertainment applications on terminal devices (such as mobile games, novel software or video software, etc.) need to be consumed to achieve a certain purpose. Taking mobile games as an example, such as resurrecting the protagonist, purchasing game equipment, etc. generally require Consumption can only be achieved; and these consumption methods are: prompting the user and realizing it by sending a deduction SMS; or, without any prompt, deducting the fee directly. Therefore, when children play with terminal devices such as mobile phones or tablet computers, it is easy to cause unintentional deductions, resulting in economic losses for parents.

The prior art is: first intercept the unauthorized application, and prompt the operator, and continue to execute the unauthorized application after the operator manually confirms. , they may not know what the result of sending such a text message will be, and may choose to continue execution in order to play the game, resulting in no actual blocking effect.

SUMMARY OF THE INVENTION

The present invention provides a method and device for preventing malicious deduction, which can prevent malicious deduction triggered by limited users and enhance the function of the terminal.

The present invention provides a method for preventing malicious deduction, including:

receiving the first verification information input for the identity verification interface on the terminal;

When the first user identifier corresponding to the first verification information is determined to be a restricted user, detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal;

If there is a malicious deduction operation corresponding to the first user identifier on the terminal, the malicious deduction operation is prevented.

Correspondingly, the present invention also provides a device for preventing malicious deduction, including:

a verification information receiving module, configured to receive the first verification information input for the identity verification interface on the terminal;

a user identification module for judging whether the first user identification corresponding to the first verification information is a restricted user;

a deduction behavior detection module, configured to detect whether there is a malicious deduction operation corresponding to the first user identification on the terminal when the first user identification corresponding to the first verification information is determined to be a restricted user;

The control module is configured to prevent the malicious deduction operation if there is a malicious deduction operation corresponding to the first user identifier on the terminal.

Implement the present invention, have the following beneficial effects:

When the first user identifier corresponding to the first verification information is determined to be a restricted user, the present invention can detect whether there is a malicious deduction operation corresponding to the first user identifier on the terminal, and if so, prevent the malicious deduction. It can prevent malicious deductions triggered by limited users, enhance the functions of the terminal, and avoid unnecessary economic losses.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings used in the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic flowchart of a method for preventing malicious fee deduction provided by an embodiment of the present invention;

2 is a schematic flowchart of another method for preventing malicious deduction provided by an embodiment of the present invention;

3 is a schematic flowchart of another method for preventing malicious deduction provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of an apparatus for preventing malicious deduction of fees according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for preventing malicious deduction provided by an embodiment of the present invention; the method for preventing malicious deduction provided by an embodiment of the present invention can be implemented in a terminal device such as a mobile phone, a PAD, or a notebook computer. Above, as shown in FIG. 1, the method for preventing malicious deduction in this embodiment may include:

Step S101, receiving the first verification information input for the identity verification interface on the terminal;

The first verification information may be information such as fingerprints, sliding tracks, numbers or faces;

The terminal may display the identity verification interface when the system is initialized; the terminal may also provide buttons or icons for user switching, and display the identity verification interface whenever the buttons or icons trigger user switching.

Step S102, when the first user identifier corresponding to the first verification information is determined to be a restricted user, detect whether there is a malicious deduction operation corresponding to the first user identifier on the terminal;

Specifically, when the terminal receives the first verification information input for the identity verification interface on the terminal, the terminal can determine whether the first user identifier corresponding to the first verification information is a restricted user.

Optionally, the terminal may acquire the verification information of the user through collection, set a corresponding user ID for each verification information, and then set a user category for the user ID, and the user category may be a restricted user or an unrestricted user; or, The terminal can download the user identification list of the restricted user from the network side, where the user identification list of the restricted user includes the user identification of the restricted user and the corresponding verification information;

The terminal determining whether the first user identifier corresponding to the first verification information is a restricted user may specifically include: acquiring the first user identifier corresponding to the first verification information, and detecting the first user identifier corresponding to the first verification information Whether it is included in the pre-stored list of user identifiers of restricted users, and if so, it is determined that the first user identifier corresponding to the first verification information is a restricted user.

When the first user identifier corresponding to the first verification information is determined to be a limited user, it is detected whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; specifically, the terminal may detect the Whether there is outgoing data corresponding to the first user ID on the terminal, such as outgoing text messages, outgoing call requests, outgoing purchase requests, etc. If so, obtain the application corresponding to the data sent program, and determine whether the application program is a restricted application, if so, obtain the transmission parameters of the data sent, and detect whether the transmission parameters are qualified, if the transmission parameters are unqualified, the transmission parameters are key characters For example, detecting whether the key character is qualified, if not, it is determined that the sending parameter is not qualified, and it is determined that there is a malicious deduction operation corresponding to the first user identifier on the terminal;

Optionally, the terminal determining whether the application is a restricted application may specifically be: the terminal detects whether the application is included in the restricted application list, and if the application is included in the restricted application list, then determine that the application is a restricted application;

The restricted application list may be determined according to the settings of the unrestricted user, for example, the unrestricted user selects some/some applications on the terminal as restricted applications, thereby generating the restricted application list; or, the restricted application list may be It is downloaded by the terminal from the network side; or, the restricted application list can be determined according to the settings of the unrestricted user and the download from the network side. It is assumed that the restricted applications set by the unrestricted user include A, B, and C, and the restricted application list downloaded by the terminal The restricted applications in the restricted application list include B, C, and D, and the restricted applications in the restricted application list determined according to the settings of the unrestricted user and the network-side download include A, B, C, and D.

The malicious deduction operation includes at least one of dialing a non-contact number, sending a deduction SMS, sending an in-app purchase request, or malicious traffic consumption;

When the terminal initiates a call request, it is determined that there is data sent out on the terminal, and it is further detected whether the application program executing the call request is a restricted application. If so, it is further detected whether the called terminal is included in the contact list. , indicating that the terminal is dialing a non-contact number, then it is determined that there is a malicious deduction operation on the terminal;

When the terminal sends a short message, it is determined that there is data to be sent out on the terminal, and it is further detected whether the application program that executes the sending of the short message is a restricted application, and if so, it is further detected whether the sending number of the short message is an SP (ServiceProvider, service provider). , is the access number of the direct provider of the mobile Internet service content application service) service, if so, it is determined that there is a malicious deduction operation on the terminal;

When the terminal sends an application request, it is determined that there is data sent out on the terminal, and it is further detected whether the application is a restricted application. If so, it is further detected whether the application request contains payment-related key characters. There is a malicious deduction operation on the above-mentioned terminal;

If the terminal consumes traffic, it is determined that there is data sent out on the terminal, and further detects whether the application consuming the traffic is a restricted application, if so, further detects whether the traffic is normal, and if not, determines whether the terminal There is a malicious deduction operation on the website.

Step S103, if there is a malicious deduction operation corresponding to the first user identifier on the terminal, prevent the malicious deduction operation;

When the malicious deduction operation is to dial a non-contact number, the preventing the malicious deduction operation may specifically be: refusing to initiate a call request corresponding to the first user identifier;

When the malicious deduction operation is the sending of the deduction short message, the preventing the malicious deduction operation may specifically be: refusing to send the deduction short message corresponding to the first user identifier;

When the malicious deduction operation is the sending of the in-app purchase request, the preventing the malicious deduction operation may specifically be: refusing to send the in-app purchase request.

When the malicious deduction operation is the malicious traffic consumption, the preventing the malicious deduction operation may specifically be: searching for an application program corresponding to the malicious traffic consumption, and restricting the Internet access authority of the application program.

In the embodiment shown in FIG. 1, when the first user identifier corresponding to the first verification information is determined to be a restricted user, it can be detected whether there is a malicious deduction operation corresponding to the first user identifier on the terminal, If so, the malicious deduction operation is prevented, thereby preventing malicious deduction triggered by limited users, avoiding unnecessary economic losses, enhancing the functions of the terminal, and further improving user experience.

Please refer to FIG. 2. FIG. 2 is a schematic flowchart of another method for preventing malicious deduction provided by an embodiment of the present invention; the method for preventing malicious deduction provided by an embodiment of the present invention can be implemented in a terminal such as a mobile phone, a PAD, or a notebook computer. On the device, as shown in FIG. 2 , the method for preventing malicious deduction in this embodiment may include:

Step S201, receiving the first verification information input for the identity verification interface on the terminal;

Step S202, judging whether the first user identifier corresponding to the first verification information is a restricted user; if the first user identifier corresponding to the first verification information is a restricted user, perform step 204; otherwise, Go to step 203;

Step S203, enter the unrestricted mode;

Step S204, detecting whether there is a malicious deduction operation corresponding to the first user ID on the terminal; if there is a malicious deduction operation corresponding to the first user ID on the terminal, perform step S205; otherwise , execute step S204;

Step S205, obtaining the recorded number of malicious deductions corresponding to the first user ID;

Step S206, judging whether the number of malicious deductions is less than the preset malicious deduction threshold corresponding to the first user ID; if the malicious deduction is less than the preset malicious deduction threshold, execute Step S207; if the number of malicious deductions is equal to the preset threshold for the number of malicious deductions, perform step S210;

Step S207, obtaining the number of deduction amounts of the malicious deduction operation;

Step S208, judging whether the number of the deduction amount is less than or equal to the preset malicious deduction amount threshold; if the deduction amount is less than or equal to the preset malicious deduction amount threshold, then go to step S209, otherwise go to step S209 S210;

Wherein, before receiving the first verification information input for the identity verification interface on the terminal, the terminal may first receive the second verification information input for the identity verification interface on the terminal, in the second verification information corresponding to the second verification information When the user ID is determined to be an unrestricted user, receive a setting instruction for the threshold of the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user ID, and extract the input malicious deduction corresponding to the first user ID. The threshold for the number of charges and the threshold for the number of malicious deductions are saved.

Further, if the amount of deduction is less than or equal to the preset malicious deduction threshold, the terminal may also obtain the amount of deduction for the malicious deduction operation, and generate authorization request information to obtain the second user. Identify the corresponding communication address, and send the authorization request information to the communication address, the second user ID is the authorized user of the first user ID, if the returned user ID corresponds to the second user ID If the authorization confirmation response is received, step S209 is performed; otherwise, step S210 is performed;

It should be noted that, in this embodiment of the present invention, the terminal first determines whether the number of malicious deductions is less than the preset threshold for the number of malicious deductions corresponding to the first user ID, and if not, the terminal further determines the deduction amount. Whether the number is less than or equal to the preset malicious deduction amount threshold, in other optional embodiments, may first determine whether the deduction amount is less than or equal to the preset malicious deduction amount threshold. If not, it is further judged whether the number of malicious deductions is less than the preset threshold of malicious deductions corresponding to the first user ID; or, it is only judged whether the malicious deductions are less than the first user ID The corresponding preset number of malicious deduction thresholds; or, it is only determined whether the amount of deductions is less than or equal to the preset threshold of malicious deductions, which is not limited in the present invention.

Step S209, do not prevent the malicious deduction operation, and add one to the number of malicious deductions corresponding to the first user ID;

Step S210, preventing the malicious deduction operation.

In the embodiment shown in FIG. 2 , when it is detected that there is a malicious deduction operation corresponding to the first user ID on the terminal, it can be further determined whether the number of malicious deductions is less than that corresponding to the first user ID. The preset malicious deduction times threshold, if yes, further determine whether the deduction amount is less than or equal to the preset malicious deduction amount threshold, if the malicious deduction times are equal to the preset malicious deduction corresponding to the first user ID The malicious deduction operation is prevented only when the amount of deductions is greater than the preset amount of malicious deductions, so that the amount of malicious deductions can be controlled, and the function of the terminal is enhanced.

Please refer to FIG. 3, FIG. 3 is a schematic flowchart of another method for preventing malicious deduction provided by an embodiment of the present invention; the method for preventing malicious deduction provided by an embodiment of the present invention can be implemented in a terminal such as a mobile phone, a PAD, or a notebook computer. On the device, as shown in FIG. 3 , the method for preventing malicious deduction in this embodiment may include:

Step S301, receiving the first verification information input for the identity verification interface on the terminal;

Step S302, judging whether the first user identifier corresponding to the first verification information is a restricted user; if the first user identifier corresponding to the first verification information is a restricted user, perform step 304; otherwise, Go to step 303;

Step S303, enter the unrestricted mode;

Step S304, detecting whether there is a malicious deduction operation corresponding to the first user ID on the terminal; if there is a malicious deduction operation corresponding to the first user ID on the terminal, perform step S305; otherwise , execute step S304;

Step S305, obtaining the deduction amount of the malicious deduction operation, and generating authorization request information;

Step S306, obtaining a communication address corresponding to a second user identification, and sending the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification;

The communication address corresponding to the second user identifier may be a mobile phone number, email address, WeChat account or QQ number, etc. corresponding to the second user identifier; when generating authorization request information, the terminal may obtain the corresponding address of the second user identifier. A communication address is used, and the authorization request information is sent to the communication address. The communication address takes a mobile phone number as an example. The terminal can set the authorization request information as a short message and send it to the corresponding terminal through the mobile phone number.

Step S307, detecting whether the returned authorization confirmation response corresponding to the second user identifier is received; if the returned authorization confirmation response corresponding to the second user identifier is received, step S308 is performed; if no return is received the authorization confirmation response corresponding to the second user identity, then perform step S309;

Further, after the authorization request information is sent to the communication address, the returned charge deduction setting information corresponding to the second user identifier can also be received, and the charge deduction setting information includes the charge deduction setting information corresponding to the first user identifier. The corresponding malicious deduction times threshold and/or malicious deduction amount threshold, the terminal then extracts the deduction setting information corresponding to the first user ID and saves it, and the authorized user of the limited user can use the deduction setting information in real time. Setting the threshold for the number of malicious deductions and/or the threshold for the number of malicious deductions can reduce frequent interactions;

Step S308, the malicious deduction operation is not prevented.

Step S309, preventing the malicious deduction operation.

In the embodiment shown in FIG. 3 , when it is detected that there is a malicious deduction operation corresponding to the first user identifier on the terminal, further, the number of deduction amounts of the malicious deduction operation is obtained, and an authorization is generated. request information, and then send the authorization request information to the communication address corresponding to the second user ID, if the returned authorization confirmation response corresponding to the second user ID is received, the malicious deduction operation will not be prevented, otherwise , the malicious deduction operation is prevented, the parent can remotely control the malicious deduction behavior of the child, and the terminal function is enhanced.

Please refer to FIG. 4 . FIG. 4 is a schematic structural diagram of a device for preventing malicious deduction provided by an embodiment of the present invention; the device for preventing malicious deduction provided by an embodiment of the present invention can be implemented in a terminal such as a mobile phone, a PAD, or a notebook computer. In the device; as shown in FIG. 4, the device 4 for preventing malicious deduction in the embodiment of the present invention may at least include: a verification information receiving module 401, a user identification module 402, a deduction behavior detection module 403, and a control module 404, wherein:

A verification information receiving module 401, configured to receive the first verification information input for the identity verification interface on the terminal;

A user identification module 402, configured to determine whether the first user identification corresponding to the first verification information is a restricted user;

A charge deduction behavior detection module 403, configured to detect whether there is a malicious charge deduction operation corresponding to the first user identification on the terminal when the first user identification corresponding to the first verification information is determined to be a restricted user;

The control module 404 is configured to prevent the malicious deduction operation if there is a malicious deduction operation corresponding to the first user identifier on the terminal.

The processing module 404 can be specifically used for:

When the malicious deduction operation is to dial a non-contact number, refuse to initiate a call request corresponding to the first user identifier; or,

When the malicious charge deduction operation is the sending of the charge deduction short message, refuse to send the charge deduction short message corresponding to the first user identifier; or,

When the malicious deduction operation is the sending of the in-app purchase request, refuse to send the in-app purchase request; or,

When the malicious deduction operation is the malicious traffic consumption, an application program corresponding to the malicious traffic consumption is searched, and the Internet access authority of the application program is restricted.

In an optional implementation manner, the device 4 for preventing malicious deductions may further include a deduction times acquisition module 405 and a deduction times judgment module 406, wherein:

Deduction times obtaining module 405, configured to obtain the recorded malicious deduction times corresponding to the first user identifier;

Deduction times judgment module 406, configured to judge whether the malicious deduction times are less than the preset malicious deduction times threshold corresponding to the first user ID;

The control module 404 is also used to:

If the number of malicious deductions is less than the preset threshold for the number of malicious deductions, the malicious deduction operation is not prevented, and the number of malicious deductions corresponding to the first user ID is incremented by one.

Still further, if the malicious deduction times are less than the preset malicious deduction times threshold, the device 4 for preventing malicious deductions may further include a deduction amount acquisition module 407 and a deduction amount judgment module 408, wherein :

A deduction amount obtaining module 407, configured to obtain the number of deduction amounts of the malicious deduction operation;

The deduction amount judging module 408 is configured to determine whether the deduction amount is less than or equal to the preset malicious deduction amount threshold, if the deduction amount is less than or equal to the preset malicious deduction amount threshold, triggering The control module 404 performs the operation of not preventing the malicious deduction, and increments the number of malicious deductions corresponding to the first user ID by one.

Wherein, the verification information receiving module 401 is also used for:

receiving the second verification information input for the identity verification interface on the terminal;

The device for preventing malicious deduction may also include:

The setting module 409 is configured to, when the second user identifier corresponding to the second verification information is determined to be an unrestricted user, receive a threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user identifier. The instruction is set to extract and save the inputted threshold for the number of malicious deductions and the threshold for the amount of malicious deductions corresponding to the first user identifier.

The control module 404 can also be used to:

If the number of malicious deductions is less than the preset number of malicious deductions threshold, or, if the number of deductions is less than or equal to the preset number of malicious deductions threshold, execute the blocking of malicious deductions operate.

In another optional implementation manner, if there is a malicious deduction operation corresponding to the first user identifier on the terminal, the device for preventing malicious deduction may further include an authorization request information generating module 410, an authorization request information The sending module 411 and the response receiving module 412, wherein:

an authorization request information generation module 410, configured to obtain the number of deduction amounts of the malicious deduction operation, and generate authorization request information;

an authorization request information sending module 411, configured to obtain a communication address corresponding to a second user identification, and send the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification;

A response receiving module 412, configured to receive the returned authorization confirmation response corresponding to the second user identifier;

The processing module 404 can also be used to:

If the returned authorization confirmation response corresponding to the second user identifier is received, the malicious deduction operation is not prevented;

Otherwise, the malicious deduction operation is blocked.

Further, the response receiving module 412 can also be used for:

Receive the returned charge deduction setting information corresponding to the second user identifier, where the charge deduction setting information includes a malicious charge count threshold and/or a malicious charge amount threshold corresponding to the first user identifier;

The setting module 409 can also be used to:

The deduction setting information corresponding to the first user identifier is extracted and saved.

Optionally, the malicious charge deduction operation includes at least one of dialing a non-contact number, sending a charge deduction short message, sending an in-app purchase request, or malicious traffic consumption.

It is understandable that the functions of each functional module of the device 4 for preventing malicious deduction of fees in this embodiment can be specifically implemented according to the methods in the above method embodiments, which can be specifically corresponding to the relevant descriptions of the method embodiments with reference to FIGS. 1 to 3 , It will not be repeated here.

It should be noted that, in the foregoing embodiments, the description of each embodiment has its own emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present invention.

The steps in the method of the embodiment of the present invention may be adjusted, combined and deleted in sequence according to actual needs.

The modules or units in the apparatus of the embodiment of the present invention may be combined, divided, and deleted according to actual needs.

The modules or units in the embodiments of the present invention may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit, central processing unit), or an ASIC (Application Specific Integrated Circuit, an application-specific integrated circuit).

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium. During execution, the processes of the embodiments of the above-mentioned methods may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like.

The above disclosures are only preferred embodiments of the present invention, and of course, the scope of the rights of the present invention cannot be limited by this. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.

Claims (32)

1. a method for preventing malicious deduction, it is characterized in that, described method comprises: receiving the first verification information input for the identity verification interface on the terminal; When the first user identifier corresponding to the first verification information is determined to be a restricted user, detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; If there is a malicious deduction operation corresponding to the first user ID on the terminal, obtain the recorded number of malicious deductions corresponding to the first user ID; The preset malicious charge deduction times threshold corresponding to the first user identifier; if the malicious charge deduction times are less than the preset malicious charge deduction times threshold, the malicious charge deduction operation is not prevented. 2. The method of claim 1, wherein the method further comprises: If the malicious deduction operation is not prevented, the number of malicious deductions corresponding to the first user ID is incremented by one. 3. The method of any one of claims 1-2, wherein, The method also includes: If the number of malicious deductions is equal to the preset threshold for the number of malicious deductions, the malicious deduction operation is blocked. 4. The method of claim 1, wherein The malicious charge deduction operation includes at least one of dialing a non-contact number, sending a charge deduction short message, sending an in-app purchase request or malicious traffic consumption. 5. The method of claim 4, wherein The preventing the malicious deduction operation includes: When the malicious deduction operation is to dial a non-contact number, refuse to initiate a call request corresponding to the first user identifier; or, When the malicious charge deduction operation is the sending of the charge deduction short message, refuse to send the charge deduction short message corresponding to the first user identifier; or, When the malicious deduction operation is the sending of the in-app purchase request, refuse to send the in-app purchase request; or, When the malicious deduction operation is the malicious traffic consumption, an application program corresponding to the malicious traffic consumption is searched, and the Internet access authority of the application program is restricted. 6. A method for preventing malicious deduction, wherein the method comprises: receiving the first verification information input for the identity verification interface on the terminal; When the first user identifier corresponding to the first verification information is determined to be a restricted user, detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; If there is a malicious deduction operation corresponding to the first user identifier on the terminal, the method further includes: Obtain the number of deduction amounts of the malicious deduction operation, and generate authorization request information; obtaining a communication address corresponding to a second user identification, and sending the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification; If the returned authorization confirmation response corresponding to the second user identifier is received, the malicious deduction operation is not prevented; Otherwise, the malicious deduction operation is blocked. 7. The method according to claim 6, wherein after obtaining the communication address corresponding to the second user identifier and sending the authorization request information to the communication address, The method further includes: receiving returned charge deduction setting information corresponding to the second user identifier, where the charge deduction setting information includes a malicious charge count threshold and/or malicious charge deduction corresponding to the first user identifier. Amount threshold; The deduction setting information corresponding to the first user identifier is extracted and saved. 8. A method for preventing malicious deduction, wherein the method comprises: receiving the first verification information input for the identity verification interface on the terminal; When the first user identifier corresponding to the first verification information is determined to be a restricted user, detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; If there is a malicious deduction operation corresponding to the first user ID on the terminal, obtain the amount of deduction for the malicious deduction operation; determine whether the amount of deduction is less than or equal to the preset malicious deduction amount number threshold; If the amount of deduction is less than or equal to the preset amount of malicious deduction threshold, the malicious deduction operation is not prevented. 9. The method of claim 8, wherein the method further comprises: If the malicious deduction operation is not prevented, the number of malicious deductions corresponding to the first user ID is incremented by one. 10. The method according to claim 8, wherein before receiving the first verification information input for the identity verification interface on the terminal, the method further comprises: receiving the second verification information input for the identity verification interface on the terminal; When the second user identifier corresponding to the second verification information is determined to be an unrestricted user, receive an instruction for setting the threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user identifier, extract the inputted The threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user identifier are stored. 11. The method according to claim 9, wherein before receiving the first verification information input for the identity verification interface on the terminal, the method further comprises: receiving the second verification information input for the identity verification interface on the terminal; When the second user identifier corresponding to the second verification information is determined to be an unrestricted user, receive an instruction for setting the threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user identifier, extract the inputted The threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user identifier are stored. 12. The method of any one of claims 8-11, wherein The method also includes: If the amount of deduction is greater than the preset amount of malicious deduction threshold, the malicious deduction operation is prevented. 13. The method of claim 8, wherein The malicious charge deduction operation includes at least one of dialing a non-contact number, sending a charge deduction short message, sending an in-app purchase request or malicious traffic consumption. 14. The method of claim 13, wherein The preventing the malicious deduction operation includes: When the malicious deduction operation is to dial a non-contact number, refuse to initiate a call request corresponding to the first user identifier; or, When the malicious charge deduction operation is the sending of the charge deduction short message, refuse to send the charge deduction short message corresponding to the first user identifier; or, When the malicious deduction operation is the sending of the in-app purchase request, refuse to send the in-app purchase request; or, When the malicious deduction operation is the malicious traffic consumption, an application program corresponding to the malicious traffic consumption is searched, and the Internet access authority of the application program is restricted. 15. A method for preventing malicious deduction, wherein the method comprises: receiving the first verification information input for the identity verification interface on the terminal; When the first user identifier corresponding to the first verification information is determined to be a restricted user, detecting whether there is a malicious deduction operation corresponding to the first user identifier on the terminal; Wherein, if there is a malicious deduction operation corresponding to the first user identifier on the terminal, the method further includes: Obtain the number of deduction amounts of the malicious deduction operation, and generate authorization request information; obtaining a communication address corresponding to a second user identification, and sending the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification; If the returned authorization confirmation response corresponding to the second user identifier is received, the malicious deduction operation is not prevented; Otherwise, the malicious deduction operation is blocked. 16. The method according to claim 15, wherein after acquiring the communication address corresponding to the second user identifier and sending the authorization request information to the communication address, the method further comprises: Receive the returned charge deduction setting information corresponding to the second user identifier, where the charge deduction setting information includes a malicious charge count threshold and/or a malicious charge amount threshold corresponding to the first user identifier; The deduction setting information corresponding to the first user identifier is extracted and saved. 17. A device for preventing malicious deduction, wherein the device comprises: a verification information receiving module, configured to receive the first verification information input for the identity verification interface on the terminal; a user identification module for judging whether the first user identification corresponding to the first verification information is a restricted user; a deduction behavior detection module, configured to detect whether there is a malicious deduction operation corresponding to the first user identification on the terminal when the first user identification corresponding to the first verification information is determined to be a restricted user; an acquisition module for the number of deductions, configured to acquire the recorded number of malicious deductions corresponding to the first user identifier; Deduction times judgment module, configured to judge whether the malicious deduction times are less than the preset malicious deduction times threshold corresponding to the first user ID; A control module, configured to not prevent the malicious deduction if there is a malicious deduction operation corresponding to the first user identifier on the terminal, and the malicious deduction times are less than the preset malicious deduction times threshold deduction operation. 18. The apparatus of claim 17, wherein The control module is further configured to: if the number of malicious deductions is less than the preset threshold of malicious deductions, add one to the number of malicious deductions corresponding to the first user identifier. 19. The device of any one of claims 17-18, wherein The control module is further configured to prevent the malicious deduction operation if the malicious deduction times are equal to the preset malicious deduction times threshold. 20. The apparatus of claim 17, wherein the malicious charge deduction operation comprises at least one of dialing a non-contact number, sending a charge deduction short message, sending an in-app purchase request, or malicious traffic consumption. 21. The apparatus of claim 20, wherein The device further includes: a processing module; The processing module is specifically used for: When the malicious deduction operation is to dial a non-contact number, refuse to initiate a call request corresponding to the first user identifier; or, When the malicious charge deduction operation is the sending of the charge deduction short message, refuse to send the charge deduction short message corresponding to the first user identifier; or, When the malicious deduction operation is the sending of the in-app purchase request, refuse to send the in-app purchase request; or, When the malicious deduction operation is the malicious traffic consumption, an application program corresponding to the malicious traffic consumption is searched, and the Internet access authority of the application program is restricted. 22. A device for preventing malicious deduction, wherein the device comprises: a verification information receiving module, configured to receive the first verification information input for the identity verification interface on the terminal; a user identification module for judging whether the first user identification corresponding to the first verification information is a restricted user; a deduction behavior detection module, configured to detect whether there is a malicious deduction operation corresponding to the first user identification on the terminal when the first user identification corresponding to the first verification information is determined to be a restricted user; Wherein, if there is a malicious deduction operation corresponding to the first user identifier on the terminal, the device further includes: an authorization request information generation module, used to obtain the number of deduction amounts of the malicious deduction operation, and to generate authorization request information; an authorization request information sending module, configured to obtain a communication address corresponding to a second user identification, and send the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification; a response receiving module, configured to receive the returned authorization confirmation response corresponding to the second user identifier; The processing module is configured to not prevent the malicious deduction operation if the returned authorization confirmation response corresponding to the second user identifier is received; otherwise, prevent the malicious deduction operation. 23. The apparatus of claim 22, wherein the response receiving module is further configured to: Receive the returned charge deduction setting information corresponding to the second user identifier, where the charge deduction setting information includes a malicious charge count threshold and/or a malicious charge amount threshold corresponding to the first user identifier; The device further includes: a setting module, configured to extract and save the deduction setting information corresponding to the first user identifier. 24. A device for preventing malicious deduction, wherein the device comprises: a verification information receiving module, configured to receive the first verification information input for the identity verification interface on the terminal; a user identification module for judging whether the first user identification corresponding to the first verification information is a restricted user; a fee deduction behavior detection module, configured to detect whether there is a malicious deduction operation corresponding to the first user identifier on the terminal when the first user identifier corresponding to the first verification information is determined to be a restricted user; Wherein, if the number of malicious deductions is less than the preset threshold of malicious deductions, the device further includes: a deduction amount obtaining module, used to obtain the number of deduction amounts of the malicious deduction operation; a deduction amount judging module, configured to determine whether the deduction amount is less than or equal to a preset malicious deduction amount threshold; The control module is configured to not prevent the malicious deduction operation if the deduction amount is less than or equal to a preset malicious deduction amount threshold. 25. The apparatus of claim 24, wherein The control module is further configured to add one to the number of malicious deductions corresponding to the first user identifier if the number of deductions is less than or equal to a preset threshold for the number of malicious deductions. 26. The apparatus of claim 25, wherein The verification information receiving module is also used for: receiving the second verification information input for the identity verification interface on the terminal; The device also includes: A setting module, configured to receive the setting of the threshold for the number of malicious deductions and the threshold for the number of malicious deductions corresponding to the first user ID when the second user ID corresponding to the second verification information is determined to be an unrestricted user The instruction is to extract and save the inputted malicious deduction times threshold and malicious deduction amount threshold corresponding to the first user identifier. 27. The device of any one of claims 24-26, wherein The control module is further configured to prevent the malicious deduction operation if the deduction amount is greater than a preset malicious deduction amount threshold. 28. The apparatus of claim 24, wherein the malicious charge deduction operation comprises at least one of dialing a non-contact number, sending a charge deduction short message, sending an in-app purchase request, or malicious traffic consumption. 29. The apparatus of claim 28, wherein The device further includes: a processing module; The processing module is specifically used for: When the malicious deduction operation is to dial a non-contact number, refuse to initiate a call request corresponding to the first user identifier; or, When the malicious charge deduction operation is the sending of the charge deduction short message, refuse to send the charge deduction short message corresponding to the first user identifier; or, When the malicious deduction operation is the sending of the in-app purchase request, refuse to send the in-app purchase request; or, When the malicious deduction operation is the malicious traffic consumption, an application program corresponding to the malicious traffic consumption is searched, and the Internet access authority of the application program is restricted. 30. A device for preventing malicious deduction, wherein the device comprises: a verification information receiving module, configured to receive the first verification information input for the identity verification interface on the terminal; a user identification module for judging whether the first user identification corresponding to the first verification information is a restricted user; a deduction behavior detection module, configured to detect whether there is a malicious deduction operation corresponding to the first user identification on the terminal when the first user identification corresponding to the first verification information is determined to be a restricted user; Wherein, if there is a malicious deduction operation corresponding to the first user identifier on the terminal, the device further includes: an authorization request information generation module, used to obtain the number of deduction amounts of the malicious deduction operation, and to generate authorization request information; an authorization request information sending module, configured to obtain a communication address corresponding to a second user identification, and send the authorization request information to the communication address, where the second user identification is an authorized user of the first user identification; a response receiving module, configured to receive the returned authorization confirmation response corresponding to the second user identifier; The processing module is configured to not prevent the malicious deduction operation if the returned authorization confirmation response corresponding to the second user identifier is received; otherwise, prevent the malicious deduction operation. 31. The apparatus of claim 30, wherein the response receiving module is further configured to: Receive the returned charge deduction setting information corresponding to the second user identifier, where the charge deduction setting information includes a malicious charge count threshold and/or a malicious charge amount threshold corresponding to the first user identifier; The device further includes: a setting module, configured to extract and save the deduction setting information corresponding to the first user identifier. 32. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a program, wherein, when the program is executed by hardware, it is used to implement the method described in any one of claims 1 to 16. method described.

Images