Add honeypot field to increase bot solver resiliency #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have used this Captcha plugin successfully for a month or so before spambots started to pass it, even with fairly complex questions and extremely limited retry attempt allowances.
After adding some logging, it seems that solvers simply "bruteforce" the questions until they find the right answers and then store them so they can circumvent them in the future.
A very simple and highly successful improvement was noticed when we added a simple honeypot. Our logging then showed almost all bot attempts would be caught by the honeypot.