I am experiencing a significant challenge with the detectability of proxy usage via SeleniumBase, particularly during automated interactions with services employing stringent security measures, such as Funcaptcha on Outlook. The core issue is related to the method of proxy authentication which uses custom Chrome extensions (plugins), and this method is being detected by such services, leading to blocking or other restrictive actions.

1. The proxies in use are private and, on their own, do not contribute to detectability issues.
2. My testing with Selenium Wire, which configures proxies directly without needing browser plugins, shows no detectability issues. However, SeleniumBase, which relies on plugins for proxy authentication, is detected by security mechanisms.
3. The issue becomes particularly pronounced during interactions with Outlook's Funcaptcha, which appears to have a mechanism to detect the use of browser plugins typically employed for automation and proxy settings in SeleniumBase. Even when employing SeleniumBase’s stealth configurations, including the undetectable Chrome (uc) mode, the problem persists.
4. All potential configurations within SeleniumBase aimed at reducing detectability have been tried, including various stealth modes and settings, but none have circumvented the detection by Funcaptcha’s security measures.

The reliance on plugins for setting proxies in SeleniumBase is notably problematic in scenarios where security measures actively seek out such extensions as part of their anti-automation protocols. This issue is particularly evident during processes like Funcaptcha verifications on platforms like Outlook, which are sensitive to any form of automation or non-standard browser behaviors.

This situation significantly limits the effectiveness of SeleniumBase for tasks requiring high levels of stealth, especially in environments where advanced security protocols against automation are in place. Detectability during critical security checks like Funcaptcha not only hinders automation tasks but also risks potential blocking and further access restrictions, making it a critical issue needing resolution or workaround.