EggStreme malware rebuilt after exposure

Security researchers say the hacking group behind the EggStreme malware framework has rebuilt its toolkit after being exposed, changing how the malware communicates and adding a version that waits silently for its operators instead of calling out to them.
Bitdefender published the update on 18 November 2026, following up its first EggStreme research from September 2025. That earlier work described how the framework had been used against a military company in the Philippines. The company now assesses, with high confidence, that the operation continues to target several Philippine government organisations. It also found signs of possible targeting in Taiwan, but rated that link low to medium confidence and called it a lead rather than an established fact.
Bitdefender made no new claim about who runs the operation, describing it as a suspected Chinese advanced persistent threat group. Attribution, it said, was a technical assessment based on the available evidence, not a statement about any government.
What the operators changed
The rebuild began quickly. Twelve days after Bitdefender's September report, the operators compiled a new build of EggStremeFuel, the component that profiles a system and deploys the next stage, with a different way of protecting its configuration. Two weeks later came a loader with new cryptography and a new payload format, moving from the RC4 cipher to RC5 and then to a custom cipher by the end of October 2025.
The main backdoor, EggStremeAgent, also changed. It dropped its earlier protocol in favour of raw TCP connections that still use mutual TLS, in which both sides present certificates. Newer builds added commands for mapping Windows domains, querying systems through Windows Management Instrumentation, forwarding TCP traffic, and running PowerShell, portable executable and .NET payloads in memory.
Two of the newer agent builds run in passive mode. Instead of beaconing out to a command-and-control server, they open a listening port and wait for the operator to connect. Bitdefender said the change, together with the new protocol and the expanded command set, was designed to defeat the static signatures and heuristic detections built around the framework when it was first exposed.
The keylogger is gone, but not retired
None of the newer agent builds analysed carried the keylogger that was part of the original framework. Bitdefender cautioned against reading too much into that absence. The keylogger is a separate component, and its absence reflects what the operators chose to compile into those builds, so it should not be taken as evidence that the tool has been retired. The same applies to EggStremeWizard, a secondary backdoor used alongside the main agent: there is no evidence at this stage that it has been discontinued.
The operators also appear to be moving away from the single certificate authority that once tied their servers together. That authority, created in 2019, was linked to 32 domains, and no new domains appeared under it after Bitdefender's report. The shift to campaign-specific certificate authorities is unconfirmed, though some links between the old and new infrastructure remain.
How the attacks still work
Despite the rebuild, four behaviours stayed constant: DLL sideloading, in which a legitimate program is tricked into loading malicious code; movement through file shares; running code from memory; and requiring mutual TLS. Bitdefender said the operators changed their tools but kept their methods.
How the attackers first get in remains unknown. Bitdefender said its first investigation began with a logon script on a network share, and it could not determine how that script got there. In later activity, the operators used valid credentials and a script staged on a host the victim organisation did not manage. That shows how they moved once inside, not how they got in.
Newer incidents also use an unmanaged system, reachable by other workstations but outside the organisation's endpoint management, to stage payloads and launch them through DLL sideloading using a Visual Basic Script file run remotely over Server Message Block.
Bitdefender summed up the lesson for defenders in its report: "The EggStreme operators did more than rotate - the agent we now see uses a different network protocol, has an enhanced command set, and comes in a passive variant that never beacons out." Its advice includes restricting built-in Windows tools that an environment does not need, watching for DLL sideloading by library name and location, finding unmanaged machines that can still reach workstations, and watching for new inbound listeners on workstations.