HUMAN Security, previously PerimeterX, is an enterprise bot-management platform. Its visible challenge is the well-known "Press & Hold" button, but the real verdict comes from a sensor script that gathers browser and behaviour signals. On many sites the button never appears and the whole check runs in the background.
How to identifyLink to How to identify
- A
#px-captchaelement with a "Press & Hold" button - Cookies named
_px3,_pxvid,_pxhd,_pxdeandpxcts - Calls to
px-cloud.net,px-cdn.netor a first-party collector path - An
X-PX-Authorizationheader on protected requests - A page titled "Access to this page has been denied", or a challenge overlay
- Obfuscated sensor scripts such as
init.jsandcaptcha.js
How it worksLink to How it works
- The sensor script gathers browser, canvas, WebGL, font and behaviour signals.
- It sends that telemetry to the collector, which sets or refreshes
_px3. - Low-risk sessions go through silently. Suspicious ones get Press & Hold.
- The button measures how long it is held, pointer pressure, movement during the hold and timing consistency.
- A successful hold yields a verification token that the collector validates.
- Protected requests then need the resulting cookies, and on some sites an
X-PX-Authorizationheader as well. - Scoring never stops: a valid cookie can be downgraded later if the session starts acting like a bot.
Free & open-source bypass methodsLink to Free & open-source bypass methods
| Tool | What it does | Success Rate | Link |
|---|---|---|---|
| Patchright / Camoufox | Stealth browsers for the sensor and the Press & Hold step | 40–70% | Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox |
| DrissionPage | Real Chromium with fine control of pointer events | 35–65% | g1879/DrissionPage |
| SeleniumBase UC mode | Selenium with patches for sensor-heavy pages | 35–60% | seleniumbase/SeleniumBase |
| Playwright + CDP input | Sends native pointer events for the hold | 30–60% | microsoft/playwright-python |
| curl_cffi | Mimics browser TLS for sessions already warmed up | 20–45% | lexiforest/curl_cffi |
Practical approachLink to Practical approach
- Combine a real browser, a residential IP and a persistent profile.
- Let the sensor script load and send its telemetry. Never block the collector.
- If Press & Hold appears, press with a genuine pointer event, hold for a few natural seconds while moving slightly, then let go.
- Wait for the overlay to vanish and the protected content to load.
- Keep
_px3,_pxvidand the rest of the cookie jar for later requests. - If you are still denied, start again with another profile and IP instead of hammering retries.
Practical tipsLink to Practical tips
- Hold time is only one signal. Pressure, small movements and timing consistency are checked too.
- Having a
_px3cookie proves nothing, since one is set after failed attempts as well. - HUMAN often penalises profiles and cookies reused from earlier visits. Try both fresh and warmed sessions.
- Headless Chrome is challenged hard. Headful or anti-detect browsers fare better.
- What you do after the challenge also counts: slow down and avoid machine-like request bursts.
- Collector domains and script names change, so rely on cookie and header patterns rather than URLs.