• Hi,

    I needed a more efficient way of banning bots and I ended up creating a small snippet/plugin to log the bots IPs straight in the error log.

    WP Armour usually just stops the submission and gives an error message. The spammer’s bot is still allowed to hit your server over and over again, consuming PHP resources and memory.

    By adding an error log with the offender IP, the server can process it directly with Fail2Ban (or similar) and block bots at network level.

    This is not intended as substitute for the Extended version, users still need it if they want to detect/block things like WooCommerce Checkout.

    So, the question here is, are you open to reviewing a PR for this, or would you prefer I maintain it as a standalone add-on?

    Long-term, I’m planning to maintain a community-shared, anonymized list of recurring bot patterns that could eventually complement WP Armour’s threat intelligence.

    • This topic was modified 1 week, 5 days ago by Dade.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Dinesh Karki

    (@dcsupport)

    Hi,

    This is a great idea. Moving the block to the network level is much more efficient for saving server resources, and I like the long-term vision for the shared bot list.

    I’d prefer a Pull Request to keep things integrated and seamless for users. However, if you think it’s better suited as a standalone add-on due to the technical requirements, I’m open to that as well.

    Let me know how you’d like to proceed!

    Best regards,

    Thread Starter Dade

    (@dade88)

    Kindly share the repo, I couldn’t find it before and that’s why I was posting here.

    It hooks wpa_handle_spammers directly, so it’s pretty straight forward.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.