Information processing method, device, equipment, and storage medium
By judging whether the malicious process is started on the electronic device and reboot is prohibited, the infinite loop restart problem caused by the malicious process is solved, and the system stability and user experience are improved.
Patent Information
- Application Number
- CN202010513190.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-06-08
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-06-08
AI Technical Summary
Under the system intercepted and restart mechanism of electronic devices, malicious processes may cause infinite loop restarts, causing inconvenience to users.
By obtaining interception events at the user layer, we can determine whether the current malicious process is the first interception, obtain the permission identification and time in the cache file, determine whether the malicious process is a self-start process, and prohibit restarting when it is determined to be self-start to avoid unlimited cycle.
It effectively avoids unlimited restarts caused by malicious applications starting up and improves system stability and user experience.
Smart Images

Figure CN111783090B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to electronic technology, and relate to but are not limited to an information processing method and apparatus, equipment, and storage medium. Background Art
[0002] The system security issues of electronic devices are being paid attention to by more and more manufacturers and users. At present, most electronic devices have mechanisms to intercept and process malicious processes. Among them, some electronic devices will automatically restart the electronic device after detecting a malicious process to prevent the malicious process from operating and avoid returning malicious results, so as to achieve the purpose of restoring the system. However, there are certain risks in this way. For example, if a malicious application is given the permission to start up automatically, under the security mechanism of "restart after interception", an extremely unfriendly situation will occur. That is, when the system of the electronic device intercepts the malicious process that starts up automatically, it will restart the electronic device. When the electronic device is restarted, the malicious process will start up again, and will be intercepted by the electronic device after starting up, resulting in an infinite loop. The electronic device will be unusable, which will cause a very bad experience for the user.
[0003] Therefore, how to prevent the malicious process that starts automatically at startup from causing an infinite loop restart of the electronic device under the "restart after interception" security mechanism has become an urgent problem to be solved by technical personnel in this field. Summary of the invention
[0004] Embodiments of the present application provide an information processing method, apparatus, device, and storage medium.
[0005] The technical solution of the embodiment of the present application is implemented as follows:
[0006] In a first aspect, an embodiment of the present application provides an information processing method, the method comprising:
[0007] If an interception event is obtained at the user layer, determining whether the current malicious process in the interception event is the first interception of a malicious process;
[0008] If it is not the first time to intercept a malicious process, then the first permission identifier and the first time are obtained from the cache file through the file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store the interception data when the system intercepted the malicious process last time;
[0009] Obtaining the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process;
[0010] Determine whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0011] If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0012] In the embodiment of the present application, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time includes:
[0013] Determine an interception interval according to the first time and the second time;
[0014] Determine the boot time according to the acquired startup time of the central processing unit and the second time;
[0015] If the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, it is determined that the current malicious process is a malicious process that is automatically started at boot.
[0016] In the embodiment of the present application, determining whether the current malicious process is a malicious process that starts automatically at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time also includes:
[0017] When any of the following conditions exists, it is determined that the current malicious process is a malicious process that is not started automatically at boot:
[0018] If the permission identifier of the current malicious process is different from the first permission identifier;
[0019] The interception interval is greater than the first preset time;
[0020] The power-on time is greater than the second preset time.
[0021] In the embodiment of the present application, the method further includes:
[0022] If it is determined that the current malicious process is a malicious process that is automatically started at startup, then the value of the flag bit is set to the first value;
[0023] If it is determined that the current malicious process is a malicious process that is not automatically started at boot time, then the value of the flag bit is set to the second value.
[0024] In the embodiment of the present application, the method further includes:
[0025] If the flag bit is the first value, inter-process communication is prohibited from sending a pop-up command.
[0026] In the embodiment of the present application, the method further includes:
[0027] If the flag bit is the second value, the current malicious process is checked and killed;
[0028] Determining the content of the pop-up box of the pop-up box command according to the permission identifier of the current malicious process;
[0029] The pop-up box command corresponding to the pop-up box content is sent through inter-process communication.
[0030] In the embodiment of the present application, determining whether the current malicious process in the interception event is the first interception of the malicious process includes:
[0031] If the cache file exists, it is determined that this is not the first time that a malicious process is intercepted;
[0032] If the cache file does not exist, it is determined that the malicious process is intercepted for the first time.
[0033] In the embodiment of the present application, the method further includes:
[0034] If it is the first time to intercept a malicious process, saving the permission identifier of the current malicious process and the second time into the cache file;
[0035] The current malicious process is checked and killed, and the electronic device is restarted.
[0036] In the embodiment of the present application, after determining whether the current malicious process is a malicious process that is automatically started at startup, the method further includes:
[0037] Deleting the first permission identifier and the first time in the cache file;
[0038] The permission identification of the current malicious process and the second time are saved in the cache file.
[0039] In the embodiment of the present application, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time includes:
[0040] Convert the data types of the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time into integer types;
[0041] According to the first permission identifier after the data type is converted, the permission identifier of the current malicious process, the first time and the second time, it is determined whether the current malicious process is a malicious process that is automatically started at startup.
[0042] In a second aspect, an embodiment of the present application provides an information processing device, the device comprising:
[0043] A first determining unit is used to determine whether the current malicious process in the interception event is the first interception of the malicious process if an interception event is obtained at the user layer;
[0044] A first data acquisition unit is used to acquire a first permission identifier and a first time from a cache file through a file acquisition interface if it is not the first time to intercept a malicious process; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0045] A second data acquisition unit, used to acquire the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process;
[0046] A second determining unit, configured to determine whether the current malicious process is a malicious process that is automatically started upon startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0047] The processing unit is used to detect and kill the current malicious process if the current malicious process is a malicious process that starts automatically when the computer is turned on, and to prohibit the electronic device from restarting.
[0048] In a third aspect, an embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can be executed on the processor, and when the processor executes the program, the steps in the above-mentioned information processing method are implemented.
[0049] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above-mentioned information processing method when executed by a processor.
[0050] The embodiment of the present application provides an information processing method and apparatus, device, and storage medium. If an interception event is obtained at the user layer, it is determined whether the current malicious process in the interception event is the first time that the malicious process is intercepted; if it is not the first time that the malicious process is intercepted, then a first permission identifier and a first time are obtained from a cache file through a file acquisition interface; the first time is the time when the system intercepted the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system last intercepted a malicious process; the permission identifier and the second time of the current malicious process are obtained; the second time is the time when the system intercepted the current malicious process; according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time, it is determined whether the current malicious process is a malicious process that starts automatically at power-on; if the current malicious process is a malicious process that starts automatically at power-on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting. In this way, it is possible to avoid the malicious situation of infinite restart caused by the malicious application being granted the permission to start automatically at power-on. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] Figure 1 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 1 ;
[0052] Figure 2 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 2 ;
[0053] Figure 3 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 3 ;
[0054] Figure 4 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 4 ;
[0055] Figure 5 This is a schematic diagram of the structure of the information processing device according to an embodiment of the present application;
[0056] Figure 6 A hardware entity schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0057] The technical solution of the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0058] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0059] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.
[0060] It should be pointed out that the terms "first\second\third" involved in the embodiments of the present application are merely to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described here can be implemented in an order other than that illustrated or described here.
[0061] An embodiment of the present application provides an information processing method, which is applied to an electronic device. The functions implemented by the method can be implemented by calling a program code by a processor in the electronic device. Of course, the program code can be stored in a storage medium of the electronic device. Figure 1 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 1 ,like Figure 1 As shown, the method includes:
[0062] Step S101: if an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0063] Here, before step S101, it has been determined that the current process intercepted by the system is a malicious process, and the purpose of step S101 is to determine whether this interception event is the first interception operation. In other words, even if the malicious process intercepted last time and the current malicious process are different malicious processes, as long as the last interception event exists, the system is not intercepting for the first time.
[0064] Step S102: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0065] Here, the first permission identifier is the permission identifier of the malicious process intercepted by the system last time, the first time is the time when the system intercepted the malicious process last time, and the second time is the time when the system intercepted the current malicious process. In some embodiments, if the system intercepts a malicious process for the first time, the permission identifier of the current malicious process and the second time are saved in the cache file. In addition, based on the "restart after interception" security mechanism, the electronic device can be restarted after the current malicious process is detected and killed.
[0066] Here, the electronic device may be various types of devices with information processing capabilities, such as mobile phones, PDAs (Personal Digital Assistants), navigators, digital phones, video phones, smart watches, smart bracelets, wearable devices, tablet computers, all-in-one computers, etc. During the implementation process, the server may be an electronic device, such as a mobile phone, a tablet computer, a laptop computer, a fixed terminal such as a personal computer and a server cluster, and other computing devices with information processing capabilities.
[0067] Step S103, obtaining the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process;
[0068] Step S104, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0069] Step S105: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0070] Here, the malicious process is divided into two types: one is a non-boot-start malicious process, that is, it will not start with the boot or restart of the electronic device. The other is a boot-start malicious process, that is, when the electronic device is turned on or restarted, the malicious process will also automatically start.
[0071] In an embodiment of the present application, if an interception event is obtained at the user layer, it is determined whether the current malicious process in the interception event is the first time that a malicious process is intercepted; if it is not the first time that a malicious process is intercepted, a first permission identifier and a first time are obtained from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system last intercepted a malicious process; the permission identifier and the second time of the current malicious process are obtained; the second time is the time when the system intercepted the current malicious process; based on the first permission identifier, the permission identifier of the current malicious process, the first time and the second time, it is determined whether the current malicious process is a malicious process that starts automatically at power-on; if the current malicious process is a malicious process that starts automatically at power-on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting. In this way, it is possible to avoid the malicious situation of infinite restart if the malicious application is granted the permission to start automatically at power-on.
[0072] Based on the above embodiments, the present application further provides an information processing method. Figure 2 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 2 ,like Figure 2 As shown, the method includes:
[0073] Step S201: If an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0074] Step S202: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0075] In some embodiments, the determining whether the current malicious process in the interception event is the first interception of the malicious process can be implemented in the following manner:
[0076] Step S21a: If the cache file exists, it is determined that this is not the first time that a malicious process is intercepted;
[0077] Step S22a: If the cache file does not exist, it is determined that the malicious process is intercepted for the first time.
[0078] In some embodiments, the method further comprises:
[0079] Step S21b: if it is the first time to intercept a malicious process, save the permission identifier of the current malicious process and the second time into the cache file;
[0080] Step S22b, check and kill the current malicious process, and restart the electronic device.
[0081] Step S203, obtaining the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process;
[0082] Step S204: determining an interception interval according to the first time and the second time;
[0083] Step S205, determining the boot time according to the acquired startup time of the central processing unit and the second time;
[0084] Step S206: If the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, determine that the current malicious process is a malicious process that is automatically started at boot;
[0085] Here, if the boot time is less than or equal to the second preset time, it is considered to be within the fixed boot time, and the user has no time to operate the electronic device. If the boot time is greater than the second preset time, it is considered to exceed the fixed boot time, and the user has enough time to operate the electronic device, for example, the user can uninstall the application corresponding to the malicious process, or the user can directly reinstall the system of the electronic device.
[0086] In some embodiments, the method further comprises:
[0087] Step S21c, deleting the first permission identifier and the first time in the cache file;
[0088] Step S22c, saving the permission identifier of the current malicious process and the second time into the cache file.
[0089] Here, after determining whether the current malicious process is a malicious process that is automatically started at startup, the existing data in the cache file can be deleted, and the interception data of the current malicious process can be saved in the cache file. In this way, the cache file stores the last interception data at any time.
[0090] Step S207: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0091] Here, if the current malicious process is a malicious process that starts automatically when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting. In this way, the user can uninstall the application corresponding to the malicious process that starts automatically when the computer is powered on, or reinstall the system, etc. In the embodiment of the present application, the malicious process data intercepted last time and the current malicious process data can be converted into integers and then compared.
[0092] In an embodiment of the present application, if an interception event is obtained at the user layer, it is determined whether the current malicious process in the interception event is the first time to intercept the malicious process; if it is not the first time to intercept the malicious process, then the first permission identifier and the first time are obtained from the cache file through the file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store the interception data when the system intercepted the malicious process last time; the permission identifier and the second time of the current malicious process are obtained; the second time is the time when the system intercepted the current malicious process; according to the first time and the second time, the interception interval time is determined; according to the obtained startup time of the central processing unit and the second time, the boot time is determined; if the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval time is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, it is determined that the current malicious process is a malicious process that starts automatically at boot; if the current malicious process is a malicious process that starts automatically at boot, the current malicious process is checked and killed, and the electronic device is prohibited from restarting, so that if the malicious application is given the permission to start automatically at boot, it can avoid the malicious situation of infinite restart.
[0093] Based on the above embodiments, the present application further provides an information processing method, the method comprising:
[0094] Step S211: If an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0095] Step S212: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0096] In some embodiments, if the cache file exists, it is determined that this is not the first time that the system intercepts a malicious process; if the cache file does not exist, it is determined that this is the first time that the system intercepts a malicious process.
[0097] Of course, it is also possible to determine whether the system is intercepting a malicious process for the first time based on whether there is interception data in the cache file. To this end, those skilled in the art can use different methods to determine whether the system is intercepting a malicious process for the first time based on actual needs.
[0098] Step S213, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0099] Step S214: determining an interception interval according to the first time and the second time;
[0100] Step S215, determining the boot time according to the acquired startup time of the central processing unit and the second time;
[0101] Step S216: When any of the following conditions exists, determine that the current malicious process is a malicious process that is not started automatically at boot:
[0102] If the permission identifier of the current malicious process is different from the first permission identifier;
[0103] The interception interval is greater than the first preset time;
[0104] The power-on time is greater than the second preset time;
[0105] Here, if the permission identifier of the current malicious process is different from the first permission identifier, then the current malicious process is considered to be a malicious process that is not automatically started at boot. If the interception interval is greater than the first preset time, then the current malicious process is considered to be a malicious process that is not automatically started at boot. If the boot time is greater than the second preset time, then the current malicious process is considered to be a malicious process that is not automatically started at boot.
[0106] Step S217: if the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, determine that the current malicious process is a malicious process that is automatically started at boot;
[0107] Step S218: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0108] Here, after determining that the intercepted current malicious process is a malicious process that starts automatically at boot, the electronic device will be prohibited from restarting. In this way, it can avoid the situation where the electronic device is restarted infinitely due to the malicious process that starts automatically at boot under the "restart after interception" security mechanism.
[0109] It should be noted that if the electronic device is an Android operating system, the above steps S211 to S218 are all completed at the native layer, that is, the local framework layer.
[0110] Based on the above embodiments, the present application further provides an information processing method. Figure 3 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 3 ,like Figure 3 As shown, the method includes:
[0111] Step S301: if an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0112] In some embodiments, the determining whether the current malicious process in the interception event is the first interception of the malicious process can be implemented in the following manner:
[0113] Step S31a: If the cache file exists, it is determined that this is not the first time that a malicious process is intercepted;
[0114] Step S32a: If the cache file does not exist, it is determined that the malicious process is intercepted for the first time.
[0115] Step S302: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0116] In some embodiments, the method further comprises:
[0117] Step S31b: if it is the first time to intercept a malicious process, save the permission identifier of the current malicious process and the second time into the cache file;
[0118] Step S32b, check and kill the current malicious process, and restart the electronic device.
[0119] Step S303, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0120] Step S304: determining an interception interval according to the first time and the second time;
[0121] Step S305, determining the boot time according to the acquired startup time of the central processing unit and the second time;
[0122] Here, after step S305, step S306 or step S307 is executed.
[0123] Step S306: If the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, determine that the current malicious process is a malicious process that is automatically started at boot;
[0124] Here, step S308 is executed after step S306.
[0125] In some embodiments, the method further comprises:
[0126] Step S31c, deleting the first permission identifier and the first time in the cache file;
[0127] Step S32c, saving the permission identifier of the current malicious process and the second time into the cache file.
[0128] Step S307: Determine that the current malicious process is a non-boot-started malicious process when any of the following conditions exists: if the permission identifier of the current malicious process is different from the first permission identifier; the interception interval is greater than the first preset time; the boot time is greater than the second preset time;
[0129] Here, step S311 is performed after step S307.
[0130] In some embodiments, the permission identifier, the second time, the first permission representation and the first time of the current malicious process may all be converted into data types and converted into integer types for comparison.
[0131] Step S308: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting;
[0132] Step S309: If it is determined that the current malicious process is a malicious process that is automatically started at startup, then the value of the flag bit is set to the first value;
[0133] Here, after determining whether the current malicious process is a malicious process that is automatically started at boot time, subsequent processing can be performed by setting a flag bit.
[0134] Step S310: If the flag bit is the first value, prohibiting inter-process communication from sending a pop-up command;
[0135] Here, if the flag bit is the first value, it means that the current malicious process is a malicious process that is automatically started at startup, so inter-process communication is prohibited from sending a pop-up command (for example, inter-process communication is prohibited from sending a pop-up command with the content of "the device will automatically restart after a certain period of time"), and the electronic device is prohibited from restarting. Therefore, the user can uninstall the application corresponding to the current self-starting malicious process by himself, or the user can also reinstall the system of the electronic device by himself.
[0136] Step S311: if it is determined that the current malicious process is a malicious process that is not started automatically at startup, then the value of the flag bit is set to a second value;
[0137] Step S312: If the flag bit is the second value, the current malicious process is checked and killed;
[0138] Step S313: determining the pop-up box content of the pop-up box command according to the permission identifier of the current malicious process;
[0139] Step S314: sending a pop-up box command corresponding to the pop-up box content through inter-process communication.
[0140] For example, the value of the permission identifier of the current malicious process can be used to determine whether the current malicious process belongs to a system application or a third-party application. If it belongs to a system application, a pop-up box command can be sent to inform the user that the electronic device will restart after a certain period of time. If it belongs to a third-party application, a pop-up box command can be sent to let the user choose whether to restart the electronic device.
[0141] In an embodiment of the present application, if an interception event is obtained at the user layer, it is determined whether the current malicious process in the interception event is the first time that a malicious process is intercepted; if it is not the first time that a malicious process is intercepted, then a first permission identifier and a first time are obtained from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system last intercepted a malicious process; the permission identifier and the second time of the current malicious process are obtained; the second time is the time when the system intercepted the current malicious process; the interception interval time is determined according to the first time and the second time; the boot time is determined according to the obtained startup time of the central processing unit and the second time; when any of the following exists, it is determined that the current malicious process is a malicious process that is not self-started at boot: if the permission identifier of the current malicious process is different from the first permission identifier; the interception interval time is greater than the first preset time; the boot time is greater than the second preset time; if the current malicious process If the permission identifier of the malicious process is the same as the first permission identifier, and the interception interval time is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, it is determined that the current malicious process is a malicious process that starts automatically at boot; if the current malicious process is a malicious process that starts automatically at boot, the current malicious process is checked and killed, and the electronic device is prohibited from restarting; if the current malicious process is determined to be a malicious process that starts automatically at boot, the value of the flag bit is set to the first value; if the current malicious process is determined to be a malicious process that does not start automatically at boot, the value of the flag bit is set to the second value; if the flag bit is the first value, inter-process communication to send a pop-up command is prohibited; if the flag bit is the second value, the current malicious process is checked and killed; according to the permission identifier of the current malicious process, the pop-up content of the pop-up command is determined; and the pop-up command corresponding to the pop-up content is sent through inter-process communication. In this way, it is possible to avoid the malicious situation of infinite restart if the malicious application is granted the permission to start automatically at boot.
[0142] Based on the above embodiments, the present application further provides an information processing method, the method comprising:
[0143] Step S311: if an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first interception of a malicious process;
[0144] Step S312: If the cache file exists, it is determined that this is not the first time that a malicious process is intercepted;
[0145] Step S313: If the cache file does not exist, it is determined that the malicious process is intercepted for the first time;
[0146] Step S314: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0147] Step S315, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0148] Step S316: determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0149] Step S317: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0150] Based on the above embodiments, the present application further provides an information processing method, the method comprising:
[0151] Step S321: If an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0152] Step S322: if it is the first time to intercept a malicious process, save the permission identifier of the current malicious process and the second time into the cache file;
[0153] Step S323: Check and kill the current malicious process, and restart the electronic device.
[0154] Step S324: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0155] Step S325, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0156] Step S326, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0157] Step S327: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0158] Based on the above embodiments, the present application further provides an information processing method, the method comprising:
[0159] Step S331: If an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0160] Step S332: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0161] Step S333, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0162] Step S334, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0163] Step S335, deleting the first permission identifier and the first time in the cache file;
[0164] Step S336: Save the permission identifier of the current malicious process and the second time into the cache file.
[0165] Step S337: If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0166] Based on the above embodiments, the present application further provides an information processing method, the method comprising:
[0167] Step S341: If an interception event is obtained at the user layer, determine whether the current malicious process in the interception event is the first time to intercept a malicious process;
[0168] Step S342: if it is not the first time to intercept a malicious process, then obtain a first permission identifier and a first time from a cache file through a file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time;
[0169] Step S343, obtaining the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0170] Step S344: convert the data types of the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time into integer types;
[0171] Step S345, determining whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier after the data type is converted, the permission identifier of the current malicious process, the first time, and the second time;
[0172] Step S346: If the current malicious process is a malicious process that is automatically started when the computer is turned on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting.
[0173] Based on the above embodiments, the present application further provides an information processing method. Figure 4 The following is a schematic diagram of the implementation process of the information processing method of the present application embodiment. Figure 4 ,like Figure 4 As shown, the method includes:
[0174] Step S401: When a malicious process is intercepted, check whether a cache file exists;
[0175] Here, the cache file may be a tmp.txt file. Of course, the file type of the cache file may be set according to actual needs. For example, the type of the cache file may also be a .tmp file or a .temp file.
[0176] In other embodiments, the cache file or the data in the cache file may be encrypted and stored, that is, encrypted with a fixed key when writing, and decrypted with the fixed key after reading.
[0177] If the cache file does not exist, execute step S402; if the cache file exists, execute step S403.
[0178] Step S402: Create the cache file, and record the UID (User Identification) of the intercepted malicious process and the time when the malicious process was intercepted into the created cache file;
[0179] Here, if the cache file does not exist, it means that the malicious process is intercepted for the first time.
[0180] In an embodiment of the present application, the UID of the malicious process can be passed in by the kernel. After detecting that the current process is a malicious process, the UID of the current process will be passed to the upper layer. The UID is the permission identifier of the process.
[0181] In an embodiment of the present application, the time of the intercepted malicious process can be obtained in a variety of ways. For example, the time period information between 00:00:00 on January 1, 1970 and the time point when the malicious process is currently intercepted can be obtained through the time() interface, and the time period information can be used as the time when the malicious process is intercepted.
[0182] Step S403, obtaining the UID and time of the malicious process recorded in the cache file during the last interception;
[0183] Here, the first two lines of data in the cache file can be obtained through the fget() interface (the first two lines of the cache file record the UID of the malicious process intercepted during the last interception and the last interception time). In addition, the data obtained by the fget() interface can be forcibly converted into an integer type for comparison with the interception data this time.
[0184] Step S404, determining the boot time according to the acquired CPU (Central Processing Unit) startup time and the time when the malicious process is currently intercepted;
[0185] Here, the CPU startup time can be obtained through the clock_gettime() interface.
[0186] Step S405: Determine the interception interval time according to the time when the malicious process is currently intercepted and the time recorded in the cache file when the malicious process was last intercepted;
[0187] Step S406, determining whether the currently intercepted malicious process is a malicious process that is automatically started upon startup;
[0188] Step S407: If the UID of the currently intercepted malicious process is the same as the UID of the malicious process recorded during the last interception, and the boot time is less than the first preset time, and the interception interval is less than the second preset time, it is determined that the currently intercepted malicious process is a malicious process that is automatically started at boot;
[0189] If it is determined that the currently intercepted malicious process is a malicious process that is automatically started when the computer is turned on, step S409 is executed.
[0190] Here, the first preset time and the second preset time may be the same or different.
[0191] Here, if the UID is the same, it means that the permission changes for two consecutive privilege escalations are the same. If the boot time is less than the first preset time, it means that it is within the fixed boot time. If the interception interval is less than the second preset time, it means that the privilege is frequently elevated. Therefore, if all three judgment conditions in step S407 are met, it is considered that the malicious process currently intercepted is a malicious process that is automatically started at boot.
[0192] For example, if the UID of the currently intercepted malicious process is the same as the UID of the last intercepted malicious process, and the current boot time is less than 5 minutes, and the interval between the two interceptions is less than 5 minutes, then the currently intercepted malicious process is considered to be a malicious process that is automatically started at boot (i.e., the self-starting item frequently elevates privileges).
[0193] Of course, if it is determined that the currently intercepted malicious process is a malicious process that starts automatically when the computer is powered on, a flag bit flag=1 can be set, and correspondingly, if it is determined that the currently intercepted malicious process is a malicious process that does not start automatically when the computer is powered on, the flag bit can be set to flag=0. In this way, corresponding processing can be performed later according to the value of the identifier.
[0194] In some embodiments, while the performance is gradually optimized, the judgment threshold (i.e., the first preset time and the second preset time) can be gradually reduced to prevent malicious processes from using the time difference to perform malicious operations. For example, the first preset time can be changed from 5 minutes to 3 minutes.
[0195] Step S408: If the UID of the currently intercepted malicious process is different from the UID of the malicious process recorded in the last interception, or the boot time is greater than or equal to the first preset time, or the interception interval is greater than or equal to the second preset time, it is determined that the currently intercepted malicious process is a malicious process that is not automatically started at boot;
[0196] If it is determined that the currently intercepted malicious process is a malicious process that is not automatically started at boot time, step S410 is executed.
[0197] In some embodiments, if the judgment is completed, the last interception data in the cache file is deleted to ensure that the cache file only contains the last interception data, and the UID and time of the currently intercepted malicious process are written into the cache file.
[0198] Step S409: Do not send a pop-up command and prohibit the mobile phone from restarting;
[0199] Here, if the currently intercepted malicious process is a malicious process that is automatically started when the computer is turned on, the APP (Application) will no longer be notified through IPC (Inter-Process Communication) to pop up a window or force restart.
[0200] In some embodiments, if the malicious process currently intercepted is a malicious process that starts automatically at startup, forced restart of the electronic device is prohibited, and the user can be informed to uninstall the application corresponding to the malicious process that starts automatically at startup as soon as possible or reinstall the system of the electronic device.
[0201] Step S410: Send a pop-up command, and the user determines the subsequent operation.
[0202] Here, if the currently intercepted malicious process is not a malicious process that starts automatically when the computer is powered on, a pop-up box command can be sent through IPC, and different pop-up box contents can be selected according to the type of UID, and the user can determine the subsequent operations.
[0203] Here, if the malicious process currently intercepted is a malicious process that is not automatically started when the computer is turned on, it is judged as a normal interception. Furthermore, the size of the UID of the malicious process can be used to determine whether to restart the electronic device. For example, if the size of the UID is within a certain threshold range, the application corresponding to the malicious process is considered to be a system application, and a pop-up window is issued to remind the user that the electronic device will be restarted after a certain period of time. If the size of the UID is outside the certain threshold range, the application corresponding to the malicious process is considered to be a third-party application, and a pop-up window is issued to remind the user whether to restart the electronic device, and the electronic device is restarted or not according to the user's choice.
[0204] In some embodiments, a blacklist can be added to record the PID (Process ID) of the process that is determined to be malicious and self-starts to elevate privileges, and then returned to the R&D department for confirmation. Then, when installing the APK (Android Package) later, this blacklist is detected to prevent the malicious application from being installed again, or the malicious application is automatically uninstalled.
[0205] In the embodiment of the present application, through the operations in step S401 to step S410, the malicious situation of infinite restart caused by a malicious application being granted the power-on self-start permission is avoided.
[0206] In the prior art, if a system process is privileged, the malicious process will be intercepted first, then data will be reported, and finally a pop-up window will be displayed to prompt the user's phone to restart after a certain period of time. If a system is hijacked maliciously, it will automatically start and privilege will be elevated every time it is turned on, and it will be forced to restart indefinitely. However, through the information processing method in the embodiment of the present application, when such a situation occurs, the pop-up window and restart will be suspended, leaving the user time to operate (such as uninstalling, restoring to factory, etc.).
[0207] Based on the foregoing embodiments, the embodiments of the present application provide an information processing device, which includes the units included, the modules included in the units, and the components included in the modules, which can be implemented by a processor in an electronic device; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a CPU, MPU (Microprocessor Unit), DSP (Digital Signal Processing) or FPGA (Field Programmable Gate Array), etc.
[0208] Figure 5 Schematic diagram of the structure of the information processing device according to the embodiment of the present application. Figure 5 As shown, the device 500 includes:
[0209] The first determining unit 501 is used to determine whether the current malicious process in the interception event is the first interception of the malicious process if an interception event is obtained at the user layer;
[0210] The first data acquisition unit 502 is used to acquire a first permission identifier and a first time from a cache file through a file acquisition interface if it is not the first time to intercept a malicious process; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store the interception data when the system intercepted the malicious process last time;
[0211] The second data acquisition unit 503 is used to acquire the permission identifier of the current malicious process and the second time; the second time is the time when the system intercepts the current malicious process;
[0212] A second determining unit 504 is used to determine whether the current malicious process is a malicious process that starts automatically at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time;
[0213] The processing unit 505 is used to detect and kill the current malicious process if the current malicious process is a malicious process that starts automatically when the computer is turned on, and prohibit the electronic device from restarting.
[0214] In some embodiments, the second determining unit 504 includes:
[0215] A first determining module, configured to determine an interception interval time according to the first time and the second time;
[0216] The first determination module is further used to determine the boot time according to the acquired startup time of the central processing unit and the second time;
[0217] The second determination module is used to determine that the current malicious process is a malicious process that starts automatically at startup if the permission identifier of the current malicious process is the same as the first permission identifier, the interception interval is less than or equal to the first preset time, and the startup time is less than or equal to the second preset time.
[0218] In some embodiments, the second determining unit 504 further includes:
[0219] The third determination module is used to determine that the current malicious process is a malicious process that is not automatically started when the computer is powered on, when any of the following conditions exists:
[0220] If the permission identifier of the current malicious process is different from the first permission identifier;
[0221] The interception interval is greater than the first preset time;
[0222] The power-on time is greater than the second preset time.
[0223] In some embodiments, the apparatus further comprises:
[0224] A setting unit 506, configured to set the value of the flag bit to a first value if it is determined that the current malicious process is a malicious process that is automatically started at startup;
[0225] The setting unit 506 is further configured to set the value of the flag bit to a second value if it is determined that the current malicious process is a malicious process that is not automatically started upon startup.
[0226] In some embodiments, the apparatus further comprises:
[0227] The prompt prohibition unit 507 is used to prohibit the inter-process communication from sending a pop-up box command if the flag bit is the first value.
[0228] In some embodiments, the apparatus further comprises:
[0229] A detection and killing unit 508, configured to detect and kill the current malicious process if the flag bit is the second value;
[0230] A pop-up box determination unit 509 is used to determine the pop-up box content of the pop-up box command according to the permission identifier of the current malicious process;
[0231] The pop-up box sending unit 510 is used to send the pop-up box command corresponding to the pop-up box content through inter-process communication.
[0232] In some embodiments, the first determining unit 501 includes:
[0233] A fourth determination module, configured to determine that it is not the first time to intercept a malicious process if the cache file exists;
[0234] The fourth determination module is further configured to determine that the malicious process is intercepted for the first time if the cache file does not exist.
[0235] In some embodiments, the apparatus further comprises:
[0236] A saving unit 511 is used for saving the permission identifier of the current malicious process and the second time into the cache file if it is the first time to intercept the malicious process;
[0237] The restart unit 512 is used to detect and kill the current malicious process and restart the electronic device.
[0238] In some embodiments, the apparatus further comprises:
[0239] A deleting unit 513, used to delete the first authority identifier and the first time in the cache file;
[0240] The storage unit 514 is used to save the permission identifier and the second time of the current malicious process into the cache file.
[0241] In some embodiments, the second determining unit 504 includes:
[0242] A conversion module, used to convert the data types of the first permission identifier, the permission identifier of the current malicious process, the first time and the second time into integer types;
[0243] The execution module is used to determine whether the current malicious process is a malicious process that starts automatically at startup based on the first permission identifier after the data type is converted, the permission identifier of the current malicious process, the first time and the second time.
[0244] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.
[0245] It should be noted that in the embodiments of the present application, if the above-mentioned information processing method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for an electronic device (which can be a personal computer, server, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a ROM (Read Only Memory), a disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.
[0246] Correspondingly, an embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps in the information processing method provided in the above embodiment are implemented.
[0247] Correspondingly, an embodiment of the present application provides a readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above-mentioned information processing method are implemented.
[0248] It should be noted here that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.
[0249] It should be noted that Figure 6 A hardware entity diagram of an electronic device according to an embodiment of the present application is shown in FIG. Figure 6 As shown, the hardware entity of the electronic device 600 includes: a processor 601, a communication interface 602 and a memory 603, wherein
[0250] The processor 601 generally controls the overall operation of the electronic device 600 .
[0251] The communication interface 602 enables the electronic device 600 to communicate with other terminals or servers through a network.
[0252] The memory 603 is configured to store instructions and applications executable by the processor 601, and can also cache data to be processed or processed by the processor 601 and various modules in the electronic device 600 (for example, image data, audio data, voice communication data, and video communication data), which can be implemented through FLASH (flash memory) or RAM (Random Access Memory).
[0253] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.
[0254] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0255] In addition, all functional units in the embodiments of the present application can be integrated into one processing module, or each unit can be a separate unit, or two or more units can be integrated into one unit; the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units. A person of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium, which, when executed, executes the steps of the above method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, disks or optical disks.
[0256] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain a new method embodiment. The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain a new product embodiment. The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain a new method embodiment or device embodiment.
[0257] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. An information processing method, characterized in that: The method comprises: If an interception event is obtained at the user layer, determining whether the current malicious process in the interception event is the first interception of a malicious process; If it is not the first time to intercept a malicious process, then the first permission identifier and the first time are obtained from the cache file through the file acquisition interface; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store the interception data when the system intercepted the malicious process last time; Obtaining the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process; Determine whether the current malicious process is a malicious process that is automatically started at startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time; If the current malicious process is a malicious process that is automatically started when the computer is powered on, the current malicious process is checked and killed, and the electronic device is prohibited from restarting; The determining, according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time, whether the current malicious process is a malicious process that is automatically started upon startup includes: Determine an interception interval according to the first time and the second time; Determine the boot time according to the acquired startup time of the central processing unit and the second time; If the permission identifier of the current malicious process is the same as the first permission identifier, and the interception interval is less than or equal to the first preset time, and the boot time is less than or equal to the second preset time, it is determined that the current malicious process is a malicious process that is automatically started at boot.
2. The method according to claim 1, characterized in that The determining, according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time, whether the current malicious process is a malicious process that starts automatically upon startup also includes: When any of the following conditions exists, it is determined that the current malicious process is a malicious process that is not started automatically at boot: If the permission identifier of the current malicious process is different from the first permission identifier; The interception interval is greater than the first preset time; The power-on time is greater than the second preset time.
3. The method according to claim 2, characterized in that The method further comprises: If it is determined that the current malicious process is a malicious process that is automatically started at startup, then the value of the flag bit is set to the first value; If it is determined that the current malicious process is a malicious process that is not automatically started at boot time, then the value of the flag bit is set to the second value.
4. The method according to claim 3, characterized in that The method further comprises: If the flag bit is the first value, inter-process communication is prohibited from sending a pop-up command.
5. The method according to claim 3, characterized in that: The method further comprises: If the flag bit is the second value, the current malicious process is checked and killed; Determining the content of the pop-up box of the pop-up box command according to the permission identifier of the current malicious process; The pop-up box command corresponding to the pop-up box content is sent through inter-process communication.
6. The method according to any one of claims 1 to 5, characterized in that: The determining whether the current malicious process in the interception event is the first interception of the malicious process includes: If the cache file exists, it is determined that this is not the first time that a malicious process is intercepted; If the cache file does not exist, it is determined that the malicious process is intercepted for the first time.
7. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: If it is the first time to intercept a malicious process, saving the permission identifier of the current malicious process and the second time into the cache file; The current malicious process is checked and killed, and the electronic device is restarted.
8. The method according to any one of claims 1 to 5, characterized in that: After determining whether the current malicious process is a malicious process that is automatically started at startup, the method further includes: Deleting the first permission identifier and the first time in the cache file; The permission identification of the current malicious process and the second time are saved in the cache file.
9. The method according to any one of claims 1 to 5, characterized in that: The determining, according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time, whether the current malicious process is a malicious process that is automatically started upon startup includes: Convert the data types of the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time into integer types; According to the first permission identifier after the data type is converted, the permission identifier of the current malicious process, the first time and the second time, it is determined whether the current malicious process is a malicious process that is automatically started at startup.
10. An information processing device, characterized in that: The device comprises: A first determining unit is used to determine whether the current malicious process in the interception event is the first interception of the malicious process if an interception event is obtained at the user layer; A first data acquisition unit is used to acquire a first permission identifier and a first time from a cache file through a file acquisition interface if it is not the first time to intercept a malicious process; the first time is the time when the system intercepts the malicious process corresponding to the first permission identifier; the cache file is used to store interception data when the system intercepted the malicious process last time; A second data acquisition unit, used to acquire the permission identifier of the current malicious process and a second time; the second time is the time when the system intercepts the current malicious process; A second determining unit, configured to determine whether the current malicious process is a malicious process that is automatically started upon startup according to the first permission identifier, the permission identifier of the current malicious process, the first time, and the second time; A processing unit, configured to detect and kill the current malicious process if the current malicious process is a malicious process that is automatically started upon startup, and prohibit the electronic device from restarting; The second determining unit includes: A first determining module, configured to determine an interception interval time according to the first time and the second time; The first determination module is further used to determine the boot time according to the acquired startup time of the central processing unit and the second time; The second determination module is used to determine that the current malicious process is a malicious process that starts automatically at startup if the permission identifier of the current malicious process is the same as the first permission identifier, the interception interval is less than or equal to the first preset time, and the startup time is less than or equal to the second preset time.
11. An electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps of the information processing method according to any one of claims 1 to 9 are implemented.
12. A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the information processing method according to any one of claims 1 to 9 are implemented.
Citation Information
Patent Citations
Malicious program cleaning method and device for windows
CN110674504A
