Mitigation of malicious actions associated with graphical user interface elements

1. A computer implemented method for mitigating malicious actions associated with graphical user interface elements, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising the steps of:

monitoring, by the computing device, a user interface element in a graphical user interface environment of an application executing on the computing device;

identifying, by the computing device, an association between the user interface element and a malicious action, based on determining a temporal proximity between a user interaction with the user interface element and an occurrence of the malicious action, wherein determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action comprises repeatedly determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action to establish a confidence level above a threshold; and

blocking, by the computing device, access to the user interface element to prevent the malicious action from executing, while allowing the application and the graphical user interface environment to continue executing on the computing device.

2. The method of claim 1 , wherein identifying the association between the user interface element and the malicious action comprising querying, by the computing device, a malware database with a property of the user interface element.

3. The method of claim 1 , wherein the association between the user interface element and the malicious action is identified based on a crowd sourced reputation of one or more properties of the user interface element.

4. The method of claim 1 further comprising:

identifying, by the computing device, the user interaction with the user interface element;

identifying, by the computing device, the malicious action executed on the computing device; and

responsive to identifying the association between the user interface element and the malicious action, inserting, by the computing device, into a malware database a property of the user interface element and a property of the associated action executed on the computing device.

5. The method of claim 4 , wherein the property of the user interface element is at least one of: an automation identifier, a process identifier, and a spatial identifier.

6. The method of claim 5 , wherein the process identifier is at least one of: an image file size, an executable file name, a memory footprint, and a computer resource consumption fingerprint.

7. The method of claim 1 , further comprising:

determining, by the computing device, that the user interface element is whitelisted or signed; and

allowing, by the computing device, access to the user interface element.

8. The method of claim 1 , wherein blocking access to the user interface element comprises at least one of: inserting a hook, producing a popup message, disabling use of a human-computer interface, and overlaying a window.

9. The method of claim 1 , wherein the monitoring, the identifying, and the blocking are performed using the Windows application programming interface in the Microsoft Windows operating system.

10. A computer system for mitigating malicious actions associated with graphical user interface elements, the computer system comprising:

system memory;

a user interface monitor component residing in the system memory, the user interface monitor component being programmed to monitor a user interface element in a graphical user interface environment of an application executing on the computer system;

a malware identifier component residing in the system memory, the malware identifier component being programmed to identify an association between the user interface element and a malicious action, based on determining a temporal proximity between a user interaction with the user interface element and an occurrence of the malicious action, wherein determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action comprises repeatedly determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action to establish a confidence level above a threshold;

a user interface blocker component residing in the system memory, the user interface blocker component being programmed to block access to the user interface element to prevent the malicious action from executing, while allowing the application and the graphical user interface environment to continue executing on the computing device; and

at least one processor configured to execute the components.

11. The computer system of claim 10 , wherein identifying the association between the user interface element and the malicious action comprising querying a malware database with a property of the user interface element.

12. The computer system of claim 10 , wherein the association between the user interface element and the malicious action is identified based on a crowd sourced reputation of one or more properties of the user interface element.

13. The computer system of claim 10 further comprising:

a fingerprint component residing in the system memory, the fingerprint component being programmed to: identify the user interaction with the user interface element, and identify the malicious action executed on the computer system; and

wherein the malware identifier component is further programmed to responsive to identifying the association between the user interface element and the malicious action, insert into a malware database a property of the user interface element and a property of the associated action executed on the computer system.

14. The computer system of claim 13 , wherein the property of the user interface element is at least one of: an automation identifier, a process identifier, and a spatial identifier.

15. The computer system of claim 14 , wherein the process identifier is at least one of: an image file size, an executable file name, a memory footprint, and a computer resource consumption fingerprint.

16. The computer system of claim 10 , further comprising a trust component residing in the system memory, the trust component being programmed to determine that the user interface element is whitelisted or signed, and allow access to the user interface element.

17. The computer system of claim 10 , wherein blocking access to the user interface element comprises at least one of: inserting a hook, producing a popup message, disabling use of a human-computer interface, and overlaying a window.

18. The computer system of claim 10 , wherein the monitoring, the identifying, and the blocking are performed using the Windows application programming interface in the Microsoft Windows operating system.

19. At least one non-transitory computer readable-storage medium for mitigating malicious actions associated with graphical user interface elements, the at least one non-transitory computer readable-storage medium storing computer executable instructions that, when loaded into computer memory and executed by at least one processor of a computing device, cause the computing device to:

monitor, by the computing device, a user interface element in a graphical user interface environment of an application executing on the computing device;

identify, by the computing device, an association between the user interface element and a malicious action, based on determining a temporal proximity between a user interaction with the user interface element and an occurrence of the malicious action, wherein determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action comprises repeatedly determining the temporal proximity between the user interaction with the user interface element and the occurrence of the malicious action to establish a confidence level above a threshold; and

block, by the computing device, access to the user interface element to prevent the malicious action from executing, while allowing the application and the graphical user interface environment to continue executing on the computing device.

20. The non-transitory computer readable-storage medium of claim 19 , wherein identifying the association between the user interface element and the malicious action comprising querying, by the computing device, a malware database with a property of the user interface element.