In August 2025, a buyer acquired the Essential Plugin portfolio, formerly known as WP Online Support, through the website marketplace Flippa. The new owner then added a hidden backdoor to more than 30 of those WordPress plugins. The code stayed quiet until April 2026, when it started injecting hidden SEO spam and visitor redirects into affected sites.

What is going on

Plugins update themselves from WordPress.org, and site owners trust whoever publishes them. When a plugin changes hands, that trust transfers to the new owner automatically. In this case the new owner used it to ship malicious code to every site that installed the update.

The planted code was a deserialization backdoor. In plain terms, the plugin accepted data from outside and turned it back into live instructions, which let an attacker run commands on the site. It sat dormant for months before switching on.

It is a bit like buying a chain of hardware shops and quietly keeping a copy of every key you ever sold. Nothing happens for a while, and then one day all the doors open at once.

Once active, the backdoor wrote code into wp-config.php, the core settings file of a WordPress site. From there it served hidden spam links and sent some visitors to other sites.

Who is affected

WordPress.org closed 31 plugins from the Essential Plugin and WP Online Support range and pushed a forced update to installed sites. That update removed the backdoor code from the plugins themselves.

It did not clean sites that were already infected. Any WordPress site that had one of these plugins installed should be treated as possibly compromised, regardless of size or type.

What to do now

  1. Check your plugin list for anything published by Essential Plugin or WP Online Support.
  2. Remove or replace those plugins. Deactivating alone is not enough.
  3. Open wp-config.php and look for injected code you do not recognise, especially near the top or bottom of the file.
  4. Look for stray files such as wp-comments-posts.php in your site root and delete anything that is not part of WordPress.
  5. Change your admin passwords and database password, and review user accounts for ones you did not create.

If you have a clean backup from before April 2026, restoring it and reapplying your content is often faster than hunting for leftovers.

How to check your own site

Our free Website Security Check flags outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. For a deeper look at a site you own, you can run a full scan, which adds WordPress deep scans and exposed-file and secret checks against sites whose ownership you verified.

Source: BleepingComputer, April 2026.