Executive Summary
QiAnXin XLab has disclosed a previously undocumented Linux backdoor named CWPdoor, designed to operate inside Control Web Panel (CWP), a web-based server administration platform used to manage Linux hosting environments.
The investigation began on June 29, 2026, when QiAnXin's Cyber Threat Insight and Analysis System (CTIA) identified a suspicious update script named cwpsrv_update.sh. The script downloaded a replacement cwpsrv binary from an external server and installed it over the existing Control Web Panel management web server.
Further analysis revealed that the replacement binary contained malicious code capable of executing attacker-supplied commands through specially crafted HTTP/HTTPS requests. Unlike conventional backdoors that continuously communicate with a command-and-control server, CWPdoor remains passive during normal operation and activates only when it receives a request containing three specific HTTP headers and a valid digital signature.
The backdoor incorporates multiple stealth mechanisms, including:
Suppression of access logs for malicious requests.
Preservation of original file and directory timestamps.
Removal of shell command history.
Encrypted command execution and response handling.
Execution through a separate helper process communicating over a Unix domain socket.
QiAnXin identified two CWPdoor samples targeting cwpsrv versions 1.15.10 and 1.24.0. The researchers also reported a sample uploaded to VirusTotal on September 30, 2026, from Brazil, indicating that the malware was present outside a purely experimental environment.
The initial infection and distribution mechanism remains unknown. QiAnXin has not established a connection between CWPdoor and the Ebury backdoor found in the same submitted archive.
Technical Description
CWPdoor is not a standalone executable installed alongside the legitimate server software. Instead, its malicious functionality is embedded directly into the legitimate cwpsrv binary through source-code modification and recompilation.
Control Web Panel is a free, open-source hosting management platform for CentOS and other Linux distributions. Its dedicated management web server, cwpsrv, is based on a customized Nginx implementation and serves the control panel interface and associated applications.
By replacing this binary, the attacker can maintain a backdoor within a process that administrators would ordinarily consider legitimate.
The malicious binary behaves like the original server under normal conditions. Its backdoor functionality is activated only when the incoming HTTP request satisfies the attacker's authentication and validation requirements.
QiAnXin reported that more than 340,000 CWP instances were exposed to the internet during the preceding month. This figure represents potentially exposed systems, not confirmed infections.
Attack Overview
1. Malicious Update Script Discovery
On June 29, 2026, QiAnXin identified a suspicious Bash script named:
cwpsrv_update.sh
The script masquerades as a server update mechanism and downloads a replacement cwpsrv binary from:
136.0.141[.]71
The script supports specific CWP server versions, including 1.15.10 and 1.24.0, and requires root privileges to perform the replacement.
Its execution sequence includes:
Checking the locally installed
cwpsrvversion.Downloading the corresponding malicious binary.
Verifying that the downloaded binary matches the expected version.
Backing up the existing legitimate executable.
Stopping the
cwpsrvservice.Replacing
/usr/local/cwpsrv/bin/cwpsrvwith the malicious binary.Restarting the service and checking the master, worker, and helper processes.
Rolling back the replacement if the health check fails.
If installation succeeds, temporary files and the backup are deleted.
2. File Timestamp Manipulation and Evidence Removal
The update script incorporates additional techniques to reduce the likelihood of detection during routine system checks.
It restores the original access and modification timestamps of the replacement binary and its parent directory. Consequently, commands such as ls and stat may not reveal that the legitimate executable was replaced.
The script also executes:
history -d
This removes the current command from the shell history, reducing the available evidence of the installation activity.
These techniques make timestamp-based investigations and routine command-history reviews less reliable.
3. Passive HTTP Backdoor Activation
Once installed, CWPdoor waits for specially crafted HTTP/HTTPS requests.
The attacker must provide three specific HTTP headers:
| HTTP Header | Purpose |
|---|---|
X-Ngx-Integrity-Time | Carries the request timestamp |
X-Ngx-Integrity-Data | Contains the encrypted command |
X-Ngx-Integrity-Sig | Contains the Base64-encoded RSA digital signature |
The backdoor validates the request timestamp against a window of approximately ±300 seconds.
It then verifies the RSA signature using a public key embedded within the malicious binary. The signed data consists of the timestamp and encrypted command values.
If validation fails, the request is handled as ordinary web traffic. If validation succeeds, the backdoor proceeds with command execution.
This mechanism provides a controlled activation channel and makes arbitrary unauthenticated requests insufficient to trigger the malicious functionality.
4. Encrypted Command Execution
After successful validation, CWPdoor decrypts the supplied command and forwards it to a separate helper child process through a Unix domain socket.
The malware uses the following communication mechanism:
The encrypted command is Base64-encoded.
The first 16 bytes after decoding contain the AES initialization vector.
The remaining bytes contain AES-256-CBC ciphertext.
The AES key is derived from the SHA-256 digest of the embedded RSA public key string.
The helper process executes the command and returns the result to the main process.
The output is encrypted and delivered to the attacker in an HTTP 200 response with the content type application/octet-stream.
This creates a bidirectional encrypted command channel operating through ordinary web traffic.
5. Access Log Suppression
One of CWPdoor's most significant capabilities is its ability to suppress logging of malicious requests.
The backdoor modifies the request's module context array and replaces the context pointer associated with the logging module. This prevents the malicious request from being recorded through the normal access-logging mechanism.
As a result, administrators may not find the corresponding command-execution request in standard web access logs.
The combination of passive activation, valid digital signatures, encrypted command traffic, and access-log suppression significantly complicates detection and forensic investigation.
Indicators of Infection and Detection
QiAnXin identified several host-level indicators that administrators can use to investigate potentially compromised CWP servers.
1. Unix Domain Socket
CWPdoor uses the following Unix domain socket for communication between its main process and helper process:
ngx_http_integrity_helper
Run the following command to check for the socket:
ss -axp | grep integrityInvestigate any unexpected matching socket, including the associated process and service context.
2. Suspicious Helper Processes
Check for suspicious helper processes associated with cwpsrv:
ps aux | grep cwpsrvReview unexpected child processes and determine whether they are associated with legitimate CWP functionality.
3. Malicious Binary Strings
Search the cwpsrv executable for strings associated with the backdoor:
strings /usr/local/cwpsrv/bin/cwpsrv | grep X-Ngx-IntegrityThe presence of unexpected X-Ngx-Integrity strings is a useful investigation lead.
4. Binary Integrity Verification
Compare the installed cwpsrv executable against a trusted copy of the corresponding vendor-provided version.
Investigate:
Unexpected binary changes.
Differences in executable hashes.
Unusual backup files.
Unexpected modifications to the CWP service.
Unexplained process and service restarts.
Do not rely exclusively on file timestamps because the deployment script deliberately restores timestamp values.
Indicators of Compromise (IOCs)
The following indicators were published by QiAnXin XLab.
Network Indicators
| Indicator | Type | Description |
|---|---|---|
136.0.141[.]71 | IPv4 | Downloader and update infrastructure |
Downloader URLs
| URL | Description |
|---|---|
http://136.0.141[.]71/static/cwpsrv_update.sh | Malicious update script |
http://136.0.141[.]71/static/cwpsrv_1.15.10 | Malicious cwpsrv binary for version 1.15.10 |
http://136.0.141[.]71/static/cwpsrv_1.24.0 | Malicious cwpsrv binary for version 1.24.0 |
File Hashes
| MD5 | File | Description |
|---|---|---|
e505d4ffa21cf494a5dc2d7c8f4f1236 | cwpsrv_update.sh | Malicious Bash deployment script |
965aea67fb40de1bab5169ada993349f | cwpsrv_1.15.10 | CWPdoor-enabled Linux binary |
d3f4e95113d49ab3991b45e457bda75b | cwpsrv_1.24.0 | CWPdoor-enabled Linux binary |
Host-Based Indicators
| Indicator | Type | Description |
|---|---|---|
ngx_http_integrity_helper | Unix domain socket | Backdoor helper-process communication |
X-Ngx-Integrity-Time | HTTP header | Backdoor request timestamp |
X-Ngx-Integrity-Data | HTTP header | Encrypted command data |
X-Ngx-Integrity-Sig | HTTP header | RSA signature used for request validation |
/usr/local/cwpsrv/bin/cwpsrv | File path | Targeted CWP management server binary |
cwpsrv.prev-* | Backup filename pattern | Backup of the original server binary |
IOC handling note: The IP address and URLs are published indicators associated with the observed deployment activity. Validate their current reputation and historical relevance before applying network blocks. The Unix socket, HTTP header names, and file paths are behavioral investigation indicators rather than standalone proof of compromise.
Potential Impact
Successful deployment of CWPdoor may expose affected Linux hosting environments to significant security risks.
Remote Command Execution: The backdoor allows an attacker with the required signed request to execute commands on the compromised server. Since the deployment script requires root privileges, the resulting access may provide extensive control over the host.
Hosting Environment Compromise: CWP systems often manage websites, DNS, email, and other hosting resources. A compromised management server could expose multiple hosted services and associated data.
Credential Exposure: Attackers with command execution capability may access stored credentials, configuration files, SSH keys, database credentials, and other sensitive information.
Website and Service Manipulation: An attacker may modify hosted websites, configuration files, DNS settings, or other services managed through the compromised control panel.
Stealthy Persistence: Replacing the legitimate cwpsrv binary allows the backdoor to operate within an expected service, while timestamp manipulation and log suppression reduce detection opportunities.
Forensic Challenges: The removal of command history, deletion of temporary installation files, and suppression of access logs may limit the evidence available during incident response.
Recommendations
Immediate Actions
Identify Exposed CWP Systems: Inventory all internet-facing Control Web Panel instances and identify their installed versions and management interfaces.
Check for CWPdoor Indicators: Run the socket, process, and binary-string checks published by QiAnXin. Investigate any matching results before taking remediation action.
Verify
cwpsrvBinary Integrity: Compare the installed executable against a trusted vendor-provided copy. Do not rely solely on timestamps or file metadata.Hunt for Malicious Deployment Activity: Review shell history, process execution telemetry, file creation events, service restart records, and network connections involving
136.0.141[.]71.Review Network Telemetry: Search historical firewall, DNS, proxy, and EDR records for connections to the published downloader IP and URLs.
Restrict Management Access: Ensure CWP administrative interfaces are not unnecessarily exposed to the public internet. Restrict access to trusted management networks and authorized source addresses.
Treat Confirmed Hosts as Compromised: Isolate affected servers where operationally possible and investigate for additional unauthorized accounts, processes, persistence mechanisms, and data access.
Restore Trusted Software: Follow the vendor's supported recovery process and replace the malicious binary with a trusted version. Do not assume that restoring the original binary alone removes every attacker-controlled component.
Rotate Credentials: Immediately rotate CWP administrative credentials and review SSH keys, database credentials, hosting accounts, API tokens, and other secrets that may have been accessible to the attacker.
Preserve Evidence: Capture the suspicious binary, process details, socket information, relevant logs, file metadata, and network telemetry before remediation.
Preventive Actions
Harden Control Panel Exposure: Avoid exposing CWP management interfaces directly to the internet wherever possible. Use VPNs, restricted access lists, or dedicated management networks.
Implement File Integrity Monitoring: Monitor critical CWP binaries and directories, especially
/usr/local/cwpsrv/bin/, for unexpected modifications.Monitor Service Execution: Establish baselines for legitimate
cwpsrvmaster, worker, and helper processes. Alert on unexpected child processes or unusual process relationships.Monitor Unix Domain Sockets: Detect unexpected sockets and investigate those associated with web-server processes, particularly
ngx_http_integrity_helper.Improve Linux Audit Visibility: Enable appropriate audit logging for executable replacement, privilege escalation, shell command execution, service restarts, and sensitive file access.
Monitor Suspicious HTTP Headers: Inspect management-server requests for unexpected
X-Ngx-Integrity-*headers. Correlate these observations with process execution and host-level evidence.Strengthen Egress Controls: Restrict unnecessary outbound connections from hosting servers and monitor unusual communication with external IP addresses.
Maintain Trusted Backups: Keep verified backups of system binaries and configurations, and regularly test recovery procedures.
Patch and Maintain CWP: Keep Control Web Panel and its underlying Linux operating system updated using trusted vendor sources.
Conduct Regular Threat Hunting: Search for binary tampering, unexpected helper processes, suspicious command execution, and abnormal management-server behavior.
MITRE ATT&CK Mapping
| Tactic | Technique ID | Technique |
|---|---|---|
| Initial Access | T1190 | Exploit Public-Facing Application – potential, initial access method unknown |
| Execution | T1059.004 | Unix Shell |
| Persistence | T1505.003 | Web Shell – related server-side backdoor behavior; mapping is contextual |
| Defense Evasion | T1070.003 | Clear Command History |
| Defense Evasion | T1070.006 | Timestomp |
| Defense Evasion | T1562.002 | Disable Windows Event Logging – not applicable; do not use for this Linux logging behavior |
| Command and Control | T1071.001 | Web Protocols |
| Command and Control | T1573.001 | Encrypted Channel: Symmetric Cryptography |
| Lateral Movement | Not established | No lateral movement behavior reported in the research |
The mappings above are behavioral suggestions. CWPdoor's initial access vector is unknown, and its custom logging suppression should not be treated as a confirmed match to a Windows-specific ATT&CK technique.
Conclusion
CWPdoor demonstrates how attackers can compromise a legitimate server-management component and use it as a stealthy command-execution mechanism. By embedding malicious functionality directly into the cwpsrv binary, the backdoor can operate without presenting itself as a separate suspicious executable.
Its use of signed HTTP requests, encrypted command execution, Unix domain socket communication, timestamp manipulation, and access-log suppression makes traditional perimeter monitoring and routine file checks insufficient on their own.
Organizations operating Control Web Panel should prioritize binary integrity verification, host-level investigation, restricted management access, and credential rotation where compromise is suspected.
The reported exposure of more than 340,000 internet-facing CWP instances highlights the importance of reviewing externally accessible server-management infrastructure. Administrators should investigate the published indicators and follow QiAnXin's recovery guidance when CWPdoor is suspected or confirmed.
