WordPress maintenance Hacked site cleanup Security plugin Pricing Security tips
Home / Security tips / Website security
October 27, 2026

Fake Cloudflare Check Can Install a WordPress Backdoor

You open your site while still logged in to /wp-admin/. A screen says it’s checking your browser. Behind that fake Cloudflare check, your browser may be installing a WordPress backdoor you never approved.

That’s the trick described in Securonix Threat Research’s report on TRUST#GRAFT. It isn’t a WordPress bug or an authentication bypass. The attacker needs a browser already logged in to the same site as an administrator who can install plugins. Your own session does the work.

How a browser check turns into a plugin install

Malicious JavaScript covers the real page with a full-screen frame made to look like a Cloudflare-style “Just a moment…” check. While you wait, it checks the browser for signs of automation or analysis tools.

Then it tests whether your session can reach /wp-admin/. If it can, the script opens the plugin upload page, reads its security nonce, downloads a ZIP called wm.zip from an attacker-controlled server, and uploads it through WordPress’s normal plugin upload process. It requests the normal activation link too. To WordPress, this looks like an administrator installing a plugin, because the requests come from that administrator’s browser.

The script also searches localStorage and sessionStorage for values with names suggesting tokens, API keys, or sessions. It sends those values, plus up to 1,500 characters of browser-readable cookies, to the attacker. JavaScript can’t read HttpOnly cookies. It can read data left in browser-accessible storage.

There’s a second lure: the script can try to put a command on your clipboard for a fake verification step. That doesn’t mean anyone actually pasted or ran it. Still, if a “verify you are human” page asks you to paste something into a terminal or Run box, don’t. No genuine website check needs you to paste commands anywhere.

Why the Plugins screen won’t settle it

The uploaded plugin calls itself Web Media Optimizer, version 2.1. It isn’t an optimizer. It adds attacker-controlled JavaScript to public pages, stores controller settings in WordPress options and transients, and disables TLS certificate checks when fetching its controller URL. A token-gated path can log the attacker in as the site’s first administrator or change which remote script gets loaded.

It hides from the normal plugin list, action links, and update views. So a clean-looking Plugins screen proves very little.

Worse, activation copies the backdoor to wp-content/mu-plugins/wmedia-recovery.php. WordPress loads PHP files in that folder automatically, outside the usual enable-and-disable routine. Deleting only the ordinary plugin folder leaves the copy running. Both copies need to go together.

What nobody knows yet

The report does not establish how the malicious loader first reaches people. A hacked page, injected content, an ad, a theme, a plugin, or a redirect would be guesses. We also don’t know who is behind TRUST#GRAFT, where victims are, or how many sites are affected.


What to check on your site

You don’t need to recognise the fake screen. Check what the attack would leave behind. If you’re unsure what belongs on the site, ask whoever maintains it before deleting anything.

  1. Look in the files. Use your hosting file manager or SFTP to open wp-content/mu-plugins. It may not exist, or it may contain files you or your host knowingly put there. Look especially for wmedia-recovery.php. Don’t rely on the ordinary Plugins screen.
  2. Check wp-content/plugins. Look for a folder you didn’t add, including one related to Web Media Optimizer. A missing folder does not clear the site if the MU-plugin copy remains.
  3. Review administrators. Open Users > All Users and check every administrator account you don’t recognise. Pay extra attention to the first administrator account: that’s the account the backdoor’s login path targets.
  4. Check your homepage source. Look for script tags loading from unfamiliar domains. The report names caapman[.]me, vtevens[.]icu, gerlace[.]com, nutmann[.]club, okuneva[.]sbs, and vilialobos[.]lol. The last is the plugin’s default remote script source. These are clues, not a complete blocklist.
  5. Look at activity records, if you have them. A single admin session visiting the plugin upload page, uploading a ZIP, and activating a plugin in quick succession deserves attention. Check times in your host’s logs or logging plugin.
  6. Glance at scheduled tasks. As a general cleanup check, you can list WP-Cron events with wp cron event list if you use WP-CLI. The report does not say this malware creates cron events.

Our free Bearmor malware scanner checks areas including MU plugins, though it doesn’t inspect every file. We haven’t tested it against this exact sample. Treat it as another pair of eyes; checking that folder by hand takes a minute.

Make your admin session harder to borrow

Give WordPress administration its own browser profile, or a separate browser. Don’t open email links, news, or random pages there while you’re logged in. And log out when you’re done. Logging out cuts off the active admin session this attack needs, though it doesn’t erase tokens left in browser storage.

  • Keep administrator accounts to a minimum. Use an Editor account for everyday publishing, and an admin account only for admin work.
  • Limit who can upload plugins and require approval for new installs. If a maintainer handles updates, adding define( 'DISALLOW_FILE_MODS', true ); to wp-config.php blocks dashboard plugin and theme installs and updates. You’ll need SFTP, WP-CLI, or host tools for updates instead. For a DIY owner, that trade-off can be a pain.
  • If your setup supports it, consider a content security policy and script allowlist to restrict public-page scripts. Test before switching on a strict policy.

Keeping the server side current matters too, for a different reason. Our PHP2Shell post explains what to ask your host about critical PHP flaws. Don’t confuse that host-side issue with this browser-mediated attack.

If you find the backdoor

Preserve evidence before cleanup: copy suspicious files and relevant logs if you can. Then remove the ordinary plugin folder and wp-content/mu-plugins/wmedia-recovery.php as one job. Check options and transients for suspicious remote URLs, inspect public pages for injected scripts, and look for anything else that was added. Removing two files isn’t proof the whole site is clean.

Rotate every administrator password, invalidate admin sessions, review accounts, and remove unknown administrators. In your own profile, WordPress offers Users > Profile > Log Out Everywhere Else; changing a password normally ends that account’s other sessions too. Review application passwords and connection keys. We have a separate walkthrough for auditing that access.

If the script ran in your browser, assume browser-stored tokens and API keys might have been exposed and rotate those as well. If you can’t tell whether the site is clean, get help with hacked site cleanup rather than trusting a quick plugin deletion.

Today’s five-minute check: open your file manager, find wp-content/mu-plugins, and identify every PHP file in it. If you can’t explain one of them, don’t asume it’s harmless.