Required for the site to work (login, preferences, security). Always on.
CrowdSec 1.8.1 patches its new bot-detection feature
CrowdSec shipped v1.8.1, fixing a false positive in the bot-detection feature added in 1.8.0 last month. For MSP edges, the useful pattern stays the same: logs in, hub rules out, review before blocking.
In this article
CrowdSec has released version 1.8.1, a quick patch on top of last month's 1.8.0 release, fixing a false positive in the bot-detection feature the project added on 31 August. The bug flagged Brave Browser users running with Shields enabled as suspicious; 1.8.1 corrects that along with three smaller fixes on the Local API side.

What changed and why it's still labeled Alpha
Version 1.8.0 added a browser-challenge and device-fingerprint check that CrowdSec's AppSec module can place in front of protected web traffic: it issues a proof-of-work challenge, evaluates the result, and grants a signed cookie to clients that pass, while repeated suspicious behavior converts into a normal CrowdSec alert and decision. CrowdSec labels the feature Alpha, meaning its configuration and shipped rules can still change between releases — worth knowing before wiring it into a production blocking policy without a review step.
The defensive loop for MSP edges
The operational pattern that makes CrowdSec useful for managed edges hasn't changed with this release: inventory which edges actually emit the auth, WAF or proxy logs CrowdSec needs to parse; subscribe to hub scenarios and blocklists that match those log sources; deploy bouncers — the components that act on CrowdSec's decisions — only where a customer's remediation policy has signed off; and schedule false-positive review inside agreed change windows rather than letting blocking rules run unsupervised. That loop applies whether or not a given site enables the new bot-detection check.
Rolling out 1.8.1
- If 1.8.0's bot detection is already deployed, update to 1.8.1 to clear the Brave false positive before it generates support tickets.
- Treat bot detection as Alpha in any client-facing SLA — expect its rules to shift in later releases.
- Keep an audit trail of who approved which remediation rule per tenant; that record matters more than the detection feature itself when a customer asks why traffic was blocked.
Sources: CrowdSec v1.8.1 release notes, Help Net Security.