China-Linked Hackers Rebuild EggStreme Malware Within Weeks of Being Exposed
A suspected Chinese advanced persistent threat (APT) group has rebuilt parts of its EggStreme malware framework after security firm Bitdefender exposed it. Bitdefender said the timing suggested its original report, published in September 2025, was a likely trigger. The update made no new attribution claim.
In that first report, Bitdefender found the group had compromised a Philippines-based military firm using EggStreme, a fileless framework. The company now assesses with high confidence that the operation targeted multiple Philippine government organisations. It has low to medium confidence that Taiwan was also targeted, and calls that a lead rather than an established fact.
The changes came fast. A build of the EggStremeFuel component compiled 12 days after the report protected its configuration differently. Two weeks later, the operators compiled a loader with a new cipher and payload format, and replaced that cipher again by late October 2025. Bitdefender said these swaps offered little real protection but still defeated detections built for the old cipher. The EggStremeAgent backdoor moved to raw TCP connections secured with mutual TLS. Newer builds added Windows domain mapping and in-memory PowerShell, and two ran in passive mode, waiting for operators to connect in. Bitdefender said the framework's design, which lets operators swap capabilities with a new build, appeared to explain the speed.
Despite the rebuild, four behaviours stayed constant: DLL sideloading, movement through file shares, in-memory execution and mutual TLS. Bitdefender said the operators "spent at the tools level and kept their methods." That gives defenders something more durable to detect than file signatures.
Why it matters
Detections tied to specific files, ciphers or indicators failed quickly here, because the operators changed them within weeks of publication. Any organisation relying mainly on signature-based tooling or published indicators of compromise is exposed to this kind of rebuild. The stable behaviours (DLL sideloading, file share movement, in-memory execution, mutual TLS) are the better place to invest detection effort.
What to do
- Restrict built-in Windows tools that your environment does not need.
- Detect DLL sideloading by checking library names and locations.
- Find unmanaged machines that can still reach workstations.
- Watch for new inbound listeners on workstations, as some builds wait passively for operators to connect.