<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3" -->

---
title: Malcious Admin Menu Editor Pro plugin backdoors 1,500...
description: A threat actor compromised the maintainer website of the Admin Menu Editor Pro WordPress plugin and pushed malicious updates (versions 2.35 and 2.36) that...
canonical: https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites | daily.dev
og:description: A threat actor compromised the maintainer website of the Admin Menu Editor Pro WordPress plugin and pushed malicious updates (versions 2.35 and 2.36) that...
og:url: https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3
og:image: https://api.daily.dev/og/posts/HQ55UqlR3.png
og:image:alt: Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites

**[BleepingComputer](https://daily.dev/sources/bleepingcomputer)** · 3 min read · 0 upvotes · 0 comments

## Summary

A threat actor compromised the maintainer website of the Admin Menu Editor Pro WordPress plugin and pushed malicious updates (versions 2.35 and 2.36) that installed a web shell and created a hidden admin user on affected sites. About 230 customers running roughly 1,500 sites installed the trojanized 2.35 build before it was pulled, and the attacker also managed to compromise the subsequent 2.36 release. Signs of compromise include a wp-user-consent.php file, a new object-cache directory, and hidden wp_ prefixed users and options. The developer recommends restoring from a pre-September-14 backup or manually removing the malicious files and database entries; version 2.34 and the free plugin are believed unaffected.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.bleepingcomputer.com/news/security/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites>

## Questions this post answers

### How do I know if my WordPress site was affected by the Admin Menu Editor Pro backdoor?

Check for an includes/wp-user-consent.php file in the admin-menu-editor-pro directory, a new /wp-content/object-cache/ directory, a hidden user beginning with wp_ in the wp_users table, and options named like wp_ocache* in the wp_options table. These indicate the trojanized Admin Menu Editor Pro version 2.35 or 2.36 was installed, which created a hidden admin account and web shell.

_Teams tracking plugin supply-chain risks follow incident writeups like this on daily.dev._

### What versions of Admin Menu Editor Pro were compromised in the supply chain attack?

Versions 2.35 and 2.36 of Admin Menu Editor Pro were compromised after a threat actor gained unauthorized, likely root-level, access to the maintainer's website and pushed malicious updates. Version 2.35 was available for download from roughly 06:00 to 13:00 UTC before being pulled, but the attacker also tampered with the replacement version 2.36 released later that day. Version 2.34 and the free Admin Menu Editor plugin are believed to be unaffected.

_Anyone auditing plugin versions after a breach can track fixes like this via daily.dev._

### How do I remove the Admin Menu Editor Pro backdoor from a compromised WordPress site?

The most reliable fix is restoring the site from a safe backup made before September 14. If no clean backup exists, delete the plugin, remove the /wp-content/object-cache/ directory, and delete the hidden wp_ prefixed user in wp_users along with the wp_ocache* entries in wp_options. The attacker had likely root-level server access, so a full server review is also advisable.

_Developers cleaning up after plugin compromises can find remediation steps like this on daily.dev._

## Similar posts on daily.dev

- [BdThemes plugins supply-chain hack creates rogue WordPress admins](https://daily.dev/posts/bdthemes-plugins-supply-chain-hack-creates-rogue-wordpress-admins-lfahg18ig) · BleepingComputer · 0 upvotes · 0 comments
- [Someone Bought 30 WordPress Plugins and Planted a Backdoor in All of Them.](https://daily.dev/posts/someone-bought-30-wordpress-plugins-and-planted-a-backdoor-in-all-of-them--zu6yjzajf) · Hacker News · 1 upvotes · 0 comments
- [Smart Slider updates hijacked to push malicious WordPress, Joomla versions](https://daily.dev/posts/smart-slider-updates-hijacked-to-push-malicious-wordpress-joomla-versions-umc8mytqf) · BleepingComputer · 0 upvotes · 0 comments

---

Tags: [#cyber](https://daily.dev/tags/cyber), [#php](https://daily.dev/tags/php), [#wordpress](https://daily.dev/tags/wordpress), [#malware](https://daily.dev/tags/malware)

[View this post on daily.dev](https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites","url":"https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3"},"datePublished":"2026-09-15T20:35:37.244Z","dateModified":"2026-09-15T21:56:25.877Z","description":"A threat actor compromised the maintainer website of the Admin Menu Editor Pro WordPress plugin and pushed malicious updates (versions 2.35 and 2.36) that...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d040d47671f8c2bff66ec16f2ec14421?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d040d47671f8c2bff66ec16f2ec14421?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"BleepingComputer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"BleepingComputer","logo":"https://media.daily.dev/image/upload/s--as8nJ3qy--/f_auto,q_auto/v1774959951/logos/bleepingcomputer?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bleepingcomputer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cyber,php,wordpress,malware","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"BleepingComputer","item":"https://daily.dev/sources/bleepingcomputer"},{"@type":"ListItem","position":3,"name":"Malcious Admin Menu Editor Pro plugin backdoors 1,500 WordPress sites"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/malcious-admin-menu-editor-pro-plugin-backdoors-1-500-wordpress-sites-hq55uqlr3#faq","mainEntity":[{"@type":"Question","name":"How do I know if my WordPress site was affected by the Admin Menu Editor Pro backdoor?","acceptedAnswer":{"@type":"Answer","text":"Check for an includes/wp-user-consent.php file in the admin-menu-editor-pro directory, a new /wp-content/object-cache/ directory, a hidden user beginning with wp_ in the wp_users table, and options named like wp_ocache* in the wp_options table. These indicate the trojanized Admin Menu Editor Pro version 2.35 or 2.36 was installed, which created a hidden admin account and web shell. Teams tracking plugin supply-chain risks follow incident writeups like this on daily.dev."}},{"@type":"Question","name":"What versions of Admin Menu Editor Pro were compromised in the supply chain attack?","acceptedAnswer":{"@type":"Answer","text":"Versions 2.35 and 2.36 of Admin Menu Editor Pro were compromised after a threat actor gained unauthorized, likely root-level, access to the maintainer's website and pushed malicious updates. Version 2.35 was available for download from roughly 06:00 to 13:00 UTC before being pulled, but the attacker also tampered with the replacement version 2.36 released later that day. Version 2.34 and the free Admin Menu Editor plugin are believed to be unaffected. Anyone auditing plugin versions after a breach can track fixes like this via daily.dev."}},{"@type":"Question","name":"How do I remove the Admin Menu Editor Pro backdoor from a compromised WordPress site?","acceptedAnswer":{"@type":"Answer","text":"The most reliable fix is restoring the site from a safe backup made before September 14. If no clean backup exists, delete the plugin, remove the /wp-content/object-cache/ directory, and delete the hidden wp_ prefixed user in wp_users along with the wp_ocache* entries in wp_options. The attacker had likely root-level server access, so a full server review is also advisable. Developers cleaning up after plugin compromises can find remediation steps like this on daily.dev."}}]}
```

