Skip to main content

CAPTCHA guide

Kasada

An obfuscated VM and proof-of-work behind a 429, with nothing for a person to click.

Difficulty: Very high
Risk engine
Exploded concept drawing of how the Kasada challenge is built

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 a 403) with x-kpsdk-* headers
  • A challenge script named ips.js or p.js on a path specific to the customer
  • Requests to /fp, /mfc and /tl
  • The headers x-kpsdk-ct, x-kpsdk-cd, x-kpsdk-st, x-kpsdk-v and x-kpsdk-h
  • A KP_UIDz cookie
  • A binary POST to /tl sent as Content-Type: application/octet-stream
  • Bytecode for an obfuscated VM inside the script

How it worksLink to How it works

  1. A protected request without valid tokens is answered with 429 and the path of the challenge script.
  2. The browser loads /fp, /mfc and ips.js, then executes the obfuscated VM.
  3. The VM gathers fingerprint and environment signals and computes a proof-of-work.
  4. It posts an encrypted binary payload to /tl. When accepted, the reply carries x-kpsdk-ct (the session token) and x-kpsdk-st (the server time).
  5. Each protected request then sends x-kpsdk-ct along with a fresh x-kpsdk-cd proof, derived from ct, st and the request host.
  6. x-kpsdk-h ties the tokens together, so values taken from different sessions don't work.
  7. 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 /tl endpoint 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

  1. Start from a real browser with a persistent profile and a residential IP.
  2. Let the challenge script load and finish. Don't block /fp, /mfc or /tl.
  3. Keep the cookie jar (KP_UIDz) and every x-kpsdk-* value from one and the same session.
  4. Attach the returned x-kpsdk-ct and x-kpsdk-v to protected requests.
  5. When x-kpsdk-cd is required, compute a new proof for each request instead of reusing the last one.
  6. 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-ct changes once /tl accepts 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.

Skip the solver: let BrowserSolver handle Kasada

Website AntiBot runs a real browser session with matching TLS, headers, cookies and IP, clears the challenge, and returns the page. You send a URL, you get HTML back.

Kasada unlock guide →

For education and authorized testing only. Respect the law, privacy, and the terms of the sites you work with. Difficulty labels are editorial estimates. Adapted from the CC0 community field guide on GitHub.