[PR #915] [CLOSED] Attempt to bypass Google's CAPCHA using a third party service #1017

New issue

Closed

opened 2026-02-25 20:37:24 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 20:37:24 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/benbusby/whoogle-search/pull/915
Author: @Moist-Cat
Created: 12/27/2022
Status: ❌ Closed

Base: main ← Head: bypass_captcha

📝 Commits (10+)

c5ec5ca Ignore VIM backup files
5acac97 Parse response and delegate the work to the client
b26aeec Tests pass
9e8c48a Finish integration
ffa144d Merge branch 'main' into bypass_captcha
851f266 Clean up
440cb16 Fix tests
667dd9c Update readme w/ DBC instructions
8bb9472 Remove useless exception
9083d7f Merge branch 'benbusby:main' into bypass_captcha

📊 Changes

5 files changed (+192 additions, -0 deletions)

View changed files

📝 README.md (+17 -0)
📝 app/request.py (+18 -0)
➕ app/utils/captcha.py (+82 -0)
➕ test/test_captcha.py (+47 -0)
➕ test/test_files/recaptcha_v2_callback.html (+28 -0)

📄 Description

refs #211

Using a proxy or making any "suspicious" request triggers Google's reCAPTCHA v2 (with callback). I'm using https://deathbycaptcha.com/ to try to solve it.
I tested it using a blacklisted proxy, and the integration seems to be working fine. The problem is, Google just sends another CAPTCHA after we solve the first one so I'm not 100% sure if I'm sending the token to the correct endpoint of if Google is rejecting my request for some reason.
Manually solving the CAPTCHA gives the same result.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/benbusby/whoogle-search/pull/915 **Author:** [@Moist-Cat](https://github.com/Moist-Cat) **Created:** 12/27/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `bypass_captcha` --- ### 📝 Commits (10+) - [`c5ec5ca`](https://github.com/benbusby/whoogle-search/commit/c5ec5ca2ee4b41baff9c2a7bc0ac6be11b86bd4f) Ignore VIM backup files - [`5acac97`](https://github.com/benbusby/whoogle-search/commit/5acac97ae87615706039bd6a74efe7ae65d4ef6a) Parse response and delegate the work to the client - [`b26aeec`](https://github.com/benbusby/whoogle-search/commit/b26aeec17323aeca9681506db0b90675708d45e8) Tests pass - [`9e8c48a`](https://github.com/benbusby/whoogle-search/commit/9e8c48a8823646c9b9f30dbfd2efb5bfa19fb8ac) Finish integration - [`ffa144d`](https://github.com/benbusby/whoogle-search/commit/ffa144d1677c2d40ab890da6131ad88f29b962e7) Merge branch 'main' into bypass_captcha - [`851f266`](https://github.com/benbusby/whoogle-search/commit/851f266bc2215719cd7feb2926d1eb70a7986f95) Clean up - [`440cb16`](https://github.com/benbusby/whoogle-search/commit/440cb161386b3c46abbdcd524febdf1e363ba21e) Fix tests - [`667dd9c`](https://github.com/benbusby/whoogle-search/commit/667dd9cdfeefe68da47c3d526886b25b061a0b35) Update readme w/ DBC instructions - [`8bb9472`](https://github.com/benbusby/whoogle-search/commit/8bb94722a6b2959dfc8ab1ffe65b1d121ed907d5) Remove useless exception - [`9083d7f`](https://github.com/benbusby/whoogle-search/commit/9083d7fad4a0d1010959de97e138a409a6b58aba) Merge branch 'benbusby:main' into bypass_captcha ### 📊 Changes **5 files changed** (+192 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+17 -0) 📝 `app/request.py` (+18 -0) ➕ `app/utils/captcha.py` (+82 -0) ➕ `test/test_captcha.py` (+47 -0) ➕ `test/test_files/recaptcha_v2_callback.html` (+28 -0) </details> ### 📄 Description refs #211 Using a proxy or making any "suspicious" request triggers Google's reCAPTCHA v2 (with callback). I'm using https://deathbycaptcha.com/ to try to solve it. I tested it using a blacklisted proxy, and the integration seems to be working fine. The problem is, Google just sends another CAPTCHA after we solve the first one so I'm not 100% sure if I'm sending the token to the correct endpoint of if Google is rejecting my request for some reason. Manually solving the CAPTCHA gives the same result. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>