Attackers Elevate Stealth Tactics Through Deceptive WordPress Backdoors
Cybercriminals have augmented their strategies by implementing inconspicuous backdoors masquerading as authentic WordPress components. This pernicious method ensures uninterrupted administrative access, even after the detection and removal of other malicious software.
Their guise of legitimacy masks a sinister purpose: one backdoor mimics a plugin, while the other camouflages itself as a core file. Together, they establish a robust framework that affords hackers indiscriminate control over the afflicted website.
During a recent analysis of a compromised domain, two nefarious files were discovered; each masquerading as standard WordPress code while covertly manipulating administrator accounts.
The initial malevolent component was identified at ./wp-content/plugins/DebugMaster/DebugMaster.php
.
Veiled as “DebugMaster Pro,” this facade presented seemingly legitimate plugin metadata and archetypal developer annotations. In truth, its contents were heavily obfuscated, teeming with covert routines.
Upon closer examination, this file contained code that clandestinely established a secret administrator user with hardcoded credentials. It further concealed that account by filtering database queries, effectively erasing its trace from the plugin list.
The second file, ./wp-user.php
, resided at the WordPress installation’s root, appearing as yet another benign core file.
While this script was more streamlined in architecture than its counterpart, it exuded equal malevolence. It incessantly monitored for the existence of a specific administrator user.
Should the designated user be present, the script would obliterate and immediately recreate it using the hacker’s known password; if absent, it would simply generate a new account.
This procedure compels WordPress to create a new user named ‘help’ clothed in administrative garb. If the user was already present, the script ensured that its administrator privileges were promptly reinstated.
This cyclical mechanism rendered any attempts to alter or eradicate the account futile.
What Was the Malware Doing?
Both files pursued a singular goal: to perpetuate administrative access for the intruders.
The elaborate backdoor masquerading as DebugMaster Pro established a new administrator upon activation, relaying those credentials to a remote command-and-control hub.
The credentials were encoded into JSON format, subsequently Base64-encoded, and transmitted through an obscured endpoint. This methodology enabled attackers to surveil and harvest login details discreetly.
Simultaneously, the wp-user.php script functioned as an aggressive recovery mechanism. It mandated the continuous creation or restoration of the specified administrator user upon each execution, making manual interventions ineffectual.
Even if site custodians identified dubious accounts and attempted to delete or rename them, the script would reinstate the attacker’s access upon the next page load or scheduled event.
Beyond mere account management, the DebugMaster file injected external JavaScript into each visitor’s session, judiciously excluding administrators and whitelisted IP addresses.
This injected code could serve myriad purposes—redirecting traffic to malignant domains, disseminating spam content, or siphoning visitor data. It also gathered IP addresses of administrators for reconnaissance, either logging them locally or transmitting them back to the attackers.
Analysis of the Malware
The faux DebugMaster Pro plugin epitomizes the manner in which threat actors exploit social engineering and intricate obfuscation techniques.
By emulating a legitimate developmental tool plugin, attackers deflected scrutiny from site administrators, who may dismiss an ostensibly innocuous add-on.
Together, these two files manifested a dual-layered persistence strategy: one layer for deception and remote supervision, the other for brute-force restoration of compromised credentials.
Hiding the backdoor code behind layers of Base64 encoding complicates detection via signature-based scanners.
Filtering hooks obscured any evidence of its existence from the WordPress dashboard, while its remote logging channel assured that attackers received real-time alerts about new administrator accounts.

In parallel, the wp-user.php backdoor exhibited a straightforward yet effective mechanism for persistence. Eschewing complex evasion tactics, it guaranteed that the attacker’s selected account could never be permanently expunged.
This brute-force strategy for account maintenance indicated that even a proficient administrator would struggle to outmaneuver the script without first identifying and eliminating the malicious file itself.
This hybrid approach allowed attackers to remain entrenched within the WordPress site indefinitely, evading eradication efforts while maintaining comprehensive oversight.
Website proprietors are compelled to meticulously audit all plugin directories and core files for unauthorized modifications, activate file integrity monitoring, and enforce stringent reviews of administrative accounts to fortify defenses against these sophisticated and clandestine malware campaigns.
Source link: Gbhackers.com.