Description
DevDome Malware Scanner is a WordPress virus scanner that checks files and database content for malicious code, backdoor and webshell patterns, and suspicious changes. Use it as a hack scanner to investigate signs of compromise, with malware detection findings that show affected items and supporting evidence.
For malware removal, the malware cleaner offers quarantine and official package repair for eligible file findings. Review the proposed actions, restore quarantined files when needed, and repair eligible WordPress core and WordPress.org plugin packages from your dashboard. Suspicious database content and configuration changes require your review.
Scanning and cleanup work without an account, including file integrity checks against official copies and a baseline for premium or custom code. The vulnerability check lists every installed plugin, theme, the WordPress version and the PHP version with their published security holes (WPVulnerability records) and tells you what to update; it is on by default and can be turned off in Settings. An optional DevDome account adds known-malware hash checks against 90,000+ signatures, signature updates and cloud reports.
A security scan of WordPress files and data
Use the security scanner for a manual security check or scheduled malware scan. It checks:
- WordPress core, plugins and themes for changed, missing or unexpected files.
- PHP code for suspicious execution, hidden code and remote downloads.
- Uploads for executable files and PHP disguised as images or documents.
- Database content for injected scripts, hidden iframes, spam and hidden links.
- Administrator accounts for new users and unexpected administrative permissions.
- WordPress scheduled tasks for suspicious arguments and other warning signs.
- Must-use plugins and drop-ins that may help malware return.
- wp-config.php, .htaccess and .user.ini for suspicious code or settings.
The database scan covers options, posts, revisions, approved comments, post metadata and user metadata. PHP analysis follows code behavior, including request input reaching execution and downloaded content being written to disk.
Vulnerability check
Every scan lists WordPress and PHP, every theme and every plugin under Updates, in three lists, each version matched against the public WPVulnerability records (CVE, WPScan, Patchstack, Wordfence): known holes, the version that fixes them, plugins removed from WordPress.org for a security issue, and a PHP branch past its security support. The Overview says which items to update. On by default; turn it off in Settings.
This is a version check against published records. It does not test the site by attempting an exploit.
Malware detection and findings you can review
The malware checker reports severity and confidence separately:
- Severity describes potential impact: Critical, High, Medium, Low or Info.
- Confidence describes how strongly the evidence suggests malicious activity.
A changed file or newly added administrator needs investigation but does not prove an infection. Low and Info findings are review notes.
Each finding shows the affected item, why it was flagged and supporting evidence. For modified core and WordPress.org plugin files, “View what changed” compares the file with the official copy.
Coverage gaps identify checks that were skipped, failed or only partly completed. These include excluded paths, unreadable files, size limits and unavailable official checksums. An unchecked area is never treated as verified clean.
Use the findings and coverage notes as evidence for a WordPress security audit.
File integrity and official repair
WordPress core and WordPress.org plugin files are verified against official WordPress.org checksums. WordPress.org themes are compared with the official package for the installed version. A file that is the official file of another release (an update that did not finish) is reported as a note about mixed versions, not as a modification.
Premium and custom plugins and themes are tracked against a file baseline. The first scan records the starting state; later scans show changes. The baseline records what was present, not whether it was safe.
For eligible core and plugin findings, repair uses the WordPress updater to reinstall the same installed version from the official WordPress.org package. It replaces the whole package, not just the flagged file.
Before reinstalling, repair stores backup copies in quarantine. Afterwards it checks the resulting package against official checksums. If the reinstall fails, it attempts to restore those backups and reports any remaining recovery work. Repair backups can also be restored from the Quarantine tab.
Malware removal and reversible quarantine
The malware cleaner offers “One click fix” for eligible file findings through quarantine or official package repair. Eligible findings can include known malware, suspicious executable files in uploads and modified core or plugin files.
Findings requiring review remain under “Needs your decision”. These include suspicious database content, configuration changes, administrator accounts and scheduled tasks. Available actions depend on the finding and the current file.
Quarantine removes a file from disk and keeps a compressed copy in the plugin’s database table. If compression is unavailable, it stores an uncompressed copy. Each record includes the original path, hash, size and permissions.
- Restore returns the file to its original path and verifies its hash.
- Permanent deletion is a separate action.
- Official core files and protected startup files cannot be quarantined.
- Restoring a suspicious file returns its original contents to the site.
After using these tools to remove malware, review the cleanup results and scan again to check what remains.
Hack cleanup and reinfection risks
After a hack, removing an infected file may leave behind accounts, tasks or files that allow malware to return. The Reinfection risks list (under Threats) brings together administrator, scheduled-task, must-use plugin and drop-in findings for review.
Where available, “Neutralize” lets you:
- Remove an account’s administrator rights while keeping the account.
- Remove scheduled events for a suspicious task.
- Quarantine a suspicious must-use plugin or drop-in.
Account roles can be restored under Users. Quarantined files can be restored from Quarantine. Removed scheduled tasks cannot be restored through the plugin.
New administrators and other unexpected additions need your review. Legitimate plugins can also create scheduled tasks, must-use plugins and drop-ins.
Scheduled scans and scan controls
Run a scan manually or choose daily or weekly scheduled scans for recurring antimalware checks. Automatic scans are scheduled around 02:00 site time and depend on WordPress cron running.
Scans run in short batches. The open admin page drives progress, with a WP-Cron fallback after you close the tab. You can pause, resume or cancel a scan.
Settings let you adjust batch duration, deep-scan file size limits and excluded paths. Reduced coverage is reported with the results.
Works without an account
Without a DevDome account, you can run file integrity, PHP, uploads, configuration, database, user and scheduled-task checks. Quarantine, eligible official repairs and local scan history are also available.
Official verification still contacts WordPress.org. DevDome’s known-malware hash lookup requires a connected account.
Anonymous detection telemetry is optional and off by default. Reports sent through the reporting buttons are separate actions. The External services section explains what each service receives.
Optional DevDome account
Connecting an account adds:
- Known-malware hash checks against DevDome’s database of 90,000+ signatures. These send file hashes, not file contents.
- Downloaded byte-pattern signatures for matching on your site.
- Cloud reports showing site security status in your DevDome dashboard.
“Enhanced analysis” is a separate opt-in. It sends short suspicious code fragments and a file-path hint for a second opinion. The plugin attempts to redact secrets before sending them, but redaction cannot cover every secret format.
Disconnecting stops hash lookups and signature updates. Previously downloaded byte-pattern signatures can still match locally.
Dashboard and multisite
Simple view shows the verdict, cleanup options and settings. Advanced view adds finding filters, bulk actions, file changes, reinfection risks, quarantine and scan history.
On multisite, the scanner requires network administrator access because file checks and cleanup can affect shared core and plugin files. Each site keeps its own scan data.
WordPress Abilities and MCP
On WordPress 6.9 and newer, WordPress Abilities let compatible AI agents read WordPress security findings, control scans, manage settings and use cleanup actions.
MCP clients can access these abilities when the site exposes them through an adapter such as the WordPress MCP Adapter.
Abilities use the same permission checks and action rules as the dashboard. Quarantine, repair, neutralization, restore and permanent deletion require an explicit confirmation flag from the agent.
External services
The plugin talks to the following services:
-
WordPress.org APIs (api.wordpress.org, downloads.wordpress.org, core.svn.wordpress.org, plugins.svn.wordpress.org): used to fetch official core and plugin checksums, plugin directory status (whether an installed plugin was closed for a security issue), the official zip of each installed WordPress.org theme (downloaded during a scan to verify the theme’s files) and, on explicit repair or comparison actions, official file copies. When a file does not match the installed version, the release lists of that plugin, theme or WordPress and the checksums (for a theme, the zip) of a few neighbouring releases are fetched too, to tell a file of another official release from a modified one. Only your WordPress version, locale, plugin and theme slugs and their versions are sent. Terms: https://wordpress.org/about/privacy/ Privacy: https://wordpress.org/about/privacy/
-
DevDome Security API (analytics.devdome.com), only on a site connected to a DevDome account: (a) during each scan, the SHA-256 and MD5 hashes of every scanned file are checked against the DevDome database of 90,000+ known-malware signatures (hashes only, never file contents); (b) after every scan a summary (severity counts, the type, title, site-relative path, status, the names of the checks that fired, the file checksum and size of the top 50 findings of any severity, the total number of open findings, the site’s wp-admin URL for the email button, the PHP version and short-tag setting, the WordPress version, the signature-set version and the plugin version; never file contents) is sent so your DevDome dashboard shows the site’s security status and your account address gets an email when critical or high threats are found; (c) the byte-pattern signature set is delivered and updated through the account and stored on this site, together with DevDome’s short list of confirmed false alarms (file checksums and finding paths; nothing is sent for it); the hash signatures stay on DevDome’s servers and are only ever queried by hash; (d) with the separate “Enhanced analysis” opt-in, short suspicious code fragments and a file-path hint are sent for a second opinion; the plugin attempts to redact common credential and secret patterns before transmission, but no redactor can guarantee that every secret format is removed. Authentication is the site token the DevDome Dashboard provisioned on connect. Nothing is sent before you connect. (e) with the vulnerability check on (Settings, on by default), after every scan the folder names, names and versions of every installed plugin and theme (an inactive one is marked), the WordPress and PHP versions, the newer version WordPress offers for each of them, and for each item with a known hole what the Updates tab shows about it (name, severity, number of holes, the fixing version, the kind of hole and up to three record names with their link), so the DevDome dashboard shows the same list under Site Health and the account gets one email per newly found vulnerability in an active plugin or theme. Terms: https://devdome.com/terms-of-service Privacy: https://devdome.com/privacy-policy
-
WPVulnerability API (www.wpvulnerability.net), while the vulnerability check is on in Settings (on by default, switch it off there): during a scan, the folder names and versions of your installed plugins and themes, the WordPress version and the PHP version are checked against this free public vulnerability database (data published under CC0). Only folder names and version numbers are sent. Terms: https://www.robotstxt.es/legal/ Privacy: https://www.wpvulnerability.com/privacy/
Signature data source (not a service the plugin contacts): the signature set is the Linux Malware Detect database (GPLv2, rfxn.com project), imported and served by DevDome; the plugin never contacts rfxn.com. Project page: https://www.rfxn.com/projects/linux-malware-detect/ License (GPLv2): https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
-
Plugin catalog (devdome.com): the DevDome Dashboard inside wp-admin fetches the list of DevDome plugins (names, descriptions, logos, links, WordPress.org slugs) from
https://devdome.com/wp-plugins/catalog.jsonat most once every 12 hours, and only after you have connected the site to a DevDome account; a site that is not connected never contacts devdome.com for it. Only the bundled core version is sent in the request; no site or visitor data. Terms: https://devdome.com/terms-of-service Privacy: https://devdome.com/privacy-policy -
Connecting a DevDome account (optional): the DevDome Dashboard offers connecting a free DevDome account. Nothing is sent until you press the Connect button. If you do connect, the shared library sends your site address, a generated site ID and a generated secret site token to
analytics.devdome.com/api/plugin/connect/startand/api/plugin/connect/claimto link this site to your account; afterwards it confirms the connection withapi.devdome.com/plugin/accountat most once every fifteen minutes while you use the dashboard (once an hour after a refusal), and tellsapi.devdome.com/plugin/disconnectwhen you disconnect. When you connect from the DevDome Dashboard, whose Connect card states this before you press the button, those account checks also carry the slug and version of each active DevDome plugin on the site plus the bundled DevDome library, WordPress and PHP versions, so your DevDome account can show your sites and their DevDome plugins for support and update notices. Nothing about other plugins, users, email addresses, content or visitors is included. Sites connected before this was introduced, and sites connected from a button that does not show that text, do not send the list. Disconnecting stops the checks and the plugin list. Terms: https://devdome.com/terms-of-service Privacy: https://devdome.com/privacy-policy -
Detection telemetry (analytics.devdome.com), only when you tick “Help improve detection” in Settings (off by default) and only on a site that is NOT connected to a DevDome account (a connected site’s scan report, item 2, already carries the same list): after each completed scan the plugin sends the severity, type, title, site-relative path, status, the names of the checks that fired, the file checksum and size of up to 50 open findings of any severity (most severe first), the total number of open findings, the scan number, the PHP version and short-tag setting, the WordPress version, and the plugin and signature versions, under an anonymous site id (a hash; your site address is never sent). Never file contents, e-mail addresses or absolute server paths. DevDome keeps these lists to tell files flagged on many unrelated sites (allowlist rules) from the same unknown file spreading across sites (new signatures), both delivered through the daily signature update. Terms: https://devdome.com/terms-of-service Privacy: https://devdome.com/privacy-policy
-
Scanner reports (devdome.com), only when you click “Report false alarm to DevDome” in the Actions menu of a finding list or “Send scan report to DevDome” on the Overview. The dialog shows the exact text before you send it: your site address, the plugin, WordPress and PHP versions, the signature version, and for each finding its severity, type, title, site-relative path, status, file hash, the plugin it belongs to and the stored evidence lines (secrets redacted, absolute paths removed), plus the note and reply e-mail in the dialog (prefilled with the site admin address, change or clear it as you like) (both optional). Never file contents. The report goes to DevDome support, who …
Installation
- Upload the plugin and activate it.
- Open Malware Scanner in the admin menu and press Scan Now.
- The first scan verifies integrity and seeds the file baseline; later scans add the change timeline.
- Uninstalling removes the plugin’s tables, settings and scheduled tasks, including the quarantine table. Restore or delete quarantined files before uninstalling if you still need them.
FAQ
Does the plugin delete files?
Quarantine removes the file from disk and keeps a non-executable copy in the plugin’s database table, compressed when compression is available. You can restore it from the Quarantine tab at any time. Permanent deletion requires the explicit Delete permanently button on a quarantined file.
Uninstalling removes the plugin’s tables, settings and scheduled tasks, including the quarantine table. Restore or delete quarantined files first if you still need them.
Do I need a DevDome account?
No. Every scanning engine runs on your own server: core, plugin and theme integrity, code analysis, uploads, configuration files, users, cron, database and persistence. Connecting a free account adds the 90,000+ known-malware signatures, the security dashboard and the alert email.
Without an account, the signature set is never downloaded, so there is no known-malware signature matching. The scanner relies on its heuristics and reports that in the coverage notes. If you connect and later disconnect, byte-pattern signatures already on the site keep matching, but updates and the file hash check stop.
Can a cleanup break my site?
Cleanup has safeguards to reduce that risk. Files WordPress cannot boot without are never quarantined. A repair reinstalls the whole package, either all of WordPress core or the whole plugin, through the WordPress updater and verifies it against official checksums afterwards.
The flagged file and every other file the reinstall would change are copied to quarantine first. If the reinstall fails, repair attempts to put the originals back and reports any remaining recovery work.
Theme files, database content, user accounts, cron tasks and configuration files are never changed automatically, with one exception: a theme file matching a known-malware signature is quarantined. Anything quarantined can be restored with one click from the Quarantine tab.
Why does the scan list coverage gaps?
Unscanned areas cannot be called clean. The Overview lists excluded paths, files above the deep scan size limit, unreachable checksum sources, files the previous scan could not finish and stages that failed. Findings on files that could not be rechecked stay open instead of being resolved.
Does a scan slow down my site?
Scans run in short batches while the admin page is open and continue through WP-Cron when it is closed. The default is 8 seconds per request, adjustable from 3 to 25 in Settings. You can pause or cancel at any time.
Scanning uses PHP time on your server. Lower the batch budget on very constrained shared hosting.
What is the difference between severity and confidence?
Severity is potential impact: Critical, High, Medium, Low or Info. Confidence is how likely the finding is malicious.
A known-signature match has 100% confidence. A high-entropy blob alone is only a contributing signal and is never called malware by itself. Low and Info rows are notes, not threats, and never trigger an alert.
Is my website hacked?
Run a scan and review its evidence and coverage gaps. The plugin checks for changed files, suspicious PHP, database injections and unexpected administrators or scheduled tasks. A changed file or new administrator alone does not prove the site was hacked.
Review eligible cleanup actions, then scan again. The Reinfection risks list (under Threats) helps you investigate access or files that may remain after cleanup.
How do I run a WordPress virus scan?
Open Malware Scanner in the admin menu and press Scan Now. The virus scanner checks WordPress files and database content using integrity checks and code analysis, with known-malware matching available through the optional account.
For virus removal from eligible site files, review the proposed quarantine or official repair action. This scans your WordPress installation; it does not provide continuous protection for your computer or automatically clean every finding.
Can it help with a pharma hack, Japanese keyword hack or SEO spam?
Its database checks look for injected scripts, hidden iframes, spam and hidden links in options, posts, revisions, post metadata and user metadata. These checks can help investigate a pharma hack, Japanese keyword hack or other SEO spam where the infection leaves those patterns.
Suspicious database content needs your review. The plugin does not automatically rewrite affected posts or remove search engine listings.
Can it find a redirect hack or malicious redirects?
The scanner checks PHP, database content, wp-config.php, .htaccess and .user.ini for suspicious code or settings that may be involved in a redirect hack. Review the evidence to investigate malicious redirects.
Configuration and database findings require a decision. These checks do not guarantee detection of every redirect mechanism.
Can I use it as an exploit scanner?
You can use it to inspect WordPress files for suspicious execution, obfuscated code, backdoor and webshell patterns, and other evidence of compromise. Its optional vulnerability check also compares installed versions with published records.
Its exploit scanner role is limited to code inspection and version checks. It does not attempt attacks or provide a penetration test.
Can it detect a PHP trojan hidden in a plugin or upload?
It checks for suspicious PHP behavior, hidden code, executable uploads and PHP disguised as images or documents. These checks can identify behavior associated with a PHP trojan, but detection depends on the code and scan coverage.
Official file comparisons help identify modified packages. Premium and custom code is tracked against a baseline, which records changes without proving that the original files were safe.
Screenshots







