You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I looked at the quick start and it seems that it would be trivial for some automation software to simply intercept the request for loading the script and parch it to always return false.
This could theoretically be mitigated by checking the checksum of the BotD JS lib, but the code doing that could also get patched.
Are there any recommendations on how to prevent that sort of attack?
The text was updated successfully, but these errors were encountered:
Anything that runs in the browser is unsafe. If you want guarantees about client-side execution, it needs to be coupled with a server-side backend component. Apologies for a very general answer, but it's just not possible to prevent what you've described entirely with this client-only architecture.
Hello,
I looked at the quick start and it seems that it would be trivial for some automation software to simply intercept the request for loading the script and parch it to always return false.
This could theoretically be mitigated by checking the checksum of the BotD JS lib, but the code doing that could also get patched.
Are there any recommendations on how to prevent that sort of attack?
The text was updated successfully, but these errors were encountered: