Google’s Hand-Gesture reCAPTCHA Was Bypassed by Stock Photos

Google is testing a reCAPTCHA challenge that asks site visitors to wave at their webcam and submit the resulting hand video to a machine-learning model. Testers have shown the new check, called hand gesture verification, accepts a still stock photograph of a waving hand routed through OBS Studio’s virtual camera. Google has not responded to the bypass demonstrations, and the feature remains an experimental option, not the default reCAPTCHA flow.

The bypass surfaced within days of the limited rollout that started in late June. The privacy stakes are not small: Google says it temporarily captures one or more webcam videos and extracts 21 hand-knuckle coordinates from the hand before deleting the recording. The result is a verification step the early tests suggest no longer works as intended, while asking visitors to share biometric-shaped data on every site that turns the feature on.

How the Camera Check Works

Hand gesture verification sits inside Google Cloud Fraud Defense, the platform behind reCAPTCHA on login screens, sign-up forms, password reset pages, and checkout flows. When the check triggers, the browser asks for camera access, walks the visitor through a gesture such as a wave or open palm, and records a short video. Google’s machine-learning model processes that clip and pulls out 21 hand-knuckle coordinates, using the same landmark scheme that powers its MediaPipe developer toolkit, before sending a yes-or-no verdict back to the site.

The cloud documentation page describing the gesture verification workflow states the video is processed only to recognize the gesture, that audio is never recorded, and that the footage isn’t linked back to a user identity. The same page adds that the information is “used and stored in accordance with the Google Privacy Policy.” That tension between a narrow, gesture-only data promise on one side and the broad Google Privacy Policy on the other keeps surfacing in coverage of the feature.

Site operators turn the option on inside the Google Cloud reCAPTCHA console. Visitors who can’t or won’t perform a gesture fall back to the older visual and audio challenges. The gesture step doesn’t retire those puzzles; it layers a camera check on top of them. Google has not committed a general-availability date for the feature. The current technical page describes it as an experimental opt-in, not the default reCAPTCHA behavior.

Days Old and Already Bypassed

A user on X first tested the new check with a static stock photo of a hand, then routed that still image through OBS Studio’s virtual camera so the browser saw it as a live webcam feed. reCAPTCHA accepted the gesture, and the poster’s method spread.

A Neowin reporter ran the same test in person and confirmed the bypass. The journalist spent a few tries and a few stock images to position the still correctly inside OBS before reCAPTCHA accepted the gesture. The same recipe, gHacks reports, has been wired into a short Python script that automates the steps.

The bypass does not need a webcam, a real hand, or any artificial-intelligence trickery. The only required ingredients are a still image of a waving hand and a free virtual-camera driver inside OBS Studio, a tool widely used by streamers. Once a webpage asks for camera access, OBS can present any image, including a JPEG, as if it were a live device feed. The browser cannot tell the still from a live camera, and neither can the gesture check behind it.

Reports from gHacks and others stress that the same recipe can be automated. A short Python script can present the stock image, grant the camera permission, and submit the verification in succession, the report says, letting a single machine clear the challenge at scale. The underlying mechanic, the documentation makes plain, is that the gesture check sees whatever image the virtual camera is sending and returns a pass. The result is a check that filters nothing for automated callers while adding real friction for the humans it was built for. Operationally, the lock at the door is wider than the keyhole.

1. Acquire a stock photo of a waving hand from any image library
2. Load the photo as the source inside OBS Studio’s virtual camera
3. Open a site that has enabled hand gesture verification
4. Grant the camera permission when prompted
5. reCAPTCHA accepts the still image as a valid gesture

The Neowin reproduction matched the original poster’s findings, and a broader walk-through of how the camera check fell reached the same conclusion: the gesture check filters nothing the bypass can defeat. For a fuller privacy-side breakdown, see our parallel write-up of the bypass within days.

What Google’s Documentation Promises

Google’s documentation frames the feature as a brief, narrowly scoped data exchange. Every captured video is tied to a single verification attempt and a single set of 21 hand-knuckle coordinates. The page is also explicit that any data collected is used and stored under the Google Privacy Policy, the same umbrella policy that governs Search, YouTube, and Gmail.

The hitches that worry privacy researchers aren’t abstract. A deleted Nest video was recovered for a high-profile investigation after the user had asked for it to be erased, the recent example Google users point to when they ask how durable a “deleted after verification” promise actually is across Google’s wider infrastructure. An industry analysis of the biometric CAPTCHA shift has flagged that any anti-bot tool consuming body-derived signals needs a visible rulebook covering purpose, retention, secondary use, accessibility, and resistance to virtual-camera and replay attacks. None of those rules currently appear on the HGV page itself.

The feature’s own documentation spells out a narrow front-page promise, then defers to a much broader privacy policy on the back. The same posture has shown up across Google’s other temporary-permission features, including guest mode in Maps and face-matching in Photos, where the company reserves a wide range of secondary uses for the captured signal. Until Google publishes an explicit HGV-specific data schedule, the working assumption for users is the wider one.

