HUMAN Security (PerimeterX)
Bypass the HUMAN Security / PerimeterX press-and-hold challenge and obtain the signed _px3 / _px2 cookie.
HUMAN Security (formerly PerimeterX) protects sites with a sensor script plus, on a high risk score, an interactive press-and-hold challenge. The solver completes that challenge and returns the signed verdict cookie the protected origin validates.
| Type string | When to use |
|---|---|
HumanSecurity | Standard HUMAN Security / PerimeterX challenge |
PerimeterX | Alias for the same solver - the vendor's former name |
Data fields
| Field | Required | Description |
|---|---|---|
site_key | Yes | The PerimeterX appId, e.g. PXHYx10rg3. Read it from window._pxAppId on the block response, or from the collector hostname collector-<appid>.px-cloud.net. |
uuid | Yes | The challenge uuid from the block response (window._pxUuid). Without it only the sensor loads and no challenge is rendered, so there is nothing to solve. |
vid | No | Visitor id (window._pxVid). Frequently empty on a first-time client - send it when the block response provides one. |
The uuid is per-session and short-lived. Harvest it from the block response
immediately before submitting the task - a reused or stale uuid yields a cookie the origin
rejects.
Solution fields
| Field | Description |
|---|---|
solution.cookie | The full cookie string - send it as-is in your Cookie header. |
solution.token | Same value as cookie, for clients reading the generic field. |
solution.userAgent | Must be reused on every subsequent request. |
The verdict cookie name differs per deployment: some issue _px3, others _px2.
Do not hardcode either - replay the whole string.
Send the entire cookie string, not just the verdict cookie. Measured on sweetwater.com
(appId PXp2TBVNJZ): _px3 sent alone was refused with 403, while _px3 together with
_pxvid was served 200.
Example
{
"api_key": "YOUR_API_KEY",
"type": "HumanSecurity",
"site_url": "https://example.com/",
"proxy": "user:pass@host:port",
"data": {
"site_key": "PXHYx10rg3",
"uuid": "88c4569e-d93c-11f1-88e5-2efe2778b0f2"
}
}{
"errorId": 0,
"status": "ready",
"solvtime": 12.1,
"data": {
"useragent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...",
"language": "en-US,en;q=0.9",
"solution": {
"cookie": "_pxvid=853079ba-...; _px3=239c0b099015ec55...; pxcts=YLn1F-xLTAWrTEK6..."
}
}
}Obtaining the block context
The appId and uuid both come from the response that blocked you. PerimeterX serves two shapes and either can be parsed:
HTML block page - declares the values as globals:
<script>
window._pxAppId = 'PXHYx10rg3';
window._pxUuid = '88c4569e-d93c-11f1-88e5-2efe2778b0f2';
window._pxVid = '';
</script>JSON block body - returned by some API endpoints:
{ "appId": "PXAJDckzHD", "uuid": "a5952268-d94f-11f1-946f-bc9e3a903483", "vid": "" }How to identify HUMAN Security
- Look for
_px3,_px2,_pxvidorpxctscookies on the response. - Check for requests to
*.px-cloud.net,*.px-cdn.net,*.px-client.netoriframe.hsprotect.net. - A block response carries
<meta name="description" content="px-captcha">and a#px-captchacontainer, with a "Press & Hold" button inside nested iframes. - The collector endpoint embeds the appId:
collector-pxhyx10rg3.px-cloud.net.
Challenge variants
The same #px-captcha widget ships more than one interaction, and the solver detects and
adapts to both automatically - no extra parameters:
| Variant | Instruction copy | Behaviour |
|---|---|---|
| Press-and-hold | "Press & Hold ... until verified" | Button is held until the bar fills |
| Press once | "Press the button once, wait for confirmation" | Single click, then the bar fills on the server's clock |
Tips
- Harvest the uuid last. Build the rest of your request first, then fetch the block response and submit immediately.
- Reuse the returned
userAgent. The cookie is bound to the client that earned it. - Match the proxy. Mint and replay through the same exit IP. HUMAN binds trust to the IP, so a cookie earned on one address is unreliable on another.
- Space your solves. HUMAN rate-limits per IP, and a throttled rejection looks identical to a bot rejection - a burst of solves from one address degrades results.
- A solve clears the block. After a successful challenge the visitor is released, so subsequent requests from that IP may pass even without the cookie for a while.