{"id":1298,"date":"2013-04-13T07:55:49","date_gmt":"2013-04-13T12:55:49","guid":{"rendered":"http:\/\/patrioticfederalist.com\/wp\/?p=1298"},"modified":"2013-05-08T20:44:59","modified_gmt":"2013-05-09T01:44:59","slug":"wordpress-admin-page-being-redirected-due-to-brute-force-attempts","status":"publish","type":"post","link":"http:\/\/patrioticfederalist.com\/wp\/?p=1298","title":{"rendered":"WordPress Admin Page Being Redirected Due To Brute Force Attempts"},"content":{"rendered":"<p>Some idiots are always trying to brute force all WordPress pages by attempting to login as &#8220;<strong>admin<\/strong>.&#8221;\u00a0 Rather than reinvent the wheel, <a title=\"immotion\" href=\" http:\/\/www.inmotionhosting.com\/support\/website\/wordpress\/wordpress-security-preventing-brute-force-attacks-on-admin-loginhttp:\/\/\" target=\"_blank\">Immotion<\/a> explains it pretty well:<\/p>\n<p><strong>What is a Brute Force Attack?<\/strong><\/p>\n<p>One of the methods to gain information -primarily LOG-IN information &#8211; is by using a method called<strong> BRUTE FORCE<\/strong> attack.\u00a0 Basically, as the name suggests, they are not hiding the attack, and there&#8217;s no efficiency to the attack. You could say it&#8217;s like taking the &#8220;shotgun approach.&#8221;\u00a0 It simply is hitting the server looking for one thing, the correct login information for your WordPress site.\u00a0 Hackers will often infect other computer systems and then set them to attempt logging into the WordPress Administrator.\u00a0 The illustration below shows graphically how the attack traffic can come from many locations and be mixed with normal website traffic.\u00a0 The attack can also come from just one location, but the method of trying to crack the login is the same &#8211; it is simply going through a sequential search for your login.\u00a0 Brute force attacks can also increase resource usage of the website.\u00a0 Therefore, brute force attacks are not only trying to crack through your security, but they are also driving up resource usage when multiple attempts on the WordPress login is occurring.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: center;\"><a title=\"Admin\" href=\"http:\/\/www.inmotionhosting.com\/support\/images\/stories\/WP\/brutef.jpg\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" title=\"Admin Brute Force\" alt=\"brutef\" src=\"http:\/\/www.inmotionhosting.com\/support\/images\/stories\/WP\/brutef.jpg\" width=\"400\" height=\"352\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><strong>Preventing WordPress Brute Force Attacks<\/strong><\/p>\n<p>Since users are no longer using WordPress as simply a blogging solution, there isn&#8217;t as much emphasis on user management for the owners of the WordPress site.\u00a0 And this may also be a contributing factor to the problem.\u00a0 WordPress Site Administrators should regularly cycle their passwords and review their user lists to make sure that no one has been added that isn&#8217;t supposed to be on the list. Especially users added as Administrator-level users.\u00a0 There are also WordPress sites that do not require that people register to post comments or other actions on the website. To prevent unauthorized access we recommend the following:<\/p>\n<ul>\n<li>Block access to the WP-LOGIN.PHP\u00a0 using the HTACCESS file by requiring an additional password<\/li>\n<li>Block access to the WP-LOGIN.PHP using the HTACCESS file by allowing only specific IP address or range of IP addresses<\/li>\n<li>Find a plugin that prevents access to the login screen after a particular number of tries.\u00a0 The plugin should then use an interval of inaccessibility before the next attempt to login would be allowed.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>The first two methods using .htaccess are recommended as they will help to prevent excessive resource usage. <\/strong> There is no guarantee of this with the plug-in, unless the plugin can limit access no matter how many times login attempts are being made.\u00a0 The following information are examples of the code solutions for the .htaccess file as listed above.\u00a0 You get to .htaccess using Cpanel interface that all hosts provide.\u00a0 Use the &#8220;file manager&#8221; to find it then use their &#8220;code editor&#8221; to add the code.<\/p>\n<p><a href=\"http:\/\/patrioticfederalist.com\/wp\/wp-content\/uploads\/2013\/04\/cpanelFM.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-medium wp-image-1304\" alt=\"_cpanelFM\" src=\"http:\/\/patrioticfederalist.com\/wp\/wp-content\/uploads\/2013\/04\/cpanelFM-300x65.jpg\" width=\"300\" height=\"65\" srcset=\"http:\/\/patrioticfederalist.com\/wp\/wp-content\/uploads\/2013\/04\/cpanelFM-300x65.jpg 300w, http:\/\/patrioticfederalist.com\/wp\/wp-content\/uploads\/2013\/04\/cpanelFM-500x109.jpg 500w, http:\/\/patrioticfederalist.com\/wp\/wp-content\/uploads\/2013\/04\/cpanelFM.jpg 504w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p><strong>.HTACCESS method to deny user login using specific IP address or range of IP addresses:<\/strong><\/p>\n<p><em>Note:The below code needs to be in the .htaccess file located in the WP-ADMIN folder. If you don&#8217;t see one, then create a blank text file and name it .htaccess saving it in the wp-admin folder<\/em><\/p>\n<address>AuthUserFile \/dev\/null<\/address>\n<address>AuthGroupFile \/dev\/null<\/address>\n<address>AuthName &#8220;Admin Access Only&#8221;<\/address>\n<address>AuthType Basic<\/address>\n<address>&lt;LIMIT GET&gt;<\/address>\n<address>order deny,allow<\/address>\n<address>deny from all<\/address>\n<address># whitelist Admin 1 IP address<\/address>\n<address>allow from xx.xx.xx.xxx<\/address>\n<address># whitelist Admin 2 IP address<\/address>\n<address>allow from xx.xx.xx.xxx<\/address>\n<address>&lt;\/LIMIT&gt;<\/address>\n<address>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<\/address>\n<address>Another hosting company gave me this and it works on this site using it in the .htaccess I had to create.\u00a0 Replace Xs with your IP address which you can get from <a title=\"IPaddress\" href=\"http:\/\/www.whatsmyipaddress.com\" target=\"_blank\">Whatsmyipaddress.com<\/a>:<\/address>\n<p>&lt;Files ~ &#8220;^wp-login.php&#8221;&gt;<br \/>\nOrder deny,allow<br \/>\nDeny from all<\/p>\n<p>Allow from xx.xx.xx.xx<br \/>\n&lt;\/Files&gt;<\/p>\n<address>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<\/address>\n<address>You can add more IP addresses by adding an additional Allow from xx.xx.xx.xx to the code above.<\/address>\n<address>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<\/address>\n<p><strong>.HTACCESS method to deny user login using additional password for wp-login access:<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p><em>Note:The code below would be in the .htaccess file located in the .htaccess file located where you have installed WordPress.\u00a0 <em>If you don&#8217;t see one, then create a blank text file and name it .htaccess<\/em><br \/>\n<\/em><\/p>\n<p>&nbsp;<\/p>\n<address>&lt;FilesMatch &#8220;\\.wp-login.php$&#8221;&gt;<\/address>\n<address>AuthName &#8220;WordPress&#8221;<\/address>\n<address>AuthType Basic<\/address>\n<address>AuthUserFile \/home\/username\/.htpasswd<\/address>\n<address>Require valid-user<\/address>\n<address>&lt;\/FilesMatch&gt;<\/address>\n<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<\/p>\n<p>Some other common sense things to do to secure your WordPress site<\/p>\n<h2>Delete the \u2018admin\u2019 account<\/h2>\n<p>The default Administrator account on WordPress has a username of \u2018admin\u2019. Everyone knows that so don&#8217;t use it.\u00a0 Create another user with admin privileges.\u00a0 Login with that name to make sure it works and then delete the &#8220;admin&#8221; user.<\/p>\n<p>Go into the Dashboard \u00bb Users \u00bb Add New User screen. Create a new user with the role of Administrator. Now log out, and log back in as the new user.<\/p>\n<p><a href=\"http:\/\/www.problogger.net\/archives\/2011\/08\/11\/take-5-minutes-to-make-wordpress-10-times-more-secure\/\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" title=\"5min-wpsecurity-2\" alt=\"\" src=\"http:\/\/www.problogger.net\/wp-content\/uploads\/2011\/07\/5min-wpsecurity-2.jpg\" width=\"386\" height=\"236\" \/><\/a><\/p>\n<p>Go to the Users screen again and delete \u2018admin\u2019. You can transfer all of the content created by \u2018admin\u2019 to your new user account before confirming deletion.<\/p>\n<p>I recommend the plugin &#8220;<strong>WP Security Login Notification<\/strong>&#8221; too.\u00a0 It will tell you when there are failed login attempts.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Some idiots are always trying to brute force all WordPress pages by attempting to login as &#8220;admin.&#8221;\u00a0 Rather than reinvent the wheel, Immotion explains it pretty well: What is a Brute Force Attack? One of the methods to gain information -primarily LOG-IN information &#8211; is by using a method called BRUTE FORCE attack.\u00a0 Basically, as &#8230; <a title=\"WordPress Admin Page Being Redirected Due To Brute Force Attempts\" class=\"read-more\" href=\"http:\/\/patrioticfederalist.com\/wp\/?p=1298\" aria-label=\"Read more about WordPress Admin Page Being Redirected Due To Brute Force Attempts\">Read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[55],"tags":[447,448,446,445,449],"class_list":["post-1298","post","type-post","status-publish","format-standard","hentry","category-wordpress","tag-admin-bot-attack","tag-admin-brute-force","tag-admin-panel-not-working","tag-admin-panel-rediriect","tag-wordpress-brute-force"],"_links":{"self":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/1298","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1298"}],"version-history":[{"count":12,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/1298\/revisions"}],"predecessor-version":[{"id":1300,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/1298\/revisions\/1300"}],"wp:attachment":[{"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1298"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1298"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/patrioticfederalist.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1298"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}