IP Library Granted Patent US 11,157,621
Granted Patent B1
US 11,157,621 · App. 16/211,787 · Granted Oct 26, 2021

Systems and methods to detect and prevent auto-click attacks

Inventors: Sharad Mhaske (Maharashtra, IN); Shrikant Pawar (Mumbai, IN)
Assignee: NortonLifeLock Inc.
G06F21/566G06F3/0488G06F21/554G06F2221/034
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,157,621
App. No.
16/211,787
Granted
Oct 26, 2021
Kind
B1
Abstract

The disclosed computer-implemented method for detecting and preventing auto-click attacks may include (1) detecting, by the computing device, a click input, (2) detecting, by the computing device, a finger in proximity to the computing device, (3) analyzing, by the computing device, at least one event associated with the finger, (4) determining, by the computing device, that the click input is an auto-click based on the analysis of the at least one event associated with the finger, and (5) performing a security action in response to determining that the click input is an auto-click. Various other methods, systems, and computer-readable media are also disclosed.

Claims (51)

1. A computer-implemented method for detecting and preventing auto-click attacks, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

detecting, by the computing device, a finger in proximity to a screen of the computing device;

receiving, by the computing device, a hover input representative of the finger being positioned over but not touching the screen of the computing device;

subsequent to receiving the hover input, detecting, by the computing device, a click input;

analyzing, by the computing device, the received hover input in relation to the detected click input;

determining, by the computing device, that the click input is an auto-click based on the analysis of the relationship between the received hover input and the detected click input; and

performing a security action in response to determining that the click input is an auto-click.

2. The computer-implemented method of claim 1 , wherein analyzing, by the computing device, the received hover input in relation to the detected click input comprises identifying a temporal parameter associated with the hover input.

3. The computer-implemented method of claim 1 , wherein determining, by the computing device, that the click input is an auto-click comprises:

determining, by the computing device, that the hover input was not received within a threshold time period before the detected click input.

4. The computer-implemented method of claim 1 , wherein analyzing, by the computing device, the received hover input in relation to the detected click input comprises identifying a spatial parameter associated with the hover input.

5. The computer-implemented method of claim 1 , wherein determining, by the computing device, that the click input is an auto-click comprises:

determining, by the computing device, that the hover input is representative of the finger not being positioned over the screen of the computing device within a threshold distance from the detected click input.

6. The computer-implemented method of claim 1 , wherein the screen is a touchscreen.

7. The computer-implemented method of claim 6 , further comprising:

adding a transparent overlay on the touchscreen, wherein receiving, by the computing device, the hover input, comprises receiving the hover input from the transparent overlay on the touchscreen.

8. The computer-implemented method of claim 1 , wherein performing the security action comprises performing, on the computing device, at least one of:

a blocking of an attempted auto-click;

a terminating of a program associated with the auto-click; and

a providing of a notification message to a user of the computing device.

9. A system for detecting and preventing auto-click attacks, the system comprising:

at least one physical processor; and

physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to:

detect, by a computing device, a finger in proximity to a screen of the computing device;

receive, by the computing device, a hover input representative of the finger being positioned over but not touching the screen of the computing device;

subsequent to receiving the hover input, detect, by the computing device, a click input;

analyze, by the computing device, the received hover input in relation to the detected click input;

determine, by the computing device, that the click input is an auto-click based on the analysis of the relationship between the received hover input and the detected click input; and

perform a security action in response to determining that the click input is an auto-click.

10. The system of claim 9 , wherein analyzing, by the computing device, the received hover input in relation to the detected click input comprises identifying a temporal parameter associated with the hover input.

11. The system of claim 9 , wherein determining, by the computing device, that the click input is an auto-click comprises:

determining, by the computing device, that the hover input was not received within a threshold time period before the detected click input.

12. The system of claim 9 , wherein analyzing, by the computing device, the received hover input in relation to the detected click input comprises identifying a spatial parameter associated with the hover input.

13. The system of claim 9 , wherein determining, by the computing device, that the click input is an auto-click comprises:

determining, by the computing device, that the hover input is representative of the finger not being positioned over the screen of the computing device within a threshold distance from the detected click input.

14. The system of claim 9 , wherein the screen is a touchscreen.

15. The system of claim 14 , further comprising:

adding a transparent overlay on the touchscreen, wherein receiving, by the computing device, the hover input, comprises receiving the hover input from the transparent overlay on the touchscreen.

16. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

detect a finger in proximity to a screen of the computing device;

receive a hover input representative of the finger being positioned over but not touching the screen of the computing device;

subsequent to receiving the hover input, detect a click input;

analyze the received hover input in relation to the detected click input;

determine that the click input is an auto-click based on the analysis of the relationship between the received hover input and the detected click input; and

perform a security action in response to determining that the click input is an auto-click.

17. The non-transitory computer-readable medium of claim 16 , wherein analyzing the received hover input in relation to the detected click input comprises identifying a temporal parameter associated with the hover input.

18. The non-transitory computer-readable medium of claim 16 , wherein determining that the click input is an auto-click based comprises:

determining that the hover input was not received within a threshold time period before the detected click input.

19. The non-transitory computer-readable medium of claim 16 , wherein analyzing the received hover input in relation to the detected click input comprises identifying a spatial parameter associated with the hover input.

20. The non-transitory computer-readable medium of claim 16 , wherein determining that the click input is an auto-click comprises:

determining that the hover input is representative of the finger not being positioned over the screen of the computing device within a threshold distance from the detected click input.

Assignments (6)
CHANGE OF NAME Recorded Feb 6, 2023
From: NORTONLIFELOCK INC.
To: GEN DIGITAL INC.
Reel/Frame 062714/0605 →
NOTICE OF SUCCESSION OF AGENCY (REEL 050926 / FRAME 0560) Recorded Sep 13, 2022
From: JPMORGAN CHASE BANK, N.A.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 061422/0371 →
SECURITY AGREEMENT Recorded Sep 13, 2022
From: NORTONLIFELOCK INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 062220/0001 →
CHANGE OF NAME Recorded Feb 14, 2020
From: SYMANTEC CORPORATION
To: NORTONLIFELOCK INC.
Reel/Frame 051935/0228 →
SECURITY AGREEMENT Recorded Nov 4, 2019
From: SYMANTEC CORPORATION; BLUE COAT LLC; LIFELOCK, INC,; SYMANTEC OPERATING CORPORATION
To: JPMORGAN, N.A.
Reel/Frame 050926/0560 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 6, 2018
From: MHASKE, SHARAD; PAWAR, SHRIKANT
To: SYMANTEC CORPORATION
Reel/Frame 047694/0038 →