Wordfence CLI Free reached end of life on October 14, 2026, and Premium licenses won’t renew.
Don’t settle for another scanner. Monarx goes far beyond what Wordfence CLI could do: always-on detection, automatic cleanup across the whole server, and PHP runtime protection that blocks attacks as they happen.
Switching to Monarx isn’t a like-for-like replacement. It’s an upgrade. Test it on your own servers and see the difference.
This applies to Wordfence CLI, the standalone command-line scanner. The Wordfence WordPress security plugin is not affected.
What’s changing
Wordfence is no longer issuing new Free or Premium CLI licenses. Here’s what that means for existing and prospective users.
Wordfence is no longer issuing Free or Premium CLI licenses. New users will need an alternative.
Wordfence CLI Free reached end of life on October 14, 2026. Free licenses are no longer valid or supported.
Existing Premium licenses remain supported until their expiration date. Renewals are no longer available.
Where Monarx fits
Monarx runs as an agent on your servers, combining local detection with cloud analysis and automated malware cleanup. You can manage protection through a web application or API, with controls at both server and user level.
Detects malicious files using agent-based scanning and cloud analysis, including behavioral analysis of suspicious files that may not match known signatures.
Active Protection quarantines or deletes malicious files and removes injected code from legitimate files.
ThreatShield monitors PHP execution and can block malicious activity in real time when blocking is enabled. This protection is not available in Wordfence CLI.
The upgrade
Wordfence CLI was a scanner you had to run. Monarx is protection that never stops: it watches your servers continuously, cleans infections automatically, and blocks malicious PHP activity as it happens.
Moving off Wordfence CLI? During the evaluation, we’ll review your existing scripts and integrations with you so you know what to keep in place.
How the evaluation works
You don’t need to replace your existing security tools to evaluate Monarx. Start with a few representative servers and review the results before enabling automated protection.
Technical requirements: Monarx supports selected Linux environments and requires administrative access. ThreatShield requires a PHP extension. Selected files may be sent to the cloud for analysis. We’ll review deployment requirements and data handling as part of the evaluation.
Install in detect-only mode. Deploy Monarx on a subset of your servers without enabling automatic remediation.
Review detection results. Check malware findings, false positives, and resource usage.
Test automated cleanup. Review quarantine, cleanup, and restoration behavior before enabling Active Protection.
Evaluate ThreatShield. Test PHP runtime protection separately, including blocking behavior.
Check your existing workflows. Confirm which integrations and scanning functions Monarx can cover and what needs to stay in place.
Tell us how you’re using Wordfence CLI today. We’ll help you test Monarx on your servers, compare detection results, and review your migration requirements.
Request an evaluation