News for hackers. Stuff that matters.
Re:Botspam apocalypse by sparkling on Thursday August 04, 2022 @03:38AM (#32340238)
Very nice list of countermeasures. I agree that doing these small things like hidden input fields really go a long way.

I would add to that:

- block signups/comments from known throwaway email domains

- block known datacenter IP ranges, at least for POST requests. Honestly on our sites 50% of spam was coming from AWS EC2 IPs

- use a proxy/vpn/bot detection service like https://focsec.com

Re:Botspam apocalypse by Zak on Thursday August 04, 2022 @05:48AM (#32340995)
Please don't make blocking VPNs plan A. Between snooping ISPs and public wifi networks that have indiscriminate content filters, I'm on a VPN about half the time. Many other legitimate users are as well.
Re:Botspam apocalypse by EdwardDiego on Thursday August 04, 2022 @04:48AM (#32340670)
Yup, in adtech, "IP is an AWS block" was a bot 99.999% of the time.

The 0.001% was that person using EC2 as a proxy or VPN server.

Re:Botspam apocalypse by mobilio on Thursday August 04, 2022 @05:08AM (#32340774)
It's not only AWS. Also happens on Azure and GCP.
Re:Botspam apocalypse by EdwardDiego on Thursday August 04, 2022 @06:32AM (#32341251)
True, but at the time, 3 - 4 years ago, Azure and GCP IPs were minimal.

Guess the fraudsters were vendor locked lol.

Re:Botspam apocalypse by account42 on Monday August 08, 2022 @06:32AM (#32383998)
> block signups/comments from known throwaway email domains

Throwaway email services have caught up to the point where even bigger players don't manage to block them, i.e. they rotate the domains used for the emails.

Re:Botspam apocalypse by emptyparadise on Thursday August 04, 2022 @04:16AM (#32340488)
But then you end up forcing people to use Gmail.