BlackTech is deploying a customized BlueShell backdoor for post-compromise operations on Linux systems, hiding it as a fake kernel worker process to evade detection and complicate forensic analysis.
This variant adds proxy-aware C2, host validation, and anti-analysis features that go beyond the original open-source BlueShell RAT.
BlueShell is an open-source remote access trojan (RAT) written in Go that offers attackers remote shell access, file upload/download, and SOCKS5 proxy capabilities over a command-and-control (C2) channel.
Infected hosts can be fully operated through the C2 server, enabling lateral movement, data exfiltration, and persistent access across compromised networks.
Recent analysis shows that an advanced persistent threat (APT) group, including the China-linked BlackTech, is leveraging a Linux-focused BlueShell variant in their post-intrusion toolchain.
This variant maintains the core RAT functionality but introduces campaign-specific features such as custom configuration handling, proxy-aware C2 communications, and stealth mechanisms that are not present in the original public BlueShell project.
BlackTech Masks BlueShell Backdoor
Operationally, the malware is deployed after initial access, typically via SSH-based lateral movement onto targeted Linux hosts.
The attackers drop and execute a dedicated “dropper” binary, which is responsible not only for unpacking and running the BlueShell variant but also for managing configuration delivery and implementing anti-forensic techniques.

This staged approach lets BlackTech separate the visible delivery component from the more ephemeral payload, reducing the artifacts left behind after execution.
The dropper embeds the BlueShell variant in its own data section as a large blob of encoded and compressed data.
When executed, it copies this embedded data, applies XOR decoding with a fixed key, and then decompresses it using the FastLZ algorithm.
The resulting payload is written to a temporary path such as /tmp/kthread, which serves as the executable for the BlueShell variant.
Before launching the payload, the dropper sets an environment variable (wtim) containing Base64-encoded and XOR-obfuscated configuration data.
This configuration includes parameters such as the C2 IP address and port (for example, an HTTPS service on port 443), sleep intervals for reconnection attempts, hostname filters, and enterprise proxy settings (address, port, optional credentials, and flags indicating whether to use and authenticate via the proxy).

The BlueShell variant decodes and parses this data at runtime, allowing operators to adjust campaign parameters without recompiling the malware.
To evade casual inspection, the dropper executes the BlueShell variant with a forged argv[0] value such as [kworker/12:12], causing the running process to appear as a Linux kernel worker thread in process listings.
After spawning the process, the dropper deletes the /tmp/kthread binary, ensuring no straightforward file remains on disk that directly corresponds to the running process, sect.iij said.
On a live system, investigators may see what looks like a kernel worker in tools such as ps, but /proc/PID/exe reveals an anonymous or deleted executable rather than a legitimate kernel component, making detection and analysis significantly more difficult.
Cut SOC investigation blind spots and contain threats earlier to reduce response costs and business disruption with ANY.RUN.