Stuart Neal
Director of Operations at Nextgen Marketing
We have worked with Vitalli and his team for well over a year now and will continue to do so in the future.
Having the confidence in an agency that allowed us to scale up and down development resources, as and when needed, has really made a positive difference to our agency.
Home / Blog / News / A fake Cloudflare check can install a WordPress backdoor using your own admin session
Securonix Threat Research published its analysis of an attack chain it calls TRUST#GRAFT on 22 October, and it has been circulating through the security press since. It deserves a second look from anyone managing WordPress sites for clients, because it does not break WordPress authentication at any point — it waits for an administrator who is already logged in, and uses that session against them. That is the kind of thing nobody catches by reading a changelog, and the reason a standing integrity check on the sites you manage is worth more than another scanner.
The loader runs as injected JavaScript on a compromised page:
Every one of those requests carries the administrator’s own same-origin cookies and a nonce WordPress itself issued. From the application’s point of view, an admin installed a plugin. Because that is literally what happened.
`wm.zip` contains a PHP plugin presenting as Web Media Optimizer, version 2.1, with a performance-oriented description. It is a backdoor. On activation it:
The `GRAFT` half of the name is the mu-plugins copy. Delete the visible plugin directory and the site is still backdoored. Securonix is explicit that a complete cleanup has to check `wp-content/mu-plugins` directly and confirm no equivalent copy remains.
Reported infrastructure includes `caapman[.]me`, `vtevens[.]icu`, `gerlace[.]com`, `nutmann[.]club` and `okuneva[.]sbs`, with the payload consistently at `/p/wm.zip`.
TRUST#GRAFT targets one specific working pattern: staying logged into wp-admin in the same browser profile used for ordinary browsing. Reviewing a client’s live site in one tab, wp-admin in another, research and links in a third. That is a normal Tuesday for most people who do this work, and it is the whole precondition for the attack.
Which makes the mitigation unusually cheap:
There is no vulnerable version number to compare against, so a plugin audit will not flag it. The upload looks like legitimate admin activity in access logs. The proof-of-work gate means scanning the compromised page from a server will often return nothing. The plugin hides from the Plugins screen. The realistic detection points are file-level: a new file in mu-plugins, an unexpected `POST` to `update.php?action=upload-plugin`, or outbound requests to `/p/wm.zip`.
That is a monitoring problem, not a patching problem — which is the uncomfortable part, because patching is the bit most agencies have covered and monitoring is the bit they do not.
If you are on one of our maintenance plans, file integrity monitoring already covers the must-use plugin directory and unexpected plugin installs, admin session and credential hygiene is part of the standing routine, and anything found gets written up in your monthly maintenance report. Nothing is needed from you on this one. If you are not on a plan, this is the category of problem the plan exists for: an attack that leaves the plugin list, the version numbers and the uptime graph all looking perfectly normal, and only shows up if somebody is actually watching the files.
Source: Securonix