BlogSafe.org

<p>BlogSafe Scanner is a lightweight file scanner designed to notify you when any files are modified or uploaded to your server.</p>
<p>It’s features include:</p>
<ul>
<li>Creates a checksum of each file on your web server and compares them to official WordPress checksums. *1</li>
<li>Detects new and modified files on your web server.</li>
<li>Optionally ignore files that are changed often.</li>
<li>Optionally checks plugins and themes against the U.S. NIST National Vulnerability Database for known issues. *2</li>
<li>Optionally hecks plugins and themes for last known updates and alerts you when they haven’t been updated in over 12 months. *2</li>
<li>Sends e-mail alert to the server admin when it’s been deactivated.</li>
<li>Works with WP Multi-site (Activate on parent site only).</li>
<li>Sends e-mail alearts when new or modified files are detected (Plus version).</li>
<li>Scheduling of automatic scans (Plus version).</li>
</ul>
<p>Notes regarding 3rd party services:<br />
1. BlogSafe Scanner directly contacts various WordPress API’s for checksum verification.<br />
   During this contact the following information may be sent:<br />
    a. Plugin name and version.<br />
    b. Theme name and version.<br />
    c. WordPress version.</p>
<pre><code>The WordPress Privacy Policy can be found here: [WordPress](https://wordpress.org/about/privacy/  "WordPress Privacy")
</code></pre>
<ol>
<li>
<p>BlogSafe.org monitors and mirrors a portion of the NIST National Vulnerability Database for vulnerabilities related to WordPress, plugins and themes. When opting-in, BlogSafe Scanner will poll the BlogSafe.org API for these potential vulnerabilities. At no time will the plugin contact the NIST database directly.  BlogSafe.org also maintains a database of known WordPress themes and plugins. This database is generated directly from the WordPress repository and verified via the WordPress API.  When opting-in, BlogSafe scanner will poll the BlogSafe.org API for this data. At no time does BlogSafe Scanner directly contact the WordPress SVN.<br />
 During this opt-in contact the following information may be sent:<br />
 a. A list of plugins and themes found on your website along with their versions.</p>
<p>The BlogSafe.org privacy policy can be found here: [BlogSafe] (https://blogsafe.org/privacy-policy/ “BlogSafe Privacy”)</p>
</li>
</ol>


BlogSafe Scanner

BlogSafe Scanner is a lightweight file scanner designed to notify you when any files are…

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.

BlogSafe Scanner vs Checksum Verifier