Akamai Bot Manager is an enterprise bot-detection layer in front of many large retail, banking and travel sites. Most visitors never see a CAPTCHA. Akamai scores the session and then serves the page, runs a JavaScript sensor challenge, or returns an "Access Denied" page. When a visible CAPTCHA does appear, it is usually a separate product added on top.
How to identifyLink to How to identify
- Cookies named
_abck,bm_sz,ak_bmsc,bm_sv,bm_s,bm_soandsec_cpt - An
_abckvalue split by~, showing...~-1~...before validation and...~0~...after - A sensor script on a first-party path or under
/_bm/_orchestration_/ - A
POSTwhose JSON body looks like{"sensor_data":"2;...;<ciphertext>"} Server: AkamaiGHoston blocked responses- An "Access Denied" page that shows a reference ID
- An
Akamai-BM-Telemetryheader on some API endpoints
How it worksLink to How it works
- Akamai rates the first request on its IP, TLS fingerprint, headers and cookies.
- The page pulls in a sensor script that collects browser and device signals.
- The script posts
sensor_databack to the edge, and the reply updates_abck. - A validated
_abckcarries~0~in its state field.~-1~means it has not been validated yet. - Protected endpoints expect a valid
_abckand may also checkbm_sz,bm_svor a telemetry header. - Some sites add SBSD / Content Protector, which slows suspicious clients down (tarpitting) and sets extra cookies (
sec_cpt,sbsd). - A
201 {"success":true}after a sensor post does not prove anything. Always check_abckand a protected request.
Free & open-source bypass methodsLink to Free & open-source bypass methods
| Tool | What it does | Success Rate | Link |
|---|---|---|---|
| Patchright / Camoufox | Stealth browsers to run the sensor and warm up cookies | 40–70% | Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox |
| DrissionPage | A real Chromium session where cookies are easy to inspect | 35–65% | g1879/DrissionPage |
| SeleniumBase UC mode | Selenium with patches, for pages running the JS sensor | 35–60% | seleniumbase/SeleniumBase |
| curl_cffi | Imitates browser TLS/JA3 once cookies are warm | 25–50% | lexiforest/curl_cffi |
| nodriver | CDP automation that leaks less by default | 30–55% | ultrafunkamsterdam/nodriver |
Practical approachLink to Practical approach
- Warm the session in a real browser: open the homepage, let the sensor finish, and keep every cookie.
- Look at
_abckafter the sensor post. Wait for the~0~state, or test with a protected request. - Send API calls with the same cookies, User-Agent, Accept-Language and client hints.
- Space requests out like a person would. Sensor posts fired back to back are a clear bot signal.
- On sites using SBSD / Content Protector, expect deliberate slowdowns and avoid aggressive retries.
- For login and checkout, a full browser session beats raw HTTP.
Practical tipsLink to Practical tips
- Treat
_abckas opaque: send it back exactly as you received it and never rebuild it. - The sensor relies on
bm_sz. Losing it can break the session. - Cookie names and formats differ between customers, so save the whole jar by name.
- A validated cookie can lose its standing later, so keep the session's behaviour consistent.
- Homepages are often lightly guarded. Test against the endpoint you actually need.
- Akamai sometimes runs next to another vendor (watch for
__uzm*cookies). Don't assume there is only one system.