Nikola (FirePhage)

FirePhage Security helps you monitor WordPress security locally with malware scanning, official checksum verification, login protection, update visibility, and optional FirePhage dashboard connectivity.
FirePhage Security includes:
<ul>
<li>local health and hardening checks</li>
<li>WordPress core checksum verification</li>
<li>plugin and theme repository integrity verification</li>
<li>background malware scanning</li>
<li>optional paid FirePhage dashboard connection for report sync and alerts</li>
</ul>
<h3>Licensing</h3>
FirePhage Security is licensed under GPLv2 or later.
All code and assets bundled inside this plugin are either:
<ul>
<li>original FirePhage plugin files released under GPLv2 or later</li>
<li>or GPL-compatible third-party assets documented below</li>
</ul>
Bundled third-party asset:
<ul>
<li>Choices.js</li>
<li>Source: https://github.com/Choices-js/Choices</li>
<li>License: MIT</li>
<li>Purpose: searchable country and continent dropdowns in the WordPress admin UI</li>
<li>Copyright: Josh Johnson and contributors</li>
</ul>
Choices.js is distributed under the MIT License, which is GPL-compatible.
<h3>External services</h3>
This plugin can contact external services in three cases.
<ol>
<li>Public checksum verification 
By default, the plugin requests WordPress.org plugin and theme checksum metadata directly from WordPress.org.</li>
</ol>
If the site owner explicitly enables the optional FirePhage checksum cache in Scanner Settings or during first-run setup, the plugin requests the same checksum metadata from FirePhage first and then falls back to WordPress.org if needed. These requests send only the package type, slug, and version needed for checksum verification.
When you manually choose Compare or Restore for an official WordPress.org checksum mismatch, the plugin may request the matching reference file through FirePhage so it can show a file comparison or restore the official file you selected. This happens only after a user action and is not part of normal background scanning.
FirePhage is used as a retrieval layer for official WordPress.org reference files; the plugin does not execute arbitrary remote code.
Service: https://firephage.com 
Privacy policy: https://firephage.com/privacy 
Terms: https://firephage.com/terms
<ol>
<li>Optional free FirePhage signature token 
If the site owner explicitly requests a free FirePhage signature token, the plugin sends the chosen email address, site URL details, plugin version, and optional marketing-consent preference to FirePhage so the token can be emailed and remote signature updates can be enabled.</li>
</ol>
Service: https://firephage.com 
Privacy policy: https://firephage.com/privacy 
Terms: https://firephage.com/terms
<ol>
<li>Optional paid FirePhage connection 
If the site owner explicitly connects the plugin to FirePhage, the plugin sends site connection details and security reports to FirePhage so dashboard sync and alerting can work.</li>
</ol>
Service: https://firephage.com 
Privacy policy: https://firephage.com/privacy 
Terms: https://firephage.com/terms

FirePhage Security

WordPress security plugin with malware scanning, file integrity checks, login protection, update visibility, and optional FirePhage sync.

Osman

File Change Monitor is a lightweight WordPress plugin that detects file changes in your core, theme, and plugin directories, helping you monitor unauthorized modifications or malware injections.
<h3>Features</h3>
<ul>
<li>Scans critical WordPress directories (wp-admin, wp-includes, wp-content/themes, wp-content/plugins)</li>
<li>Detects file additions, modifications, and deletions</li>
<li>Sends alert via email to the admin email address</li>
<li>Lightweight and fast</li>
<li>No configuration required – install and activate</li>
</ul>

File Change Monitor

Detects file changes in WordPress core, themes, and plugins. Sends email alerts to the site admin.

FirePhage Security vs File Change Monitor