绕过 Incapsula, 生成 reese84。
无需浏览器即可绕过 Incapsula(Incapsula 现以 Imperva 的名义销售)。Takion 通过一次 API 调用返回可用的 reese84 令牌或 ___utmvc cookie,让你的请求通过挑战,直达数据。
最后更新 · 覆盖能力已针对一个实时的 Incapsula / Imperva 目标测试。
被 Incapsula 拦住了?
在你的请求带上挑战所要求的 cookie 之前,Incapsula 不会放行:运行当前挑战的站点需要 reese84 令牌,运行经典挑战的站点需要 ___utmvc。Takion 在服务端根据实时挑战构建这个 cookie,并以可直接设置的形式返回。保留你自己的请求拿到的会话 cookie,加上 Takion 返回的那个,Incapsula 就会放你过去。
Incapsula 的工作原理
Incapsula 有两类挑战,一个站点只会用其中一类。经典的那类从 /_Incapsula_Resource 加载一段混淆脚本,并设置 ___utmvc cookie。当前的那类是 reese84,它的脚本路径在每次下发时都是随机的,脚本会构建一个探测 payload,POST 回同一路径,拿到的令牌就成为 reese84 cookie(值以 3: 开头)。两类都经过重度混淆,而且都会轮换。
Takion 为每类挑战各提供一个端点。对于 reese84,/solve 接收站点和你的代理,自行获取实时挑战,并以可直接使用的 cookie 形式返回最终令牌,同时提示何时续期。如果你想自己发送最后那个请求,/generate 会返回 payload 以及要 POST 到的端点。对于 ___utmvc,/utmvc 接收挑战脚本,返回 cookie 值以及需要重放的验证 ping。
Takion 不会给你 Imperva 的会话 cookie(incap_ses_*、visid_incap_*、nlbi_*)。这些由你自己对站点发出的请求来设置。把它们留在你的 cookie jar 里,再加上 Takion 返回的那个 cookie,会话就完整了。
- Takion 覆盖的挑战
- reese84 挑战,脚本路径随机化
- 来自 /_Incapsula_Resource 的经典 ___utmvc 挑战
- 自主传输模式:返回 reese84 payload,由你自己 POST
一次调用返回什么
一次调用即可返回站点所运行挑战对应的 cookie:来自 /solve 的 reese84 令牌,或来自 /utmvc 的 ___utmvc 值及其验证 ping。
reese84令牌本身,以可直接设置的 cookie 形式返回,并附带何时需要续期
___utmvccookie 值,以及需要重放的验证 ping
# reese84: full solve, returns the token
curl -X POST https://incapsula.takionapi.tech/solve \
-H "x-api-key: $TAKION_KEY" \
-H "Content-Type: application/json" \
-d '{ "site": "https://www.example.com", "proxy": "http://user:pass@host:port" }'
# → { "token": "3:...", "cookie": "reese84=3:...", "renew_in_sec": 815, ... }
#
# Own the transport: POST /generate → { "payload": {...}, "endpoint": "..." }
# then POST the payload as a raw text/plain body to that endpoint, from the same IP.
# Classic ___utmvc: POST /utmvc { "site", "script" } → { "cookie", "value", "validation_pings" }阅读 Incapsula / Imperva 文档同一个密钥,通吃每一堵墙。同一种 JSON 结构,适配每一个厂商。
How the Incapsula bypass works, end to end
One endpoint per challenge family. No browser, no de-obfuscating Imperva's script by hand.
- 1
You hit the wall
Instead of the page, Incapsula serves a challenge: the reese84 script, from a path that changes every time, or the classic
/_Incapsula_Resourcescript that sets ___utmvc. - 2
You call the matching endpoint
For reese84, send the site and your proxy to /solve. For ___utmvc, send the site and the raw challenge script to /utmvc. One call, no SDK.
- 3
We solve it server-side
Takion runs what Imperva's obfuscated script would have run. For reese84 it fetches the live script through your proxy and earns the token there, so it is bound to your IP. No headless Chrome anywhere.
- 4
You set the cookie and replay
Set reese84, or set ___utmvc and replay its validation pings, next to the session cookies you already hold. Send your request again through the same proxy and User-Agent and you are in.
The Incapsula cookies, decoded
Two challenge cookies, the session cookies around them, and the page you see when a check fails:
reese84- the current challenge's cookie. The value starts with
3:, and it is earned by POSTing an interrogation payload to a script path that changes on every delivery ___utmvc- the classic challenge cookie, computed by the obfuscated script at
/_Incapsula_Resource incap_ses_* / visid_incap_*- the session and visitor cookies Imperva sets on your own requests. They tie everything to one session
nlbi_<site id>- load-balancer cookies, like
nlbi_2682446andnlbi_2682446_2147483392, also set by your own requests Error 15- Imperva's block page: a 403 with an incident ID and error code 15 (codes vary).
X-Iinfois on every response, but a block carries a bot flag likeB15(14,0,0)in it, where a clean pass showsq(0 0 0 0)
Why request-based beats a headless browser here
reese84 is heavily obfuscated and it rotates. The browser way to beat it is a fleet of headless Chrome instances, each running Imperva's script, building the payload, and hoping the fingerprint holds. It works until Imperva re-obfuscates, and it costs you a browser farm, constant patching, and seconds per request.
Takion reverses the challenge and builds the payload directly. A solve is one HTTP call instead of a full page render. No Chrome farm to babysit, no Selenium retries when a container dies mid-challenge. You send the site and your proxy, you get the cookie back. Same story for ___utmvc.
What gets an Incapsula session flagged
A valid cookie is necessary, not sufficient. Imperva watches for these the moment you replay:
- User-Agent drift. The most common failure. Your User-Agent has to be identical on the challenge, the Takion call, and the final request. One mismatch and the token reads as a different client.
- Changing IP after the solve. The reese84 token is bound to the IP it was earned on. Solve and replay through the same proxy.
- Proxy or TLS mismatch. Even a valid token fails behind a bad proxy or a mismatched TLS stack. Keep the client consistent and the proxy clean.
- Treating the payload as the cookie. With /generate, POST the payload to the endpoint we return and set the token the site answers with. Or use /solve and skip that step.
- Skipping the validation pings. After setting ___utmvc, replay the pings /utmvc returns, or the cookie never validates.
- Dropping the session cookies. A reese84 or ___utmvc without the incap_ses, visid_incap and nlbi cookies your own requests picked up reads as an incomplete session.
The one rule that kills most 403s
Keep one User-Agent and one proxy across the whole session. Same UA on the challenge, the Takion call, and the final request, through the same clean proxy, and Imperva stays cleared.
部分使用 Incapsula 的网站
Incapsula / Imperva 守护着这些网站。Takion 在每一个上都能通过,所以绕过 accor 和绕过任何其他防护墙一样,都是同一次 POST。
登录流程上的 reese84
reese84,上面还叠加了 DataDome
Incapsula 绕过常见问题
- 两者都支持,各有一个端点。一个站点只会用两类中的一类。reese84 走 /solve(或 /generate),经典的 ___utmvc 走 /utmvc。你看到的是哪种挑战,就调用对应的端点。
- 把站点 URL 和你浏览所用的代理发送到 /solve。Takion 通过该代理获取挑战、构建 payload,然后返回令牌、一个可直接使用的
reese84=3:...cookie,以及告诉你何时刷新的renew_in_sec。令牌绑定在获取它的 IP 上,所以你的流量要保持在同一个代理上。 - 从页面 HTML 中取出
/_Incapsula_Resource脚本的 URL,加载该脚本,然后把它的原始 JavaScript 连同站点一起 POST 到 /utmvc。我们返回 ___utmvc cookie 和一组 验证 ping。设置 cookie,重放这些 ping,再重试你原来的请求。全程不需要浏览器。 - 几乎都是 User-Agent、代理或 TLS 不匹配。令牌绑定在获取它的会话和 IP 上。在挑战、Takion 调用和最终请求中使用 相同的 User-Agent,并通过同一个干净的代理、以一致的 TLS 重放。一个有效的 cookie 如果从不同的指纹重放,会被判定为劫持,Imperva 就会返回拦截页面:一个带有事件 ID 和错误码 15 的 403(也会出现其他错误码,比如 17)。
所有其他防护墙
今天就开始绕过 Incapsula。
免费开始,无需绑卡。一个密钥通吃每一堵墙,一小时内完成首次求解。