Changelog
2.0.4
- A stored snippet that is nothing but
document.write(unescape(...))of plain text and bare formatting tags is a review item, not a Critical finding. Anything else written that way is reported as before. - In
.htaccess, a rule that only turns away well-known SEO tools, scrapers, scanners and HTTP libraries (403 or 410) is no longer counted as a cloaking condition when the same file also redirects to another site. A rule that names a search engine, and every other user-agent rule beside such a redirect, is reported as before. - Amazon Associates code in posts and custom fields (product and banner frames, the tracking pixel, the ad scripts) is no longer reported as a hidden frame or a script from an unknown host.
- A PHP file in the uploads folder that only holds data (fixed values behind an exit guard, as some plugins write their settings or cache there) is a Low note, not an executable upload. A file with any code in it is reported as before.
- A long key, licence or certificate string in a
wp-config.phpthat holds nothing but settings (defines, plain assignments and the WordPress include) no longer makes the file a Medium review item. Awp-config.phpwith any other code is reviewed as before. - A command-line script in the site root that stops every web request in its first statement starts from a lower score and is reviewed, not quarantined. Code in it is still analysed and can raise the finding.
- A plugin folder is no longer reported for “many files not in the official package” when those files are empty placeholders.
- On a site with a renamed content folder, cached pages get the same treatment as under
wp-content/cache/. - A plugin updated while a scan runs, to the release WordPress.org offers at that moment but has no file list for yet, is not compared with the old release. That scan says so as reduced coverage and the next scan checks it.
- A translated site whose own language file list cannot be fetched no longer gets a “modified core file” alarm for
wp-includes/version.phpat once: such files are left unjudged for two scans in a row at most, with a coverage note.
2.0.3
- A WordPress core file that belongs to the English package, or to the language package the site was installed from, is no longer reported as a modified core file on a site that shows another language. The file is compared with the official list of that package for the installed WordPress version. A file that only a translated package ships is no longer reported as a missing core file on a site installed from another package.
2.0.2
- The File Changes list now shows the 1,000 newest changes of the last 90 days and says how many there are in total. On a site with many changed files the scanner page used to print every one of them, which made it slow and several megabytes large.
2.0.1
- Fixed a flood of false alarms on sites where a plugin keeps cached page content in WordPress transients (Internal Link Juicer, for example). Cached copies that hold embeds or ad scripts were reported one by one as medium threats, tens of thousands on a large site. They are now one low priority note for the whole group of rows. A transient is still reported as a threat when it holds code that is proof of an attack on its own, such as a script that decodes and runs a hidden payload.
- Fixed the scanner page not opening (a blank page, an error 500 or a not found page) on sites with tens of thousands of findings. The Threats and Reinfection risks lists now show up to 1,000 findings, the open ones first and the most severe on top, with the real totals above them, and the Overview names the 200 most severe items that need a decision and says how many more there are.
- The fix plan, the scan report, and the findings and security summary abilities now read findings in pages, so they no longer run out of memory on such sites. The fix plan ability returns the real number of decisions next to the list.
2.0.0
- New Updates tab: every installed plugin and theme, the WordPress version and the PHP version with their published security holes, the version that fixes them, plugins removed from WordPress.org, PHP branches past their security support, and an Update button. The Overview lists what needs an update. The check is on by default now (turn it off in Settings); the active plugins and theme also go to the DevDome dashboard on connected sites, taking over from Site Monitor.
- Each known hole now says how bad it is (critical, high, medium or low) and what an attacker could do with it, grouped by kind: site takeover, database access, file access, script injection and others. The worst items are listed first.
- PHP is marked only when its branch has lost security support. Hosts patch a supported PHP branch without changing its version number, so the holes published for a version no longer count against it.
- A connected site’s DevDome dashboard now shows the same list as the Updates tab: inactive plugins and themes, WordPress and PHP included, with what each hole lets an attacker do.
- The Updates tab opens with what needs an update and why, then lists WordPress and PHP, themes and plugins separately.
- The screen has five tabs in one row: Threats now holds Reinfection risks and File changes behind three buttons, and Scan History sits at the bottom of the Overview.
- The Updates tab no longer says “No known vulnerabilities” when items could not be checked.
- A known hole carries the same severity everywhere: the Threats list, the Overview, the alert and the Updates tab.
- Reinstalling a plugin no longer leaves a copy of every plugin file in Quarantine. Copies identical to the reinstalled files are removed once the reinstall is verified, and the remaining copies of a plugin are removed when that plugin is updated.
- A plugin that ships one very large file (over 8 MB) can be repaired when that file is the official one.
- One click fix: when several files of one plugin were changed, the files the reinstall already put back are marked repaired instead of failed.
- A JavaScript file that only mentions the PHP open tag is no longer analysed as PHP code.
- Fixed: a threat found in a plugin, theme or must-use plugin file was closed as gone by the next scan when the file had not changed since. A file with an open threat is now analysed on every scan, so the threat stays listed until it is handled.
- .htaccess: the PHP version line a host writes (cPanel, CloudLinux, LiteSpeed) and rules that switch PHP off in a folder are no longer reported as a PHP handler. A handler that runs images or other file types as PHP still is.
- Repair and View what changed say “could not be fetched, try again later” when WordPress.org does not answer, and “no official checksum” only when there is none.
- A threat that came back shows a red Reappeared badge, like an open one.
- Overview: every item under Needs your decision has a Dismiss button (the list’s Ignore; reopen it under Threats).
- Threats, Reinfection risks and Quarantine lists: the Severity and Status columns sort on click (worst first, then the other way, then the original order).
- Scheduled tasks: a hook that had a handler in any earlier scan (admin or WP-Cron context) is no longer reported as an orphan when the other context runs the scan.
- A scan that fails after its auto-resolve step puts acknowledged findings back as acknowledged, not as open.
- Neutralize (Reinfection risks): the account that is the only one able to manage the site (manage_options, with or without the administrator role) is never demoted from the list, the same guard the MCP ability had.
- Administrators: the only administrator on a site is never reported as a new or recently created account. Attackers add accounts; a single account is the owner, and deleting it would lock the site.
- Administrators: when the only administrator is a new account and every administrator of the previous scan is gone, that account is reported, with the names it replaced. A site that never had another administrator stays quiet.
- Fewer false alarms. A plugin, theme or WordPress file that is exactly the same file of another official release is no longer reported as modified or unknown. A partial update leaves files of two releases side by side; the plugin, theme or WordPress now gets one note that says so.
- WordPress post embeds (an embed of another WordPress site) are no longer reported as a hidden iframe, in any of the forms WordPress has written them and wherever it stores them.
- A script of a known service (analytics, ads, a pixel, chat, cookie consent) pasted into a settings field is a note, not an injection. A JSON-LD data block is not reported.
- Critical and High are kept for proven threats: known malware, code that hides and runs a payload, a version with a known hole. A new administrator, a new must-use file or drop-in, a changed core option, an odd scheduled task and a script or frame stored in the database are listed for review as Medium unless they carry such proof.
- A must-use file or drop-in that an installed plugin placed (a copy of its own file, or the loader it writes) is a note that names the plugin.
- After a plugin or theme update, the new files the update brought are judged like its other files.
- A connected site receives DevDome’s list of confirmed false alarms with the daily signature check. A finding on that list is kept as a note, without waiting for a plugin update.
- DevDome plugins carry a signed file list, so a staged or self-hosted copy of a DevDome plugin is no longer reported as modified.
- Code analysis: a log or cache file that is written encoded or behind an exit line, a method call on the plugin’s own class and a configuration file include are no longer reported as request-controlled code.
- A site copy that carried the plugin’s settings but not its database tables (some staging and migration tools skip them) showed “Table doesn’t exist” on every page and nothing scanned until the plugin was deactivated and activated again. The tables are now recreated on the spot the first time a query reports them missing, and the page says so; when the database user may not create tables, the page names the error instead.
- Scripts and pages in the page cache folder (wp-content/cache) are now checked for known malware and for code that decodes and runs a hidden payload or sends cookies to another server. An ordinary cached page is never reported.
- JavaScript module files (.mjs) are analysed like .js files.
- A script that sends the visitor’s cookie or stored data straight to another server is reported in files too, not only in the database.
- Code written through document.write(unescape(…)) is reported when the hidden text is a script with code in it. The old analytics and counter snippets that only load a file this way stay a note.
- A script inside a theme or plugin template is read to its end, also when PHP code interrupts it.
- Unknown script, HTML and configuration files inside wp-admin and wp-includes are looked into. A known signature or a hidden payload there is a threat, not a note.
- A file whose analysis could not finish (too large, out of time, or the scan stopped on it) is analysed again by the next scan instead of being skipped as unchanged.
- Overview: when the file of a threat changed after the scan found it, the headline says how many threats need a new scan instead of showing a green verdict.
- The warning about a new only administrator stays open until that account is no administrator any more. It used to close on the next scan.
- A payload keeps its severity inside the option of a header and footer code plugin, a bundled library folder and a script of a private plugin or theme. It used to be shown as a note there.
- Repair: the very large official files of a plugin are kept safe during the reinstall and put back when it fails. The WordPress repair also backs up the two files the updater always replaces.
- The copies a repair keeps are removed only after that plugin or WordPress was really updated, not after an update that failed or was skipped.
- Code analysis: a PHP file name split over joined strings, upper-case function names and a “Silence is golden” text no longer hide a file that writes request data into a PHP file.
- Updates tab: a record that does not say “lower than” no longer names its last affected version as the fix.
- A scan stage that could not run is reported as failed instead of being passed over.
1.3.18
- Database scan: approved comments are checked like posts (scripts, iframes, javascript: links, encoded payloads, spam keyword clusters, hidden links) plus a link count above the site’s own comment moderation limit; each hit is a review finding under Comments. Spam, pending and trashed comments stay with the moderation queue.
- Suspicious code: a PHP file whose first statement ends the request and is followed by __halt_compiler() never runs anything after that line, so the data behind it is no longer reported as binary or high-entropy code. Wordfence keeps its firewall state in such files (wp-content/wflogs/attack-data.php, config files); two of them were quarantined on a real site after a “Binary data embedded in a PHP file” note.
1.3.17
- Plugin integrity: a file that the plugin vendor’s own build ships but the WordPress.org build of the same version does not (Advanced Custom Fields downloaded from advancedcustomfields.com carries its update checker under includes/Updater/) is a LOW review note, not an unknown file with a quarantine button. Its code is still analysed; suspicious code keeps its full severity. Seen on a real site: two good ACF files quarantined. The same vendor build adds one “Update URI” header line to acf.php; when that line is the only difference from the WordPress.org copy, the file is a review note instead of a modified plugin file with a repair button.
1.3.16
- Verdict gate: a code-pattern finding on a file of an installed plugin or theme, a Composer library, a DevDome plugin, a must-use plugin your hosting platform installs, or a media, document or archive file is a review note (LOW or INFO), never a threat. A known-malware match or a strong signal (decoded payload executed, request input reaching exec or include, executable in uploads, auto-prepend directives) keeps its full severity. Seen on real sites: Gravity Forms and WPBakery code rated HIGH, a WP Engine must-use plugin rated CRITICAL, videos and backup archives flagged for a backtick.
- A benign verdict from the DevDome cloud analysis now lowers a pattern-only finding to a review note; before it only added a line while the finding stayed HIGH (Gravity Forms common.php).
- Trusted local baseline: a plugin, theme or must-use file an earlier scan already judged and that has not changed since is not analysed again (premium plugins, firewall plugins and hosting must-use plugins stop producing the same notes scan after scan). New, modified and first-seen files, everything outside those folders, and every file after a rules or signature update are scanned as before; the malware hash lookup still covers every file.
- A file of a bundled default theme (Twenty Twenty-Five and the others WordPress ships) that matches the WordPress core checksum list is no longer reported as modified: the theme zip on WordPress.org is built separately from the copy WordPress installs and can differ in content.
- An unknown PHP file inside a WordPress.org plugin folder that is identical to a file of an older release of the same plugin is reported as a leftover of an in-place update (Low review note with the release it belongs to), not as an unknown file (High). The list of releases comes from the WordPress.org plugin information API and is cached for a week.
- The One click fix ability is annotated destructive for MCP clients, so they ask before running it. It still moves every file it touches to quarantine first.
- A finding about a new must-use plugin, drop-in or administrator now closes itself when the file is removed or the account is deleted or demoted; it comes back if the object returns. Before, it stayed open until you clicked.
- Shared DevDome library 1.7.17: the connect beacon’s flood guard counts an IPv6 visitor per /64 network, and the one-click install of another DevDome plugin verifies the downloaded package against the published checksum before installing.
- The first activation opens the plugin screen once: the DevDome Account card when the site is not connected yet, the Overview when it is. Bulk activations never redirect.
- The restore-quarantined and update-settings abilities are marked as changes that cannot be undone, so an AI assistant connected through MCP asks before running them.
- The vulnerability feed note names the WPVulnerability data licence correctly (CC0).
- Shared DevDome library 1.7.16: the connect request to devdome.com stays valid for 60 minutes instead of 20, and the DevDome Tools page asks the server again while a request this site started is still open, so a connection authorized in a tab that never came back still completes; the Tools page notes when DevDome Analytics is not installed; the Analytics note styles are registered through WordPress instead of a style block in the page; one shared helper reads the visitor address behind a trusted proxy; the AI Assistant is listed in the plugin catalog. After connecting, the screen you land on says which account the site is connected to and the one next step.
1.3.15
- Scheduled scans no longer stall on a large backup archive or database dump that carries PHP: the check whether such a file could run as PHP now stops at the scan batch deadline, a large non-PHP file is pattern-checked in its first megabyte only and reported as partially checked, and the clock is read between the pattern passes so one batch can no longer overrun its budget by a whole megabyte.
- The code analysis no longer slows to a crawl on a very long line full of escaped quotes (a database dump line, a serialized settings blob): one megabyte of such text took 99 seconds and now takes a fraction of a second.
- The next scan batch is queued before the current one starts, so a worker that is cut off by a time limit no longer ends the scan; the following batch picks the scan up.
1.3.14
- A dismissible note at the top of the settings page mentions the free DevDome Analytics plugin, with a button that opens the plugin installer (or the Analytics screen when it is already active). Dismiss hides it for good.
- Shared DevDome library 1.7.13: uninstalling the last DevDome plugin also removes the note’s dismissal, the update-repair records and the per-user “Report a bug” flag; the visitor-beacon flood guard keeps one short-lived record per address and clears its expired ones itself, and behind Cloudflare it counts per visitor instead of per Cloudflare address.
- Nine code shapes from a real October 2026 break-in (a REST exploit that planted fake plugins, a lock360 re-infector and a fleet-wide index.php) are now recognised: function names assembled from string offsets and then called, variables named by escaped literals, a file that reads and decodes its own source, a password gate on a request key, a dispatch table built with strrev or join, errors silenced together with the time limit removed, a folder taken from the request and browsed, a remote address hidden in base64, and a visitor profile collected from the server variables and sent away. Every planted file from that incident now scores HIGH or CRITICAL; before, most scored LOW or were not reported.
- A request-driven file write in a file under 4 KB that does not use WordPress at all counts as a dropper. A small settings editor behind a capability and nonce check keeps its ordinary score.
- A PHP file that sits directly in the site root without being part of WordPress (the attacker’s admin.php next to wp-load.php) is reported, the same way an unknown file inside wp-admin or wp-includes is.
1.3.13
- Old plugin copies that an UpdraftPlus restore keeps under wp-content/updraft/plugins-old are checked against their own release on WordPress.org when its checksum list is available: a file with the same path and the same bytes as that release is no longer reported as suspicious code (two high and eight medium alarms on one site came from old Kadence Blocks and WP-Optimize copies, among them extension-less Composer bin files).
- A must-use plugin file that newly appears and is identical to a file the old copy still holds from its release is a low note naming the plugin, the same as for an installed plugin (Burst Statistics places burst_rest_api_optimizer.php this way).
1.3.12
- The report dialog (Report false alarms, Send scan report) prefills your e-mail with the site admin address so we can answer; clear the field to send without one.
- The readme now carries an Upgrade Notice, so the Plugins page of an older install says what a new version fixes.
1.3.11
- A .user.ini or .htaccess auto-prepend line that points at an installed plugin’s own loader is now a low note naming the plugin instead of a medium “persistence” alarm: NinjaFirewall writes its loader into wp-content/nfwlog and points PHP at it on every site it protects (reported from a real site, 2026-10-08), Wordfence does the same with wordfence-waf.php. The rule is general: the file is a byte copy of the plugin’s official release, or a small loader whose every include is such a file of one installed plugin. Any other target keeps the full alarm.
- Shared DevDome library 1.7.12.
1.3.10
- Overview: a small “Found a bug? Report it, we fix it within 24h” pill shows until the first scan completes or you dismiss it. It opens a note box and sends the note through the existing Report this error path (see External services, item 8); nothing is sent without your click.
- Shared DevDome library 1.7.12: a Cloudflare visitor address header is trusted only when the connection itself comes from a Cloudflare address, so a forged header from anywhere else is ignored.
1.3.9
- Shared DevDome library 1.7.10: shorter Connect text on the DevDome dashboard, which now lists only real problems and no longer says Not monitored; the one-time Report a bug hint is recorded through a nonce-checked request; icons are escaped on output.
- The scanner screen is printed directly instead of being buffered, and every value is escaped where it is printed.
- Overview: a status circle coloured by the worst open finding (red, orange, amber, green) replaces the score number; the header pills are gone.
- Settings: a DevDome Account section says what connecting sends before anything is sent; the other Connect buttons open it.
- Fixed: a file with two findings left the second one open after it was quarantined (“the file is no longer there”). All findings of a quarantined file now close together and reopen together on restore; a finding whose file is already gone closes.
- Fixed: the Overview still showed findings that had just been handled on another tab.
- Fixed: a clean result on a site without a DevDome account no longer says “1 check ran with reduced coverage”; the Scan Coverage list still names the account-only check.
- False alarms from the first 1.3.8 sites: a real PDF whose compressed stream happens to hold “<?=” is no longer a disguised executable (PHP’s own parser proves the grammar error, the file cannot run; a real shell inside a PDF still is); an EMPTY auto_prepend_file line (SureMails writes one to switch the attack off) is no longer reported; a scheduled task inside an active plugin’s own hook namespace with no handler attached (a switched-off module) is no longer a task to review.
- Listing text updated: title, short description and introduction.
1.3.8
- NinjaFirewall’s own rule set (the nfw_rules option) is no longer a “critical” finding: it is a list of attack patterns, which is why it looked like one. It is now a low note that names the plugin.
- A plugin that WordPress or your host updated while a scan was running was checked against the checksums of its previous version, so every changed file of the new release was reported as “modified”. The version is now read again from disk before the check, and once more if a difference shows up.
- A post that embeds another WordPress post is stored by WordPress itself as a hidden, sandboxed frame; that exact markup is now recognised as the embed it is instead of a hidden iframe.
- All In One Security’s firewall settings file under uploads (it starts with a stop-the-compiler statement, so nothing in it can run), Sucuri Scanner’s data files under uploads (an exit statement first, then data) and comment-only PHP stubs under other extensions (.stub, .php-old) are no longer reported as executable. Checked live against 25 security and firewall plugins.
- Admin and Site Enhancements’ settings (custom CSS and footer code) and Jetpack’s sync error log are treated like the other settings that carry code by design: a low note, not a “script injection”.
- MailPoet’s compiled email templates under uploads/mailpoet/cache (one template class per file, nothing that runs on its own) are a low “compiled template cache” note instead of dozens of high “executable upload” findings.
- A must-use file that is a byte copy of an installed plugin’s official file (NinjaFirewall’s loader) is reported as that plugin’s loader, low, instead of a high “new must-use plugin”. An empty or comment-only placeholder a hardening plugin writes into wp-includes is a low note instead of a high “unknown core file”.
1.3.7
- A hidden iframe in a script is reported only when it loads a page from a foreign address or carries inline HTML. The invisible helper frames that jQuery blockUI, elFinder and cross-site storage libraries build (UpdraftPlus, WooCommerce, WP-Optimize, All In One WP Security, Redux, YITH and others, 31 official files) are no longer “Suspicious code patterns”.
- The account report and the opt-in “Help improve detection” telemetry now include low and info findings (most severe first, 50 at most) and, for each finding, the names of the checks that fired, the file’s checksum and size, plus the scan’s PHP version, short-tag setting and WordPress version. Still no file contents, no addresses, no server paths. This lets DevDome reproduce a false alarm from the report alone instead of waiting for a support message.
1.3.6
- Photos, PDFs and other uploads are no longer reported as “PHP code inside the file” because of random bytes: a file is only a finding when PHP could actually compile and run it. On a real customer site 19 of 20 ordinary photos were still flagged by 1.3.5 (PHP short tags on); all 20 are now clean, and every known way of hiding PHP inside an image is still caught.
- The same rule now covers plugin and theme images, compressed logs, archives and other data files, which were flagged as “Suspicious code patterns” for the same random bytes.
- Elementor Pro Custom Code (_elementor_code) is treated like Elementor’s other data: a plain script there is a low note, not a high “script injection”. A script that redirects to a foreign host, decodes and runs code or loads from an unknown host stays an injection, in every known key.
- “Report false alarms” now sends every open finding (most severe first, 50 at most) instead of refusing when only low and info findings are left; when nothing is open the message says so and what to do.
1.3.5
- Fewer false alarms, measured on real customer reports: ordinary images, PDFs, fonts and compressed logs are no longer reported as “PHP code inside the file” (1,060 real media files: 43 alarms before, 4 now), while PHP really hidden in an image is still caught, including code wrapped in comments or strings.
- Normal plugin code no longer raises alarms for signing the current user out or for a boolean assert() check.
- An upload folder “keep out” index.php with a closing tag (WP Migrate) is recognised. A file that only looks like one but opens a second PHP block is now reported, which the previous version missed.
- JavaScript files that are exact copies of official WordPress files (a second WordPress install inside the site folder, backup folders) are no longer scanned as suspicious code.
- A short-echo tag followed by a backtick shell command is detected in uploads.
- When a file cannot be quarantined the message now says why: the file is gone, it is a link, it is a folder, or it is outside the folders the plugin may change.
- Measured on 1,155 public PHP malware samples: detection unchanged. On 17,261 official WordPress, plugin and theme files: 177 low to high alarms before, 147 now.
1.3.4
…
