Kasada is a bot-management platform used by airlines, retailers and ticketing sites. It is not a visual CAPTCHA at all. A protected page answers with a 429 and a challenge script, and the browser has to earn a valid token by running an obfuscated virtual machine and a proof-of-work. There is nothing to click.
How to identifyLink to How to identify
- The first request gets a
429(occasionally a403) withx-kpsdk-*headers - A challenge script named
ips.jsorp.json a path specific to the customer - Requests to
/fp,/mfcand/tl - The headers
x-kpsdk-ct,x-kpsdk-cd,x-kpsdk-st,x-kpsdk-vandx-kpsdk-h - A
KP_UIDzcookie - A binary
POSTto/tlsent asContent-Type: application/octet-stream - Bytecode for an obfuscated VM inside the script
How it worksLink to How it works
- A protected request without valid tokens is answered with
429and the path of the challenge script. - The browser loads
/fp,/mfcandips.js, then executes the obfuscated VM. - The VM gathers fingerprint and environment signals and computes a proof-of-work.
- It posts an encrypted binary payload to
/tl. When accepted, the reply carriesx-kpsdk-ct(the session token) andx-kpsdk-st(the server time). - Each protected request then sends
x-kpsdk-ctalong with a freshx-kpsdk-cdproof, derived fromct,stand the request host. x-kpsdk-hties the tokens together, so values taken from different sessions don't work.- The session token can be reused for a while, but the per-request proof must be computed every time.
Why it is hardLink to Why it is hard
- The script is a custom bytecode VM rather than readable JavaScript, and its payload format is not public.
- It looks for instrumentation (CDP, Playwright, patched runtimes) before any user behaviour is even considered.
- Tokens are bound to the session, the IP, the User-Agent and the client hints.
- Both the script and the
/tlendpoint are first-party and differ from one customer to the next.
Free & open-source bypass methodsLink to Free & open-source bypass methods
| Tool | What it does | Success Rate | Link |
|---|---|---|---|
| Patchright / Camoufox | Stealth browsers that avoid the usual CDP giveaways | 40–70% | Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox |
| DrissionPage | A real Chromium session with fine-grained control | 35–65% | g1879/DrissionPage |
| SeleniumBase UC mode | Patched automation for JavaScript-heavy challenges | 35–60% | seleniumbase/SeleniumBase |
| curl_cffi | Browser TLS imitation for the parts of the flow that need no JS | 20–45% | lexiforest/curl_cffi |
| nodriver | CDP automation that leaks less by default | 30–55% | ultrafunkamsterdam/nodriver |
Practical approachLink to Practical approach
- Start from a real browser with a persistent profile and a residential IP.
- Let the challenge script load and finish. Don't block
/fp,/mfcor/tl. - Keep the cookie jar (
KP_UIDz) and everyx-kpsdk-*value from one and the same session. - Attach the returned
x-kpsdk-ctandx-kpsdk-vto protected requests. - When
x-kpsdk-cdis required, compute a new proof for each request instead of reusing the last one. - If the page keeps returning
429, begin again with a new session and another IP.
Practical tipsLink to Practical tips
- Never combine tokens from different browser sessions or proxy exits.
x-kpsdk-ctchanges once/tlaccepts the payload, so always send the latest value.- Sending empty
x-kpsdk-*headers is not the same as leaving them out, and the sensor notices. - The anti-instrumentation checks run on first load. A clean headful browser usually does better than a patched headless one.
- Every Kasada customer is configured differently: what works on one site may fail on the next.