Machine made input patterns
Clicks and keys sent by a tool tend to be too neat, too fast or oddly placed.
Input sent through the DevTools Protocol is trusted, so defenses look at how it behaves. Common tells are a click with no earlier mouse move, exact element center targets, whole number coordinates, identical gaps between keys, and zero hold time between key down and key up. Some tools also gave screen coordinates that matched page coordinates, which a real desktop rarely does.
What it can and can't do
What the user does: Nothing. Page script listens in the background
It can
- Record pointer paths and key timing
- Measure how neat the pattern is
- Flag teleporting clicks and exact centers
- Score the session as human or machine
It cannot
- Catch careful tools that add human noise
- Identify who runs the tool
- Read what you type beyond timing
- Work on pages with few interactions
How it differs between platforms: Agent tools now add random delays and curved paths, so the signal degrades over time. A person on a trackpad can also look unusually smooth.
Browser support
Version notes
- Chrome: Applies to any Chromium based browser
- Edge: Applies to Chromium Edge
- Firefox: Same patterns can be measured
- Safari: Same patterns can be measured
- Safari on iPhone: Touch patterns
- Chrome on Android: Touch patterns
- Samsung Internet: Touch patterns
How a site asks for it
| API | mousemove/pointermove/click timing; MouseEvent.clientX/screenX; KeyboardEvent timing; PointerEvent.getCoalescedEvents() |
| Browser compat keys | api.MouseEvent.screenXapi.PointerEvent.getCoalescedEvents |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Page records pointer and key events with timestamps
- Script measures paths, gaps and coordinate patterns
- Model scores how human the pattern looks
Data you get
Shape: object
How often: stream while the person interacts
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
pointerPath | list | px | positions with timestamps before each click | Not listed |
clickOffset | float | px | distance from the exact center of the target | Not listed |
keyHoldTime | integer | ms | gap between key down and key up | Not listed |
screenVsClient | integer | px | difference between screenX and clientX, which should follow the window position | Not listed |
Technical limits
- Defeated by tools that add human noise
- Smooth trackpad users can look robotic
- Works best with many events
The story
What it is
A program that clicks tends to move like a program. The page measures that and guesses.
For you
You never see it. A person sounds irregular and so is accepted. An agent that clicks instantly in the exact middle of a button may be challenged.
For makers
Behavior models need many events, so use them on long forms, not on a single click. Add noise if you build agents that must act on defended sites, and respect the site's rules about automation.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A login page scores mouse movement before accepting a password attempt. | None named |
| shopping | A ticket queue slows clients that click with no earlier movement. | None named |
| games | A browser game flags auto clickers with identical delays. | None named |
| ads | An ad unit discards clicks that arrive with no pointer path. | None named |
| banking | A bank adds typing rhythm to a fraud score at sign in. | None named |
| developer | A tester adds random delays so an agent does not trip a defense. | Playwright |
Risks
- Penalizes assistive tools and unusual input devices
- Needs many events
What the platform says
- MDN: Pointer events. Docs describe pointer events and how pages receive coordinates and timing.
Good uses and abuse
Legitimate uses
- Bot defense
- Fraud scoring
Known abuse
- Behavior profiling
- Blocking assistive tools
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2023, Chrome: Public reports show CDP dispatched mouse events with matching screen and client coordinates
Related capabilities
Related
- Real or scripted event flag. Can tell if a click came from a real input path or from page script
- Mouse movement dynamics. Can track how your cursor moves on the page, to tell people from bots
- Pointer events (mouse, pen, touch detail). Can see where your mouse, finger or pen is and how it moves on the page
- Keyboard and IME events. Can see each key you press while the page has focus
Sources
- MDN MouseEvent.screenX
- Chrome DevTools Protocol: Input.dispatchMouseEvent
- Chrome Platform Status: PointerEvent coalesced events
How well checked: Inferred from related behavior.