# A plugin that was running and not in the plugin list · Founder notes · respira.press

> One hidden plugin took a company's legal pages offline. What it looked like, what the security scan checks since Respira for WordPress 9.1.10, and how to scan…

Source: https://www.respira.press/newsletter/hidden-plugin

---

| [ ![A row of small clay plugs on a dark desk. One is missing, and its shadow is still there, inside a thin green ring.](https://www.respira.press/emails/hidden-plugin-kv.jpg) ](https://www.respira.press/blog/hidden-wordpress-plugin-not-in-plugin-list?utm%5Fsource=newsletter&utm%5Fmedium=email&utm%5Fcampaign=hidden-plugin-2026-10) RESPIRA.PRESS · 2 OCTOBER 2026 A plugin that was running and not in the plugin list. It happened on a real site this week. The Respira security scan now looks for it on yours. 01 What happened. On 1 October a company's terms and privacy pages began showing "No results found". The pages were still in WordPress. A plugin nobody had installed was running, and the Plugins screen in wp-admin did not list it: the database held 15 active plugins, the screen showed 14.It had placed one rewrite rule ahead of WordPress's own page rule, and that one line took every top-level page off the site. It was found and fixed in about ten minutes, through Respira, with no server access. 02 What the scanner looks for. One scan reads a site and checks four things: **Every known vulnerability** in WordPress, your plugins and your themes: more than 41,000 records from the Wordfence Intelligence database, refreshed every six hours. It names the version that fixes each one. **The incidents in the news**, each with its own traces: the WordPress security releases of August and September, the backdoored builds of Admin Menu Editor Pro, and others as they are published. **Signs that someone was already in:** changed WordPress core files, administrators added recently, application passwords, PHP files sitting in uploads. **New in 9.1.10, what wp-admin does not show:** a plugin that is active and hidden from the plugin list, and a rewrite rule that answers your pages before WordPress does. When something turns up, your AI can fix it with your approval: update to the exact version, or quarantine a plugin, which stops it without any of its own code running and keeps every file. Nothing is deleted.What it covers and how it works: [the Respira WordPress vulnerability scanner](https://www.respira.press/wordpress-vulnerability-scanner?utm%5Fsource=newsletter&utm%5Fmedium=email&utm%5Fcampaign=hidden-plugin-2026-10). 03 Two minutes, for all your sites. Update the plugin to 9.1.10 or later from wp-admin. Then open the Security page of your dashboard and press **Scan all sites**. It reads and changes nothing, and it goes three sites at a time. The page is part of every paid plan.Of the 67 sites scanned from the dashboard so far, 61 had at least one thing worth a look.Or ask the AI you already use:Run the security audit on my site with a deep scan. Tell me in plain words whether anything is active that the plugin list does not show. Change nothing. [Scan your sites](https://www.respira.press/dashboard/security) The whole story, with three checks you can run by hand: [A WordPress plugin that was active and not in the plugin list](https://www.respira.press/blog/hidden-wordpress-plugin-not-in-plugin-list?utm%5Fsource=newsletter&utm%5Fmedium=email&utm%5Fcampaign=hidden-plugin-2026-10). A scan that finds nothing is evidence, not a guarantee: Respira sees what WordPress can see, not the server. ![Mihai Dragomirescu](https://www.respira.press/authors/mihai-avatar.jpg) Mihai Brașov, Romania |
| --- |

## Get the next letter

One letter when something worth reading has shipped, written by the person who built it. No schedule, no sequence, and one click to leave.

[Explore all Founder notes ](https://www.respira.press/newsletter)