• 21 hand-knuckle coordinates extracted per gesture
• Audio never recorded during the verification video
• Video deleted after verification, per Google’s documentation
• One still image clears the check via OBS Studio

CAPTCHA Was Losing Long Before HGV

The new check arrives in the middle of an arms race where the previous defenses had already fallen. In 2024, researchers reported a 100% success rate against reCAPTCHAv2 using off-the-shelf object-detection models, the same YOLO-class tools that label traffic lights and crosswalks in real time. Last year, an OpenAI agent was recorded clicking through a Cloudflare “I am not a robot” check while narrating each step.

That pressure pushes platforms toward behavior-based checks, signals harder for a headless browser to fake. A webcam view of a moving hand is one such signal on paper. Google’s documentation describes the gesture check as a liveness signal, not an identity check, in the same way an automated passport gate treats a face scan. The published bypass cuts the value of that signal to roughly zero against a moderately motivated attacker.

Site operators who already feel CAPTCHA fatigue face a worse version of it. The visual challenge is annoying but takes a fraction of a second. The camera-based one prompts a permission dialog, requires a clear shot of a hand, and adds a full round-trip to Google’s cloud for analysis, all to confirm a signal that the most recent tests show can be spoofed with a still image.

Researchers call that gap a liveness tax, friction that real visitors pay and automated operators don’t, in exchange for a defense that has yet to hold. Google’s documentation markets the new check as a more human-friendly option than the visual puzzles, a claim the early tests have not borne out.

A Non-Biometric Alternative Is Already on the Table

Major browser and infrastructure vendors are betting on a different route for the same problem. Cloudflare, Google, Mozilla, and Microsoft jointly proposed Private Access Control Tokens, a cryptographic scheme that lets a server confirm a request comes from a legitimate client without any image puzzle, biometric read, or webcam permission at all. The proposal tracks the same bots-just-keep-rising pressure that pushed Google toward cameras, and it keeps the user out of the loop entirely.

We can build a better solution that maintains strong privacy and provides a much less annoying experience for real humans using the web.

That pitch came from Bobby Holley, chief technology officer for Firefox at Mozilla, in the joint announcement covered by Tom’s Hardware. For Google, the line is an implicit critique of its own biometric route.

What Users and Site Operators Should Do

For ordinary visitors, the immediate decision is whether to grant camera access at all. The Google page frames the prompt as optional, and the visual and audio challenges remain available for users who decline. Reviewing browser-level site permissions once in a while is a cheap way to confirm the camera is not lingering on domains that no longer need it. The gesture check is opt-in for site operators too, so a refused prompt simply falls back to the older CAPTCHA path.

For site operators, the calculus is harder. The bypass demonstrations show that HGV, in its current form, adds a privacy cost for legitimate users and little new protection against automated attackers. Static image and audio challenges still cover accessibility, while alternative anti-bot methods, including the cryptographic Private Access Control Tokens proposal that doesn’t rely on biometric verification, are worth weighing before any deployment of a biometric layer.

For operators, the move is to wait and see until Google demonstrates resistance to the bypass. The published recipe, virtual camera plus still photo plus an automated driver, will keep getting simpler, not harder, while the biometric-data cost on real visitors stays the same.

• Decline the camera prompt if a site’s service doesn’t justify biometric verification
• Use a separate browser profile when a check feels intrusive
• Revoke webcam access for sites that no longer need it
• Hold HGV off the table until resistance improves

Frequently Asked Questions

What is Google’s hand-gesture reCAPTCHA?

Hand gesture verification is an experimental reCAPTCHA option that asks visitors to give the browser camera access and perform a short gesture. Google’s model captures a brief video, extracts 21 hand-knuckle coordinates, and returns a pass or fail to the site.

How was it bypassed?

Testers fed a still stock photograph of a waving hand into OBS Studio’s virtual camera, which presented the still image to the browser as if it were a live webcam feed. reCAPTCHA accepted the image as a valid gesture, and reporters at gHacks, TechSpot, Tom’s Hardware, and Neowin reproduced the bypass independently.

Has Google responded to the bypass reports?

No. As of the most recent Google Cloud documentation update, the company has not announced a patch, a fix, or a timeline for general availability of hand gesture verification, and has not commented on the virtual-camera workaround.

Can users skip the hand gesture check?

Yes. Google still offers the older visual and audio challenges for users who can’t or won’t perform a gesture, and the gesture check is an opt-in for site operators rather than a forced upgrade.

What can users and website operators do today?

Visitors can decline the camera prompt, review browser permissions in Chrome, Firefox, Edge, or Safari, and use a separate browser profile when a site asks for webcam access. Site operators can hold the feature off until Google demonstrates resistance to virtual-camera bypasses, and consider the non-biometric Private Access Control Tokens proposal as an alternative.