Skip to main content

CAPTCHA guide

Imperva

Session-level bot management with JavaScript challenges and block pages.

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

Imperva, previously known as Incapsula, sells enterprise bot management and a web application firewall. A classic CAPTCHA is not guaranteed: a suspicious client may get a JavaScript challenge, an "Access denied" page, or a third-party CAPTCHA embedded in the block page. The verdict is based on TLS, IP, cookie and browser signals before any puzzle is shown.

How to identifyLink to How to identify

  • Cookies named visid_incap_*, incap_ses_*, nlbi_* and ___utmvc
  • Requests to /_Incapsula_Resource?SWJIYLWA=...
  • A block page mentioning an "Incapsula incident ID" or "Access to this page has been denied"
  • A JavaScript challenge that reloads the page after a moment
  • A reCAPTCHA, hCaptcha or GeeTest widget inside the block page
  • Response headers like X-Iinfo and X-CDN: Incapsula

How it worksLink to How it works

  1. At the edge, the first request is scored on IP reputation, TLS/JA3 fingerprint, headers and cookies.
  2. Trusted clients get the page. Doubtful ones get a JavaScript challenge or a block page.
  3. The challenge script gathers browser signals and sets the ___utmvc and incap_ses_* cookies.
  4. Later requests need that cookie jar. If the score drops, the challenge comes back.
  5. Some sites stack a visible CAPTCHA (reCAPTCHA, hCaptcha or GeeTest) on top of the JS challenge.
  6. There is no single token to win. The session itself acts as the credential.

Free & open-source bypass methodsLink to Free & open-source bypass methods

Tool What it does Success Rate Link
Patchright / Camoufox Stealth browsers that hide most automation traces 50–80% Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox
DrissionPage A real Chromium session that keeps cookies and handles challenges 45–75% g1879/DrissionPage
SeleniumBase UC mode Selenium with patches, suited to JS challenges 45–75% seleniumbase/SeleniumBase
curl_cffi Mimics browser TLS/JA3 for API-heavy targets 30–60% lexiforest/curl_cffi
undetected-chromedriver / nodriver Chrome automation with detection patches 40–70% ultrafunkamsterdam/undetected-chromedriver · ultrafunkamsterdam/nodriver

Practical approachLink to Practical approach

  1. Work from a persistent, real browser profile and a residential IP in the target's region.
  2. Open the page and let the challenge script run without blocking it.
  3. Wait for the reload or for the content to show, then keep the entire cookie jar.
  4. Carry the same cookies, User-Agent and TLS fingerprint into every following request.
  5. If a visible CAPTCHA sits in the block page, solve it as usual and stay in that session.
  6. For API calls, warm the cookies up in a browser first, then replay them through curl_cffi.

Practical tipsLink to Practical tips

  • Imperva judges the whole session. Clearing one challenge does not unlock every path on the site.
  • Datacenter IPs and inconsistent TLS fingerprints are turned away before any JavaScript runs.
  • A brand-new profile with no history raises suspicion. Reuse a warmed-up profile where possible.
  • Blocking analytics or the challenge script usually lowers the score instead of helping.
  • Challenge pages and cookie names differ between customers and change over time, so avoid hard-coding a single flow.

Skip the solver: let BrowserSolver handle Imperva

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.

Imperva 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.