What I mean by that is that the purpose of the Brave browser is
increasing privacy and an old user-agent is an identifying piece used in
the fingerprinting process. The further your Chrome digital footprint is
from Chrome/142.0.0.0 [1] of today, the more you stand out from the crowd.
[1] https://www.whatismybrowser.com/guides/the-latest-user-agent/chrome
I am glad that the solution was found.
Best,
Michael
GPG Key: 4337 2794 C8AD D5CA 8FCF FA6C D037 59DA B600 E3C0
On 11/29/25 23:51, Bruno Haible via Discussions among Savannah Hackers,
open subscription wrote:
Hi Michael,
Thanks for the answer.
Brave is an outlier here which does not match
the goals of the Brave project.
Not sure what you mean by that.
imperva recommends blocking all Chrome user-agents below 100 on page 34
of their 2025 Bad Bot Report [2] and based on the data I am seeing that
is sound advice.
[2]
https://www.imperva.com/resources/wp-content/uploads/sites/6/reports/2025-Bad-Bot-Report.pdf
Thanks for posting the justification on your side, and for confirming
that the issue is related to the User-Agent string.
If this is an updated version of Brave,
please file an issue with Brave as this string should be kept updated.
I updated my copy of the Brave browser, and the issue is gone now.
Thanks for the hint.
Bruno
