RedXOR
- Type
- Backdoor
- Capabilities
- PersistenceDefense evasionReconnaissancePost exploitation
- Platforms
- Linux
RedXOR is a Linux backdoor assessed to be linked to Chinese state-sponsored activity, based on victimology, operational tradecraft, and code similarities with malware associated with the Winnti ecosystem. It masquerades as a legitimate policy-management daemon and uses the Adore-ng Linux kernel-module rootkit to conceal its process. RedXOR establishes persistence through system initialization service entries and runs detached in the background. Its configuration, including command-and-control settings, is stored encrypted in the binary. The backdoor communicates over TCP using XOR-based data encoding and traffic formatted to resemble HTTP. It provides system reconnaissance, file-management, pseudo-terminal shell access, self-update and uninstall functions, rootkit installation, and network port-mapping functionality implemented using a modified Rinetd component. RedXOR targets Linux endpoints and servers.
Associated threat actors
2 distinct threat actors Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.
We named it RedXOR for its network data encoding scheme based on XOR. Based on victimology, as well as similar components and Tactics, Techniques, and Procedures (TTPs), we believe RedXOR was developed by high profile Chinese threat actors.
The group uses a variety of TTPs including but not limited to LoTL tactics, phishing, ransomware, cryptocurrency mining, supply chain attacks, China Chopper, Gh0st RaT, PlugX, HighNoon, Derusbi, BioPass RAT, RedXOR, and ShadowPad.
Techniques & procedures
16 distinct techniques documented for this family, organized by ATT&CK tactic.
Execution
2 techniques
Execution
If a shell is requested via the command code 3000, the malware creates a new thread executing “/bin/sh”.
In the new spawned shell, the malware executes python -c "import pty;pty.spawn('/bin/sh')” to get a pseudo-terminal (pty) interface.
Persistence
1 technique
Persistence
After installing the binary to the hidden folder, the malware sets up persistence via “init” scripts. The following files are created after executing the malware on boot: /usr/syno/etc/rc.d/S99po1kitd-update.sh /etc/init.d/po1kitd-update /etc/rc2.d/S99po1kitd-update
Privilege Escalation
1 technique
Privilege Escalation
After installing the binary to the hidden folder, the malware sets up persistence via “init” scripts. The following files are created after executing the malware on boot: /usr/syno/etc/rc.d/S99po1kitd-update.sh /etc/init.d/po1kitd-update /etc/rc2.d/S99po1kitd-update
Stealth
5 techniques
Stealth
“LKM rootkits leverage different kernel features to hook kernel functions” and are used “to hide malicious activity by hooking execution flow.”
A 2.7 MB ELF binary with near-maximum entropy (7.997 bits per byte across ~832 KB of code). The obfuscation isn't packing -- it's a custom code virtualizer or instruction-level transformation that renders static analysis effectively impossible without dedicated devirtualization tooling.
The backdoor masquerades itself as polkit daemon.
If this fails, it executes an “mv” shell command via the “system” function
It does this to create a hidden folder, called “.po1kitd.thumb”, inside the user’s home folder which is used to store files related to the malware.
Credential Access
1 technique
Credential Access
The most operationally significant capability is the backdoor's access to cloud instance metadata at 169.254.169.254 . This is the link-local address that every major cloud provider uses to serve instance credentials, API tokens, and configuration data to running workloads.
Discovery
2 techniques
Discovery
The C2 server responds with the command code 0 to collect system information.
2049 List folder
Command and Control
5 techniques
Command and Control
The backdoor encodes its network data with a scheme based on XOR.
The malware communicates with the C2 server over a TCP socket. The traffic is made to look like HTTP traffic.
Network tunneling is enabled by sending the command code 4001 to the malware.
Both have file uploading and downloading functionalities together with a running shell.
the new controller is its continued use of the legacy RC4-MD5 encryption routine... a lightweight encryption layer applied to the interactive command-and-control channel after the backdoor is activated.
Observables
5 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
Recent activity
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.