AWS WAF can put two different gates in front of a request:
| Mechanism | What happens | What the visitor sees |
|---|---|---|
| AWS WAF CAPTCHA | A puzzle has to be solved | A distorted-text image with an audio option |
| AWS WAF Challenge | JavaScript checks the browser in the background | Nothing at all; a token is issued when the check passes |
Both are switched on by AWS WAF rules (Bot Control included) and usually sit alongside rate limiting and IP reputation lists.
How to identifyLink to How to identify
- AWS or Amazon branding on the challenge page
- An "Enter the characters you see" prompt with an audio icon next to it
- Requests to
*.token.awswaf.com,captcha.awswaf.comor other*.awswaf.comhosts - An
aws-waf-tokencookie and anx-aws-waf-tokenheader - Scripts named
challenge.js,captcha.jsor containingawswaf AWSWAForawswafin response headers or the page body
How it worksLink to How it works
- A WAF rule matches the request and answers with a CAPTCHA or Challenge action.
- The browser loads the AWS WAF script, which runs a proof-of-work and fingerprint check.
- With CAPTCHA, the visitor solves the image or audio puzzle. With Challenge, the script handles everything silently.
- Passing earns an
aws-waf-tokencookie. - Every following request carries that token, and the WAF checks it each time.
Free bypass methodsLink to Free bypass methods
| Method | What it does | Success Rate | Link |
|---|---|---|---|
| Whisper | Transcribes the audio version so the answer can be typed in | 85-95% | openai/whisper |
| ddddocr | Reads the text image | 60-80% | sml2h3/ddddocr |
| EasyOCR / PaddleOCR | Stronger OCR once the image is cleaned up | 65-85% | JaidedAI/EasyOCR |
| DrissionPage | Runs the genuine AWS WAF script and keeps token and cookies | 75-90% | g1879/DrissionPage |
| Patchright / Camoufox | Stealth browsers for Challenge actions | 70-90% | Kaliiiiiiiiii-Vinyzu/patchright-python |
| undetected-chromedriver | Selenium with patches, for the challenge flow | 65-85% | ultrafunkamsterdam/undetected-chromedriver |
Two practical routesLink to Two practical routes
- Challenge action (invisible): open the page in a real browser and let
challenge.jsfinish. Takeaws-waf-tokenfrom the cookie jar and keep reusing it with the same User-Agent, TLS stack and IP.curl_cffiwith browser impersonation can carry on from there if the fingerprint lines up. - CAPTCHA action (visible): switch to the audio version and transcribe it with Whisper, or run OCR on the text image. Type the answer into the widget and AWS hands out the token.
Practical tipsLink to Practical tips
aws-waf-tokenis tied to the client. A new IP or User-Agent in the middle of a session usually kills it.- The audio version can be rate-limited, so don't request it in a tight loop.
- For OCR, crop the image, strip the noise and restrict the character set. The text is distorted but generally legible.
- Keep the browser session running: the WAF script is also what refreshes the token.
- Unpatched headless Chrome stands out immediately. A real browser profile is the safer choice.