{"id":21961,"date":"2024-01-19T10:00:59","date_gmt":"2024-01-19T08:00:59","guid":{"rendered":"https:\/\/wpbeveiligen.nl\/?p=21961"},"modified":"2023-07-27T10:02:11","modified_gmt":"2023-07-27T08:02:11","slug":"what-is-a-hack-bot-heres-how-to-protect-wordpress-from-hackbots","status":"publish","type":"post","link":"https:\/\/wpbeveiligen.nl\/en\/what-is-a-hack-bot-heres-how-to-protect-wordpress-from-hackbots\/","title":{"rendered":"What is a hack bot? Here’s how to protect WordPress from hackbots"},"content":{"rendered":"

What is a Bot?<\/strong>
\nA Bot is simply the abbreviation of a “roBot.”<\/p>\n

Bots are 1000x faster than humans.<\/p><\/blockquote>\n

If we make a simple calculation, assuming that a human can manually attack one website per hour by conducting various security tests on WordPress, and then we see that a bot can attack a new website every 30 seconds with hundreds of requests, we can understand how quickly it can happen.<\/p>\n

A computer can execute several million requests (tests) per minute.<\/p>\n

In short, your website is hacked by a Bot?!<\/h2>\n

What the bot does in slow motion:<\/strong>
\ntranslated from computer language to human terms<\/em><\/p>\n

Requests for the WordPress version<\/h2>\n
    \n
  1. Html generator?<\/li>\n
  2. Readme.html?<\/li>\n
  3. Version.php?<\/li>\n
  4. Plugin output?<\/li>\n<\/ol>\n

    Requests for active plugins<\/h2>\n
      \n
    1. Directory listing wp-content: plugins<\/li>\n
    2. Output in HTML<\/li>\n
    3. Function request<\/li>\n<\/ol>\n

      And so on… Millions of requests per minute!<\/p>\n

      And this database of requests is kept up-to-date via, yes… another Bot.<\/p>\n

      What does the bot do after making the requests?<\/h2>\n

      Once the Bot knows the WordPress version running on your server and the active plugins and theme, it compares this information with the database containing vulnerabilities for each plugin and theme.<\/p>\n

      This process takes people half an hour, but for the bot, it’s a matter of milliseconds. (Thank you, technology!)<\/p>\n

      Knowledge is power<\/h2>\n

      When the Bot knows which plugins and themes are running on the WordPress version, it will use that information to exploit known vulnerabilities and inject code into the database and server.<\/p>\n

      Oh no! Code injections into the database and server? That sounds nasty!<\/p>\n

      Indeed, it is. The injections add data, including files that become active and send spam, or gather more information about users, or gain access to the server.<\/p>\n

      How do you protect against bots?<\/h2>\n

      The bots know the standard plugins, the default WordPress version, and compare them.
      \nSo, if they no longer know which plugins you are using, which theme, and which WordPress version, the bots are left powerless!<\/p>\n

      Combine this with the right measures against bots:<\/strong><\/p>\n

        \n
      1. Proper file permissions<\/li>\n
      2. Directories in unknown locations<\/li>\n
      3. Hidden directories<\/li>\n
      4. Corrections for injections via the browser<\/li>\n
      5. Corrections for files on the server<\/li>\n
      6. Blocking users and IP addresses (bots)<\/li>\n<\/ol>\n

        Then you can stop the Bots. They are just scripts that follow protocols! Break the habit, and a Bot won’t know what to do.<\/p>\n

        You don’t have to make these adjustments to your website manually; you have a bot for that \ud83d\ude09
        \nA script, or more specifically, iThemes Security<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"

        What is a Bot? A Bot is simply the abbreviation of a “roBot.” Bots are 1000x faster than humans. If we make a simple calculation, assuming that a human can manually attack one website per hour by conducting various security tests on WordPress, and then we see that a bot can attack a new website […]<\/p>\n","protected":false},"author":4,"featured_media":916,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[167],"tags":[],"_links":{"self":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts\/21961"}],"collection":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/comments?post=21961"}],"version-history":[{"count":1,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts\/21961\/revisions"}],"predecessor-version":[{"id":23068,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/posts\/21961\/revisions\/23068"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/media\/916"}],"wp:attachment":[{"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/media?parent=21961"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/categories?post=21961"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpbeveiligen.nl\/wp-json\/wp\/v2\/tags?post=21961"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}