Erik Torsner

<p>Integrity-checker uses a mix of traditional and new techniques to scan your website for potential issues. First and foremost, it verifies that all installed code is identical to it’s original version. By comparing WordPress core, plugins and themes in your installation with the original versions available at wordpress.org, Integrity-checker can quickly determine if there are any changes you need to be aware of. Integrity-checker also lets you compare your local version to the original to help you determine if you’ve been hacked.</p>
<p>Additionally, Integrity-checker scans all installed files for permission issues. Ensuring correct permissions is vital for WordPress security, as with any PHP based web application.</p>
<p>Lastly, Integrity-checker will look through some of the basic WordPress configuration to look for common security problems like user enumeration, directory index weak credentials etc.</p>
<h4>Features</h4>
<ul>
<li>Helps you track down hacked WordPress files in core, plugins and themes  </li>
<li>Makes it easy to find issues with file permissions</li>
<li>Detects common configuration problems</li>
</ul>
<h4>3rd party software</h4>
<p><a href="https://github.com/mtdowling/cron-expression" rel="nofollow ugc">cron-expression</a> copyright Michael Dowling, see <a href="https://raw.githubusercontent.com/mtdowling/cron-expression/v1.1.0/LICENSE" rel="nofollow ugc">license</a>. Cron-expression is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.</p>
<p><a href="https://github.com/chrisboulton/php-diff" rel="nofollow ugc">php-diff</a> copyright Chris Boulton under the <a href="https://opensource.org/licenses/BSD-3-Clause" rel="nofollow ugc">BSD license</a>. php-diff is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.</p>
<p><a href="https://github.com/silexphp/Pimple/" rel="nofollow ugc">silexphp/Pimple</a> copyright Fabien Potencier, see <a href="https://github.com/silexphp/Pimple/blob/v3.0.2/LICENSE" rel="nofollow ugc">license</a>. Pimple is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.</p>
<p><a href="https://datatables.net" rel="nofollow ugc">DataTables</a> 1.10.13 copyright 2008-2016 SpryMedia Ltd. Licensed under the MIT license, see <a href="https://datatables.net/license" rel="nofollow ugc">datatables.net/license</a></p>
<p><a href="https://github.com/arnapou/jqcron" rel="nofollow ugc">jqCron.js</a> Licensed under the MIT license, see <a href="https://github.com/arnapou/jqcron/blob/master/LICENSE" rel="nofollow ugc">license</a></p>


Integrity Checker

I've modified the review after discussion with the author

This is a very useful tool! The free API limit might be a little low if you want to test the site recurrently but it's still a useful tool.

Promising!

The WordPress Integrity Checker checks your WordPress installation by detecting modified files, permissions issues and other common problems. trnk

pluginkollektiv

<p><strong>Warning: <em>Checksum Verifier</em> has reached end of life. Its functionality is available in AntiVirus 1.4.0, use this plugin instead.</strong></p>
<p><em>Checksum Verifier</em> calculates MD5 checksums for all existing WordPress core files and checks them against official checksums. It thus will detect and react upon any unrecognized modifications made on your WordPress core system (for example <a href="http://blog.sucuri.net/2014/12/soaksoak-malware-compromises-100000-wordpress-websites.html" rel="nofollow ugc">SoakSoak malware</a>).</p>
<p><em>Checksum Verifier</em> runs a daily check on MD5 checksums. In case an unexpected result is detected in core, the plugin will send an e-mail with a list of affected files to site administrators (or super-admins in WordPress multisite). The first check-up will be executed during plugin activation. Regular core updates won’t cause any alarm, of course. Only in case core files have been compromised and your site might have been hacked, the plugin will notify you.</p>
<p><em>Checksum Verifier</em> works as a “silent” background process and will only bother you in case of unexpected file modifications that could potentially threaten your core install.</p>
<p>Better security with WordPress.</p>
<h3>Usable Hooks</h3>
<ul>
<li><code>checksum_verifier_ignore_files</code><br />
Modify or extend an <code>array</code> of file paths to be excluded from verification, relative to your WordPress installation path.<br />
Default is <code>array('wp-config-sample.php', 'wp-includes/version.php', 'readme.html', 'readme-ja.html', 'liesmich.html', 'olvasdel.html', 'procitajme.html')</code>.  </li>
</ul>
<h3>Support</h3>
<ul>
<li>Community support via the <a href="https://wordpress.org/support/plugin/checksum-verifier" rel="ugc">support forums on wordpress.org</a></li>
<li>We don’t handle support via e-mail, Twitter, GitHub issues etc.</li>
</ul>
<h3>Contribute</h3>
<ul>
<li>Active development of this plugin is handled <a href="https://github.com/pluginkollektiv/checksum-verifier" rel="nofollow ugc">on GitHub</a>.</li>
<li>Pull requests for documented bugs are highly appreciated.</li>
<li>If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the <a href="https://wordpress.org/support/plugin/checksum-verifier" rel="ugc">support forums</a> first.</li>
<li>If you want to help us translate this plugin you can do so <a href="https://translate.wordpress.org/projects/wp-plugins/checksum-verifier" rel="nofollow ugc">on WordPress Translate</a>.</li>
</ul>
<h3>Credits</h3>
<ul>
<li>Author: <a href="https://sergejmueller.github.io/" rel="nofollow ugc">Sergej Müller</a></li>
<li>Maintainers: <a href="http://pluginkollektiv.org/" rel="nofollow ugc">pluginkollektiv</a></li>
<li>English Translator: <a href="http://glueckpress.com" rel="nofollow ugc">Caspar Hübinger</a></li>
<li>Russian Translator: <a href="http://wpcoder.de" rel="nofollow ugc">Sergej Müller</a></li>
</ul>


Checksum Verifier

Verifies MD5 checksums of WordPress core files, sends e-mail to the mail address of your admin user warning in case of threat.

Integrity Checker vs Checksum Verifier