Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Bitdefender illustration of a cracked egg with a red wireframe bird emerging in a server room, beside a monitor reading hatching.
Image: Bitdefender (fair use). Header illustration from the Bitdefender report "EggStreme Malware: Rebuilt Under Scrutiny," published Nov. 18, 2026.

Threat Intel

Bitdefender Says the Suspected Chinese Group Behind EggStreme Rebuilt Its Malware Within Weeks of Being Exposed, Adding an Implant That Never Calls Home and Waits Behind a Fake Windows Firewall Rule

Twelve days after Bitdefender's first report, the operators targeting Philippine government agencies began changing their configuration format, ciphers, network protocol and server certificates. Their methods did not change, and Bitdefender says those habits are what defenders should now build detections around.

Priya Shah, Threat IntelSingapore6 min read

SINGAPORE - A suspected Chinese state-aligned hacking group that spies on Philippine government agencies responded to being publicly exposed last year by rebuilding most of its malware rather than simply swapping out servers, according to a report released Wednesday by the Romanian security company Bitdefender.

Bitdefender first documented the framework, which it calls EggStreme, on Sept. 17, 2025, describing a mostly fileless toolkit with six named parts, including a backdoor with 58 commands and a keylogger. The new report, written by Bogdan Zavadovschi with contributions from Victor Vrabie, Adrian Schipor and Martin Zugec, says the operators changed how one component protects its configuration in a build compiled 12 days later, changed the loader's cryptography and payload format 14 days after that, and appear to have abandoned the single certificate authority that once tied their servers together.

"When attackers are exposed, the cheap response is to rotate," the report says. "The EggStreme operators did more than rotate."

Bitdefender assessed with high confidence that the operation continues to target Philippine government organizations, with multiple victims, and said with low to medium confidence that Taiwan is also a target. The company did not name victims or give a count, and it made no new attribution claim beyond its original description of a suspected Chinese group.

A rebuild in weeks

The changes landed on a tight schedule. The first EggStremeFuel build with a new configuration format carries a compile date of Sept. 29, 2025. That component now encrypts its settings with AES-256 using a key embedded and obfuscated in the binary, so knowing the file's name no longer helps an analyst decrypt it. The loader moved from the RC4 stream cipher to RC5 in a build dated Oct. 13, 2025, which Bitdefender saw in the wild the next day, and then to a homemade cipher by Oct. 28. Three loader builds were compiled within about 95 minutes of one another that day, which the company read as active development rather than a single release. A second custom cipher appeared by mid-December.

Bitdefender chart plotting compile timestamps of EggStreme Fuel, loader and agent builds from April 2024 to mid-2026, with a dashed line marking the first report and newer-format builds clustered after it, labeled 12 days after and 14 days later.
Image: Bitdefender (fair use).The EggStreme build timeline, showing which changes came before and after the first report.

Bitdefender said the swaps bought little real secrecy. Both custom ciphers use the same plaintext value, KERNEL32, as key and starting vector, and each payload file stores its own key in its first eight bytes. What the changes did defeat, the company said, was detection and tooling written for a specific routine. "Each change broke static signatures and heuristic detections built around the framework as we first described it," the report says.

The backdoor itself, EggStremeAgent, dropped the gRPC protocol it used before in favor of raw TCP connections wrapped in mutual TLS through the wolfSSL library, with an extra AES layer inside, so even a proxy that intercepts the TLS session sees only ciphertext. Newer builds add commands that map Active Directory users, groups and servers through the same Windows calls the built-in net commands use, without starting net.exe; forward TCP traffic; run WMI queries with supplied credentials; impersonate a logged-on user's token; and run PowerShell inside the implant's own process, so powershell.exe never starts. None of the newer builds Bitdefender analyzed include the keylogger.

The implant that waits

Two newer builds, stamped Sept. 2 and Nov. 5, 2025, do not beacon to a command server at all. On startup they open TCP port 5060, the standard port for SIP internet telephony, and use the Windows firewall programming interface to create an inbound allow rule named "Core Networking - SIP," copying the name of a rule group that ships with Windows. The rule covers the domain, private and public profiles and allows edge traversal, so traffic arriving through a NAT device can reach the port. The operator connects in and must pass a 32-byte RC4 handshake before the implant accepts commands.

Bitdefender diagram contrasting a beaconing implant that reaches out to a C2 server with a passive implant that waits behind a firewall rule on port 5060 while the operator connects in from the internet.
Image: Bitdefender (fair use).Beaconing versus passive agent, from the Bitdefender report.

For defenders in segmented or closely watched networks, that design removes the regular outbound traffic that most often gives an implant away. Bitdefender advised alerting on any firewall rule with that name that is not part of a Windows baseline, on listeners on TCP 5060 on machines that are not phone endpoints, and on the .NET runtime or PowerShell automation libraries loading inside processes that do not normally host them.

Moving through file shares

In the more recent intrusion Bitdefender examined, the operators used valid domain credentials and staged their tools on an unmanaged machine that other workstations could still reach. They launched the built-in Windows script host on each target over SMB to run a copy of prncnfg.vbs, a real Windows printer script name, which copied a three-part package to the machine: a legitimate program, a malicious DLL for it to sideload and a configuration file. Persistence came from a run key named StandaloneUpdater pointing into a OneDrive logs folder, two levels deeper than where Microsoft's genuine updater lives. A batch file, C:\Users\Public\Officelog.bat, wrapped execution, and staged files were hidden between uses.

Bitdefender diagram of EggStreme lateral movement: an operator on an unmanaged host launches WScript.exe on a target workstation over SMB, which runs prncnfg.vbs, copies the Fuel package, and starts a legitimate program at logon that sideloads a malicious DLL.
Image: Bitdefender (fair use).EggStreme lateral movement flow, from the Bitdefender report.

Bitdefender recommended alerting on WScript.exe or cmd.exe running scripts from C:\Users\Public and on run keys that point into OneDrive subfolders other than the vendor's installed updater path. Payload files hide under ordinary-looking names such as Alarm00.wav in the Windows Media folder, .sdb files in apppatch and systemZones.res in the ICU globalization folder, and the company said a non-system process reading them at startup is the tell.

What has not changed

The infrastructure picture shifted as well. The legacy certificate authority, generated in 2019, linked 32 domains, and no new domains have appeared under it since the first report. Newer binaries carry their own certificates, which Bitdefender said suggests a move toward a separate authority for each campaign, though it has not confirmed that. Some pivots remain: a reused domain, mepintei[.]com, joined two clusters the company had tracked separately, and development servers exposed certificates for domains on consecutive ports 8443 to 8445 before those domains went live, revealing names later hardcoded in an implant.

The report frames the episode against analyst David Bianco's Pyramid of Pain, which ranks indicators by how much they cost an attacker to change. The operators, it says, "spent at the tools level and kept their methods": DLL sideloading under system library names such as advapi32.dll and dbghelp.dll, staging through file shares, running from memory and requiring mutual TLS. Bitdefender urged defenders to build at least one detection for each of those constants, because a rule tied to behavior is likely to outlive the next rebuild while a rule tied to a published hash probably will not.

About the Author

Priya Shah

Priya Shah covers threat intelligence, intrusion analysis, and adversary tradecraft for SOCtember from Singapore.

Related stories

Threat Intel desk