BlogSafe.org

BlogSafe Honeypot is a ‘lite’ version of our private research tool. It’s purpose is to track two types of information.
<ul>
<li>Failed URL requests.</li>
<li>Failed login attempts.</li>
</ul>
By analyzing data collected by BlogSafe Honeypot, you will gain an insight into attempts to access known vulnerabilities as well as emerging 
threats. You’ll also be able to analyze which usernames and passwords brute-force agents are using in attempts to force their way into your site.
Main Features
<ul>
<li>Records information about connections incoming to your WordPress site that have no valid destination.</li>
<li>Records failed username and password attempts. Useful for analyzing brute-force attacks.</li>
</ul>
Other Features
<ul>
<li>IP and URL White-listing to prevent known requests and logins from being recorded.</li>
</ul>
Options
<ul>
<li>Can be configured to detect incoming The Onion Router (TOR) connections.</li>
<li>Can be configured to automatically delete requests and login attempts after 1 year.</li>
</ul>
Third Party Notice 
If the optional TOR detection is enabled, BlogSafe Honeypot will make a 3rd party connection to the TOR exit node list maintained by TOR. 
You can manually view this list here: <a href="https://check.torproject.org/exit-addresses" rel="nofollow ugc">TOR Exit List</a>

BlogSafe Honeypot

BlogSafe Honeypot is a 'lite' version our private research tool. Instead of tracking where visitors…

Donncha O Caoimh (a11n)

Andrew Ozz

Philip John

Ryan Boren

Thorsten Ott

Gary Pendergast

Jon Cave

This plugin searches the files on your website, and the posts and comments tables of your database for anything suspicious. It also examines your list of active plugins for unusual filenames.
It does not remove anything. That is left to the user to do.
Latest MD5 hash values for Exploit Scanner:
<ul>
<li>17e2ccfc834d691bc68cc5c64f9bed89 exploit-scanner.php (1.5.2)</li>
<li>1d5f9d6220fe159cd44cb70a998a1cd7 hashes-4.6.php</li>
<li>fbdf61c17f65094c8e331e1e364acf68 hashes-4.6.1.php</li>
<li>477d128d84802e3470cec408424a8de3 hashes-4.7.php</li>
<li>d53210f999847fbd6f5a2ecac0ad42f2 hashes-4.7.5.php</li>
</ul>
Latest SHA1 hash values for Exploit Scanner:
<ul>
<li>1decc1e47a53d1cab9e8f1ef15b31682198367ee exploit-scanner.php (1.5.2)</li>
<li>5cec64380a2acdc876fd22fbbbbf8c335df1ed3f hashes-4.6.php</li>
<li>99d9e7be23a350f3d1962d0f41e7b4e28c00841e hashes-4.6.1.php</li>
<li>1eeab377a1afc6d776827a063678d2461b29e71d hashes-4.7.php</li>
<li>8c890a6af26bb74e9d17e5d2b21d6be27764da45 hashes-4.7.5.php</li>
</ul>
See the <a href="http://ocaoimh.ie/exploit-scanner/" rel="nofollow ugc">Exploit Scanner homepage</a> for further information.
<h3>Interpreting the Results</h3>
It is likely that this scanner will find false positives (i.e. files which do not contain malicious code). However, it is best to err 
on the side of caution; if you are unsure then ask in the <a href="https://wordpress.org/support/" rel="ugc">Support Forums</a>, 
download a fresh copy of a plugin, search the Internet for similar situations, et cetera. You should be most concerned if the scanner is: 
making matches around unknown external links; finding base64 encoded text in modified core files or the <code>wp-config.php</code> file; 
listing extra admin accounts; or finding content in posts which you did not put there.
Understanding the three different result levels:
<ul>
<li>Severe: results that are often strong indicators of a hack (though they are not definitive proof)</li>
<li>Warning: these results are more commonly found in innocent circumstances than Severe matches, but they should still be treated with caution</li>
<li>Note: lowest priority, showing results that are very commonly used in legitimate code or notifications about events such as skipped files</li>
</ul>
<h3>Help! I think I have been hacked!</h3>
Follow the guides from the Codex:
<ul>
<li><a href="https://codex.wordpress.org/FAQ_My_site_was_hacked" rel="nofollow ugc">Codex: FAQ – My site was hacked</a></li>
<li><a href="https://codex.wordpress.org/Hardening_WordPress" rel="nofollow ugc">Codex: Hardening WordPress</a></li>
</ul>
Ensure that you change all of your WordPress related passwords (site, FTP, MySQL, etc.). A regular backup routine 
(either manual or plugin powered) is extremely useful; if you ever find that your site has been hacked you can easily restore your site from 
a clean backup and fresh set of files and, of course, use a new set of passwords.
<h3>Updates</h3>
Updates to the plugin will be posted here, to <a href="http://ocaoimh.ie/" rel="nofollow ugc">Holy Shmoly!</a> and the <a href="http://ocaoimh.ie/exploit-scanner/" rel="nofollow ugc">WordPress Exploit Scanner</a> page will always link to the newest version.
<h3>Other Languages</h3>
Unfortunately for people using WordPress versions for other locales some of the file hashes may be incorrect as some strings have to be hardcoded in their translated form. Here are some file hashes for WordPress in other languagues provided separately by other members of the community:
<ul>
<li><a href="http://wpbiz.jp/files/exploit-scanner-hashes/ja/" rel="nofollow ugc">Japanese</a> – thanks to Naoko</li>
<li><a href="http://talkpress.de/artikel/exploit-scanner-hash-deutsch-wordpress" rel="nofollow ugc">German</a> – thanks to Robert Wetzlmayr</li>
</ul>
The hash files should only be declaring an array called $filehashes and the majority of the hashes should still be the same.

Exploit Scanner

Works very well by pointing suspicious elements.

Useful and effective

Great plugin, but it's not well documented.

Anyways, it works on version 4.8.3 and theoretically any version as long as you generate (if you don't have) the hashes for your wordpress version; in my case I had to generate for 4.8.3 and it did a good job :)

Great security scan plugin but..

830 matches in a clean installation

Search the files and database of your WordPress install for signs that may indicate that it has fallen victim to malicious hackers.

BlogSafe Honeypot vs Exploit Scanner