SAASMENT

News

EggStreme malware now waits on the host instead of calling home.

After EggStreme was exposed, the operators rebuilt it, including a passive variant that opens a port and waits instead of beaconing.

Illustration of a silent server with a closed listening arc and a cracked file sliding into a stack

Impact

What was impacted
Windows endpoints running a rebuilt EggStreme backdoor. Delivery is still DLL sideloading into EggStremeAgent (Gorem RAT). Newer builds drop the keylogger, change loader cryptography, use campaign-specific certificate authorities, and some listen for the operator instead of calling out. Initial access is still unknown.
Who was impacted
Government organizations in the Philippines. Bitdefender treats evidence of targeting in Taiwan as low to medium confidence. Teams whose detections still key only on the September 2025 EggStreme hashes or the old shared certificate authority.
What you need to do
Hunt for sideloaded DLLs that use system library names, payloads staged on file shares, in-memory execution, and mutual TLS. Check for unmanaged hosts outside endpoint management that other workstations can reach, and for unexpected listening services. Do not rely on old file hashes. In the same reporting window, treat late-October 2026 ASEAN summit document lures as PlugX delivery, and patch internet-facing Microsoft Exchange.

Bitdefender says the operators behind EggStreme did more than swap file hashes and servers after the framework was exposed in September 2025. The agent now uses a different network protocol and a larger command set. Some newer builds never beacon: they open a listening port and wait for the operator to connect. Command-and-control certificates moved from one shared authority to campaign-specific authorities, so detections tied to the old certificate no longer match.

How the first host is compromised is still unknown. The chain still depends on DLL sideloading. EggStremeFuel profiles the system and starts the loader, which persists, decrypts, and runs EggStremeAgent. That backdoor handles reconnaissance, lateral movement, and file transfer, with a secondary component called EggStremeWizard. Bitdefender says the keylogger was removed from the agent builds it observed in this rebuild. Within two weeks of public disclosure, the loader’s cryptography moved from RC4 to RC5 and, by the end of October 2025, to a custom cipher. New agent commands cover Active Directory reconnaissance, WMI queries, TCP forwarding, and running PowerShell, executables, and .NET assemblies.

Newer intrusions stage payloads on an unmanaged computer that sits outside endpoint management but is still reachable from workstations, then launch the sideloaded DLL with a VBScript file run over SMB. What did not change is the operating style: sideloaded DLLs named like system libraries, staging through file shares, running from memory, and requiring mutual TLS. Palo Alto Networks has also linked EggStremeFuel and EggStremeLoader to a separate cluster, CL-STA-1048, active between March and September 2025.

The same reporting describes two other campaigns against the region. As of late October 2026, Mustang Panda sent Philippine officials a package posing as a Laos–Philippines ASEAN summit agenda and installed PlugX while showing the decoy. Since at least July 2025, Earth Alux (also called Ink Dragon, Jewelbug, REF7707, and UAT-11587; Unit 42 tracks it as TGR-STA-0049) has targeted Southeast Asian government entities, often through unpatched Microsoft Exchange servers or phishing with decoy PDFs. Its newer implants, PerfectPioneer RAT and the modular KUKURAT backdoor, reach command servers over HTTP/3.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to a rebuilt EggStreme malware campaign against government organizations in the Philippines. Bitdefender says that after the framework was exposed in September 2025, operators changed the network protocol, dropped the keylogger from observed agent builds, moved loader cryptography from RC4 to RC5 and then a custom cipher by the end of October 2025, switched to campaign-specific certificate authorities, and added a passive variant that listens instead of beaconing. Initial access is unknown. Delivery is still DLL sideloading. Newer lateral movement stages payloads on an unmanaged host and launches them with VBScript over SMB. Low-to-medium confidence of targeting in Taiwan. The same reporting also covers Mustang Panda PlugX lures (late October 2026, fake ASEAN summit agenda) and Earth Alux (TGR-STA-0049) using unpatched Exchange or phishing to deploy PerfectPioneer RAT and KUKURAT over HTTP/3.

Context:
- What was impacted: Windows endpoints via EggStremeAgent (Gorem RAT) and related loader components. Separately, PlugX via document lures, and Exchange or phishing paths into PerfectPioneer RAT and KUKURAT.
- Who should care: Philippine government IT, Southeast Asian government networks with exposed Exchange, and defenders still matching only September 2025 EggStreme hashes or the old shared certificate authority.
- What to do: hunt the unchanged behaviors (sideloaded system-library DLLs, file-share staging, in-memory execution, mutual TLS), find unmanaged staging hosts and unexpected listeners, refresh detections, patch exposed Exchange, and treat summit-themed documents as malware delivery.

Do this in order. Ask before isolating a host, blocking a port, or deleting files. Prefer read-only inventory and log search first. Do not write or run malware, sideloading proofs, or exploit code.

1. Inventory
   - List Windows endpoints, which ones lack endpoint management, and which file shares workstations can write to.
   - Record internet-facing Microsoft Exchange versions and whether they are patched.
2. Contain
   - Propose isolation only for hosts that show sideloaded DLLs, unexpected listeners, or staging shares. Ask before you apply it.
   - Do not mass-delete DLLs or shares until the hunt confirms they are malicious.
3. Hunt
   - Search for DLLs named like system libraries that were sideloaded, payloads staged on file shares, in-memory execution, and mutual TLS to unfamiliar servers.
   - Look for VBScript launched over SMB from an unmanaged host, and for processes listening when EggStreme would previously have beaconed.
   - Note ASEAN-summit or bilateral-agenda documents that dropped a second payload, and Exchange web shells on unpatched servers.
4. Remediate
   - Plan Exchange patches and a detection update that does not depend on September 2025 EggStreme hashes or the old shared certificate authority.
   - Bring unmanaged staging hosts into management or remove their access to workstation shares. Ask before changing production access.
5. Report back
   - Hosts checked, suspected hits, listeners or shares found, Exchange patch status, and what is still unmonitored.

Do not invent hashes, domains, or CVEs. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform