Skip to main content

CAPTCHA guide

VK Captcha

VK ID's 'not a robot' check combining proof-of-work, fingerprinting and a slider.

Difficulty: High
Risk engine
Exploded concept drawing of how the VK Captcha challenge is built

VK (VKontakte) runs its own CAPTCHA system under the VK ID name. In 2026 the old image CAPTCHA (captcha_sid / captcha_img) gave way to a JavaScript-heavy "not a robot" widget that mixes a proof-of-work, browser fingerprinting and, at times, a slider. You meet it during login, sign-up, password recovery, and whenever the API returns error 14.

How to identifyLink to How to identify

  • A page or iframe on id.vk.com or id.vk.ru with a path such as /not_robot_captcha
  • A #not-robot-captcha-checkbox checkbox
  • A large, obfuscated not_robot_captcha.js script
  • A slider shown to suspicious sessions
  • VK API error error_code: 14 with error_msg: "Captcha needed", redirect_uri and remixstlid
  • The legacy captcha_sid and captcha_img fields, only in old integrations

How it worksLink to How it works

  1. The VK API or the login page returns a captcha error containing a redirect_uri and a temporary user ID, remixstlid. Legacy clients may also get captcha_sid and captcha_img.
  2. The client opens the VK ID captcha page, which runs not_robot_captcha.js.
  3. The script calls captchaNotRobot.initSession and then captchaNotRobot.check. Along the way it solves a proof-of-work and collects a FingerprintJS browser_fp plus device and network signals.
  4. The proof-of-work is sent as v2. followed by Base64(JSON {hash, nonce}), and the check request also carries debug_info and interaction data.
  5. When everything passes, VK returns a success_token.
  6. The original API call is then repeated with success_token and remixstlid. The cookie and the parameter must agree.
  7. The token is tied to the session, the browser fingerprint and the IP.

Why it is hardLink to Why it is hard

  • The proof-of-work is just one layer. The browser fingerprint has to hold together too.
  • browser_fp is a FingerprintJS visitor ID built from canvas, WebGL, fonts and more. Plain HTTP can't fake it.
  • The script is heavily obfuscated and changes often.
  • VK looks at debug_info and at request timing to spot automation.
  • Even a valid token is rejected if remixstlid is missing or belongs to another session.

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

Tool What it does Success Rate Link
Playwright + real Chromium Drives the official widget, ticks the box and intercepts success_token 60–85% microsoft/playwright-python
Patchright / Camoufox Hide CDP and headless traces from the FingerprintJS check 50–80% Kaliiiiiiiiii-Vinyzu/patchright-python · daijro/camoufox
vk-captcha-solver (npm) A community solver for the VK ID captcha page experimental @tripoloski/vk-captcha-solver
DrissionPage Browser automation with tighter control over the VK ID iframe 50–75% g1879/DrissionPage

Practical approachLink to Practical approach

  1. Use a persistent browser profile and a residential IP in the target region.
  2. Trigger the captcha the normal way: login, sign-up or a controlled API call.
  3. Open the redirect_uri, wait for #not-robot-captcha-checkbox, and click it along a Bezier mouse path.
  4. If a slider follows, solve it with OpenCV template matching and a natural drag.
  5. Intercept the captchaNotRobot.check response to get success_token.
  6. Repeat the original request with success_token and the remixstlid cookie and parameter.
  7. Keep the same browser context, cookies, User-Agent and IP throughout.

Practical tipsLink to Practical tips

  • Leave debug_info untouched. A stripped or random value gives you away.
  • initSession must run before check. Skip it and you get status: BOT.
  • Hold on to the remixstlid cookie from the captcha page, because the token alone is not enough.
  • Let a real browser produce the fingerprint. HTTP-only solvers would have to fully reverse-engineer the fingerprint payload.
  • On the slider, the quality of the path matters as much as where the piece ends up.
  • VK changes this flow frequently. Pinning a known-good script version is fine for research but not as a long-term setup.

Skip the solver: let BrowserSolver handle VK Captcha

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.

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.