Celebrating 700K+ Installs Up to 35% OFF! View Details β†’

Anti-bot challenge triggers Chromium's Local Network Access prompt

Published 24 days ago

# SafeLine WAF
# πŸ’‘ feature
# πŸ’ͺ improve

Published 24 days ago

profile_photo

Julio CΓ©sar

Updated 24 days ago

0

What happens: since Chrome 142 / Edge 143 (Local Network Access), the anti-bot challenge triggers a browser permissionprompt on visitors. The DevTools probe in challenge.js β€” a single WebSocket to 127.0.0.1:9222 β€” makes Chromium ask "Access other apps and services on this device". It appears only when something is listening on 9222 (Chromium prompts after the loopback connection is established, crbug 503004479), and denying it does not break the challenge: the slider still works. So it costs user trust and buys no signal. Small correction for the docs: on HTTPS the probe is wss://, not ws://.

Impact: on a public government site (.gob.mx) serving citizens, a local-network permission prompt on an official page reads as intrusive. People press "Block" out of caution, and the page still loads.

Ask (any one is enough):
a) drop the loopback probe and rely on the DevTools checks already in the bundle (webdriver, plugins/mimeTypes, formatter/debugger timing);
b) run the probe only after other signals have already flagged the session, so the prompt almost never appears;
c) a per-site switch to disable it, default off.

challenge.js ships from waf.chaitin.com, so this can be fixed server-side with no panel release: one line in the bundle.

Happy to test a build with the probe disabled.

profile_photo

Carrie

Updated 19 days ago

0

We've recorded this request in our internal feedback system, and our product manager is currently reviewing it. If there are any further updates, we'll keep you informed.

profile_photo

Carrie

Updated 3 days ago

0

Hi <@1311074600213418018> Here is the latest conclusion from our product team's discussion:

We've identified the cause of this browser prompt. Our anti-bot challenge script performs a CDP detection check by attempting to connect to 127.0.0.1:9222, which helps identify potential browser automation.

This detection is part of our anti-bot mechanism. Removing or changing it could affect the accuracy and effectiveness of bot detection, so it cannot be disabled or modified without carefully evaluating the potential impact.

Additionally, the Local Network Access prompt is enforced by the browser itself and cannot be suppressed through SafeLine's configuration or response headers.

Given these technical considerations, we don't currently have plans to make changes specifically to eliminate this prompt. We appreciate your understanding.

Anti-bot challenge triggers Chromium's Local Network Access prompt | CyberServal | CyberServal