Web threats / PHP backdoors

wPanel PHP backdoor

wPanel is a WordPress backdoor agent that hides as locale files, keeps several ways back in and deletes rival web shells. We have matched it on 3 sites since 18 October.

wPanel in numbers

Since 18 October, the first wPanel match in our records, counted on 16 November 2026. How we count.

Sites with wPanel code3
Sites with a match in the last 30 days3
New sites in October1
Sites running WordPress (captured since 25 September)67%

The dropper is pasted into an active plugin

wPanel names itself. The block opens with // WPANEL:BEGIN, carries wpanel-agent-version: 2.0.6 on every site we found it on, and closes with // WPANEL:END-AGENT. Its first comment, in Turkish, tells the operator to paste it only into the active plugin's PHP file and to leave no closing PHP tag at the end.

We found it because the sites leaked it. On each one, a broken theme or plugin printed the PHP as page text, so the backdoor's source sits in the HTML anyone can load.

The dropper dresses as WordPress locale code. A function called _wp_locale_pack_decode reads a blob named $_wp_i18n_blob with a reordered Base64 alphabet, decrypts it with AES-256-CBC using a key and IV that ship in the same file, and inflates it with gzinflate. The result, about 96 KB of PHP, is the agent.

The agent hides in several places at once

The dropper writes the agent to every one of these paths and loads the first that works:

wp-content/languages/class-wp-locale-switch.php
wp-content/upgrade/class-wp-locale-switch.php
wp-content/cache/class-wp-locale-switch.php
wp-content/languages/class-wp-locale-data.php
wp-content/upgrade/class-wp-locale-data.php
wp-content/cache/class-wp-locale-data.php
wp-content/.wpanel/agent.php

From there it adds more ways back: a must-use plugin, a db.php drop-in, an advanced-cache.php snippet, a loader in the theme's functions.php, and a bootstrap under uploads/wp-locale-cache/. A WordPress cron heartbeat checks them and restores any that were removed. Deleting one copy leaves the rest to put it back.

It reports to a panel and works the site

The agent registers with its panel at /agent/register and reports at /agent/event, on a domain one letter off wordpress.com. The agent only acts on panel commands carrying an RSA signature it checks against a public key it ships with. The commands are plain: list, read, write, rename and delete files, upload and deploy new PHP, list plugins and users, create and delete users, change a user's role, and return the database name, user, password and host from wp-config.php.

It also cleans house. wpanel_cleanup_malware deletes a fixed list of other attackers' files, among them shell.php, wso.php, alfa.php, yakala.php, rootseo.php and nox-google-bot-bypass.php, and removes hidden admin accounts such as wp_hiddenbot that other kits create. Whoever installs wPanel wants the site to themselves.

What we see

MonthNew sites
September0
October1
November so far2

67% of wPanel sites captured since 25 September run WordPress.

Checking a site

Search plugin and theme files, and the page HTML for leaked source, for:

  • WPANEL:BEGIN, wpanel-agent-version or wpanel_agent_start
  • _wp_locale_pack_decode and $_wp_i18n_blob
  • class-wp-locale-switch.php or class-wp-locale-data.php under languages, upgrade or cache in wp-content
  • a wp-content/.wpanel/ folder
  • an unexpected must-use plugin, db.php drop-in or advanced-cache.php

Remove every copy and every loader in one pass, then check WordPress cron for the heartbeat event, or the agent restores itself. Rotate all administrator passwords and check for users you did not create.

Try the feed for 14 days.

Request a trial and we'll send you a live API key, with the same feed, removals and reasons a customer gets.