EggStreme: A Fileless APT Framework, Rebuilt the Moment It Was Exposed
A China-nexus APT runs EggStreme almost entirely in memory: a signed app sideloads a malicious DLL, each stage decrypts the next in RAM, and a 58-command backdoor and keylogger leave almost nothing on disk. When Bitdefender exposed it, the operators rebuilt it within days. Here's how it works and how to catch fileless tradecraft.
Executive summary. EggStreme is a fileless, memory-resident malware framework used by a China-nexus APT in espionage against targets including a Philippine military company and government networks. Bitdefender describes it not as one sample but as a chain of components, EggStremeFuel, EggStremeLoader, EggStremeReflectiveLoader, EggStremeAgent (a backdoor with 58 commands), EggStremeWizard and EggStremeKeylogger, paired with a Stowaway proxy for internal pivoting. Infection starts with DLL side-loading by a legitimate signed executable; each stage then decrypts the next directly into memory, leaving little readable on disk. When Bitdefender published its analysis, the operators rebuilt parts of the framework within days (rotating infrastructure, changing payload paths and config formats, and reworking the loader and agent), a reminder that exposure buys time, not safety. This piece is a defender's guide to fileless tradecraft: how the chain works, and the behaviours that catch it when signatures can't.
What it is
| Field | Detail |
|---|---|
| Name | EggStreme framework |
| Actor | China-nexus APT (espionage; APAC government/military targets) |
| Design | Fileless / memory-resident; multi-stage |
| Entry | DLL side-loading by a legitimate signed EXE (EggStremeFuel) |
| Core | EggStremeAgent backdoor (58 commands), EggStremeKeylogger, Stowaway proxy |
| Detectability | Bitdefender: "difficult to detect" (key components run in memory) |
| Response to exposure | Operators rebuilt the framework within days |
The chain, and why it's hard to see
Signed EXE ──► side-loads ──► EggStremeFuel (malicious DLL)
│ decrypts next stage
▼
Loader → ReflectiveLoader (in memory)
│
▼
EggStremeAgent (58 cmds) + Keylogger (in RAM)
│
▼
Stowaway proxy → pivot across the network- DLL side-loading: a legitimate, signed application is made to load a malicious DLL placed next to it. The trusted process does the dirty work, so EDR sees a signed binary behaving normally, until it doesn't.
- Fileless execution: each stage decrypts the next into memory rather than dropping a readable payload. There's often no malicious file on disk to scan, hash, or submit.
- In-memory backdoor + keylogger: EggStremeAgent (58 commands) and the keylogger live in RAM.
- Internal pivoting: the Stowaway proxy routes attacker traffic through the victim network for lateral movement and persistence.
Why "rebuilt after exposure" matters
When Bitdefender published IOCs, the operators didn't go quiet, they re-tooled. Bitdefender frames the changes by the classic Pyramid of Pain:
| Changed | Pain to the attacker |
|---|---|
| Hashes, IPs, domains | Trivial — swapped easily |
| Payload paths, config formats, a firewall-rule name | Artifacts — more effort |
| Fuel, loader, agent reworked | Tools — real effort |
The takeaway for defenders: detections built on hashes and IPs expire fast. Durable detection targets behaviour and technique (TTPs), the top of the pyramid, which an actor can't change without changing how they operate.
How to detect fileless tradecraft (not just this sample)
EggStreme's whole design defeats signature/file-based detection. Catch the behaviours:
1. DLL side-loading
- Alert when a signed, trusted EXE loads a DLL from an unusual location (e.g. a user-writable dir, Temp, a download folder) or a DLL whose name matches a known system library but sits in the wrong path.
- Baseline which DLLs each app legitimately loads; flag deviations (Sysmon event ID 7, image/module loads).
2. In-memory / reflective loading
- Watch for memory regions marked executable that aren't backed by a file (RWX private memory), and process hollowing/reflective-loading patterns.
- EDR memory scanning and YARA-in-memory rules on technique, not file hash.
3. Living-off-the-land and recon
- Restrict built-in Windows tools an environment doesn't need (Bitdefender's advice), and alert when they run unexpectedly.
- Flag unusual use of signed LOLBins for execution or download.
4. Network pivoting and new listeners
- New inbound listeners on workstations (a desktop shouldn't be a server) — a strong Stowaway-style pivot signal.
- Internal traffic patterns consistent with proxying/tunnelling between hosts that don't normally talk.
5. Credential and keylogging effects
- Access to LSASS or credential stores; keylogger artefacts; unexpected scheduled tasks/services for persistence.
A starting detection idea
title: Signed application side-loading a DLL from a user-writable path
status: experimental
logsource: { category: image_load, product: windows }
detection:
selection:
ImageLoaded|contains: ['\Users\', '\Temp\', '\Downloads\', '\ProgramData\']
ImageLoaded|endswith: '.dll'
filter_known:
Image|startswith: ['C:\Program Files\', 'C:\Windows\']
condition: selection and not filter_known
falsepositives: [legitimate apps that ship DLLs in user dirs — baseline per app]
level: highTune per environment; the point is to detect the technique (side-loading into unusual paths), which survives the attacker swapping hashes and domains.
Response if you suspect fileless compromise
- Preserve memory (the payload may only exist in RAM) before rebooting — capture volatile evidence.
- Hunt the technique, not the hash: side-loading, reflective loads, new listeners, LOLBin abuse.
- Hunt unmanaged machines that can reach workstations (Bitdefender's advice) — gaps in EDR coverage are where fileless actors live.
- Rebuild compromised hosts; rotate credentials; assume keylogged secrets are burned.
Conclusion
EggStreme is a clean case study in modern, fileless, hard-to-signature APT tradecraft, and in actors who re-tool the instant they're exposed. The defensive answer isn't a better blocklist of hashes; it's behaviour-based detection of side-loading, in-memory execution, LOLBin abuse and network pivoting, plus memory-aware response. Build detections at the top of the Pyramid of Pain, where re-tooling can't easily escape them.
Do this now: alert on signed apps side-loading DLLs from unusual paths, on new inbound listeners on workstations, and on unexpected use of built-in Windows tools; and make sure EDR and memory capture cover your whole fleet, including unmanaged hosts.
Related: our network pentesting manual and the community thread on a detection that actually fired.
Sources: Bitdefender (original analysis), Bitdefender (rebuilt framework), Infosecurity Magazine, Hackread, The Register. EggStreme was first disclosed by Bitdefender in 2025; this covers its analysis and the operators' subsequent re-tooling.
Related research
From CCTV to Cryptominer: Exposed GeoVision Software, a Disabled Defender and 13 Breached Organisations
Huntress traced intrusions at 13 organisations to one place: internet-exposed GeoVision camera management software running as SYSTEM on Windows. The attackers disabled Microsoft Defender with a vulnerable driver and debugger hijacks, then installed a cryptominer. Here is the attack chain, the detections that catch it, and why your physical-security systems belong in your patch programme.
Kerberoasting: Detection and Hardening for Active Directory
Kerberoasting turns weak service account passwords into domain compromise, and it barely looks like an attack. How it works, the event IDs and queries that catch it, and the hardening that makes it pointless.