Executive Summary
In late November 2025, ESET researchers uncovered a previously undocumented modular .NET malware toolset—dubbed 'Cereal'—deployed by Russia-aligned APT group Turla (also known as Snake, attributed to Russia's FSB) against a governmental organization in Kazakhstan, and subsequently against a Romanian government entity on December 23, 2025. The toolset hijacks Microsoft Exchange servers as covert command-and-control infrastructure, intercepts and exfiltrates targeted emails (including NATO- and EU-related correspondence), and leverages advanced .NET execution techniques such as VTable Fixups and native image cache abuse to evade detection. No external attacker-controlled infrastructure was identified, making network-based detection and takedown efforts extremely difficult.
The Cereal campaign reflects an escalating trend of nation-state actors embedding persistent espionage capabilities directly within enterprise email infrastructure rather than relying on external C2 servers. As geopolitical tensions involving Russia, NATO, and former Soviet states intensify in 2025–2026, Exchange-targeting tradecraft of this sophistication signals a maturing, long-term intelligence collection posture that defenders must urgently reassess.
Why This Matters Now
Turla's Cereal toolset eliminates external C2 infrastructure entirely, making traditional network-based detection and blocklist approaches ineffective. With active targeting of NATO-aligned governments and email interception techniques not previously documented for any malware family, organizations relying on perimeter defenses alone are exposed. This campaign is active now, with confirmed compromises in late 2025 and early 2026.
Attack Path Analysis
Turla's Cereal toolset gained initial footing on internet-facing Microsoft Exchange servers at governmental organizations in Kazakhstan and Romania, likely through exploitation of Exchange vulnerabilities or previously obtained credentials, then escalated privileges by abusing the .NET native image cache and WMI DLL hijacking to execute code within high-privilege Exchange and system processes. Operators moved laterally within the victim network by querying Active Directory, enumerating hosts, users, and DNS records, and accessing mailboxes via Exchange Web Services from the already-compromised Exchange hub. Command and control was conducted entirely over the victim's own Exchange server: CerealNeuron passively listened on Exchange-mimicking HTTPS paths, eliminating any external C2 infrastructure. CerealBox, injected into EdgeTransport.exe, silently intercepted and staged targeted emails matching hardcoded NATO and EU address filters, with exfiltration performed by operators issuing CerealNeuron commands to retrieve and delete the staged encrypted dumps. The long-term impact was sustained, covert espionage against government communications, with the compromised Exchange server weaponized as a persistent collection and control hub.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Turla gained initial access to internet-facing Microsoft Exchange servers at governmental targets in Kazakhstan and Romania. The exact initial vector is not confirmed, but given Turla's history and the Exchange server exposure, exploitation of Exchange vulnerabilities (e.g., ProxyLogon/ProxyShell class flaws) or use of previously stolen valid credentials is the most plausible path. CerealLoader was the first component written to disk, placed in System32 wbem directories to masquerade as legitimate DLLs loaded by WMI.
MITRE ATT&CK® Techniques
Server Software Component: IIS Components
Create or Modify System Process: Windows Service
Hijack Execution Flow: DLL Search Order Hijacking
Process Injection: Dynamic-link Library Injection
Email Collection: Remote Email Collection
OS Credential Dumping: LSA Secrets
Proxy: Internal Proxy
Obfuscated Files or Information: Embedded Payloads
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIS2 Directive (EU) 2022/2555 – Cybersecurity Risk Management Measures – System Integrity and Incident Handling
Control ID: Article 21(2)(a)(b)(e)
CISA Zero Trust Maturity Model 2.0 – Network Segmentation and Application Workload Integrity
Control ID: Network Pillar – Macro/Micro Segmentation; Application Workload Pillar – Runtime Protections
DORA (EU) 2022/2554 – Digital Operational Resilience Act – Threat Detection and ICT Incident Management
Control ID: Article 10 – ICT-related incident detection; Article 17 – ICT-related incident management
GDPR (EU) 2016/679 – Data Security and Breach Notification
Control ID: Article 32 – Security of Processing; Article 33 – Notification of Personal Data Breach
ISO/IEC 27001:2022 – Vulnerability Management, Security Monitoring, and Incident Response
Control ID: Annex A 8.8 – Management of technical vulnerabilities; Annex A 8.16 – Monitoring activities; Annex A 5.26 – Response to information security incidents
NYDFS 23 NYCRR Part 500 – Cybersecurity Monitoring and Incident Response Planning
Control ID: Section 500.14 – Monitoring; Section 500.16 – Incident Response Plan
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Government Administration
Turla's Cereal espionage toolset directly compromised governmental organizations in Kazakhstan and Romania, intercepting NATO/EU communications via Exchange servers, with lateral movement and exfiltration risks mapped to NIST.800-53.SC-7 and ZTMM.Data controls.
Military Industry
CerealBox's targeting of NATO-addressed emails exposes defense alliances to long-term infostealer operations; validated egress and east-west traffic security gaps align with PCI.4.0.3.5.1 and ZTMM.Network compliance failures under Turla's FSB-linked espionage mandate.
Information Technology/IT
Microsoft Exchange servers weaponized as C&C infrastructure via .NET native image cache abuse and VTable Fixups demand zero trust segmentation and multicloud visibility controls mapped to NIST.CSF.DE.CM-7 and ZTMM.CrossCutting.Visibility to detect passive backdoor activity.
International Affairs
Diplomatic missions and transnational institutions face persistent email interception risk as Cereal's CerealBox silently copies correspondence involving EU and NATO addresses, exploiting exfiltration gaps addressable through NIST.CSF.PR.DS-5 and ZTMM.CrossCutting.Governance egress enforcement.
Sources
- Exchange for breakfast: Turla’s Cereal tricks are not for kidshttps://www.welivesecurity.com/en/eset-research/exchange-for-breakfast-turlas-cereal-tricks-are-not-for-kids/Verified
- Turla Cereal Tricks - ESET White Paperhttps://web-assets.esetstatic.com/wls/en/papers/white-papers/turla-cereal-tricks.pdfVerified
- NCSC UK - Turla group using Neuron and Nautilus tools alongside Snake malwarehttps://web.archive.org/web/20250920160446/https://www.ncsc.gov.uk/static-assets/documents/Turla%20group%20using%20Neuron%20and%20Nautilus%20tools%20alongside%20Snake%20malware_1.pdfVerified
- MITRE ATT&CK - Turla Group (G0010)https://attack.mitre.org/groups/G0010/Verified
- Gamaredon X Turla Collaboration - ESET Researchhttps://www.welivesecurity.com/en/eset-research/gamaredon-x-turla-collab/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant to this incident because Turla weaponized a government Exchange server as both a collection hub and a C2 channel, exploiting implicit trust within the network perimeter. By enforcing workload-level segmentation and restricting lateral reachability from internet-facing services, CNSF would likely have reduced the blast radius of the compromise and constrained the attacker's ability to pivot freely across internal infrastructure.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Strict perimeter policies enforced at the workload boundary could likely reduce the attack surface available to externally facing Exchange servers, limiting which inbound paths and service interactions are reachable from outside the trust boundary.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation enforced at the workload and process communication layer could likely constrain the scope of privilege abuse by reducing which internal services and network paths a compromised Exchange process is permitted to reach, even when running at elevated privilege.
Control: East-West Traffic Security
Mitigation: East-west traffic enforcement would likely reduce the Exchange server's ability to freely initiate WMI queries, AD enumeration calls, and lateral service access toward other internal workloads, limiting the attacker's reconnaissance reach from a single compromised node.
Control: Multicloud Visibility & Control
Mitigation: Centralized traffic visibility across the environment could likely surface anomalous inbound HTTPS patterns to Exchange endpoints that deviate from known operator baselines, reducing dwell time by making the passive backdoor's communication profile more detectable.
Control: Egress Security & Policy Enforcement
Mitigation: Egress policy enforcement applied to the Exchange server's outbound communication paths could likely reduce the attacker's ability to exfiltrate staged data over unmonitored channels, constraining which destinations and protocols the compromised host is permitted to reach.
Had earlier segmentation and egress controls reduced the attacker's lateral reach and exfiltration paths, the scope of collected intelligence would likely have been narrower, and the duration of undetected access to sensitive government mailboxes would likely have been shortened.
Impact at a Glance
Affected Business Functions
- Diplomatic and Inter-Government Communications
- Classified Email and Document Exchange
- Active Directory and Identity Management
- NATO and EU Institutional Correspondence
Estimated downtime: N/A
Estimated loss: N/A
Long-term silent interception of sensitive government email communications in Kazakhstan and Romania, including messages sent to or received from NATO and EU institutional addresses. Exfiltrated data categories include diplomatic correspondence, government internal memos, .doc, .docx, and .pdf attachments of interest, Active Directory user and group records, DNS records, LSA credential secrets, and network topology information derived from WMI queries. The stealthy, persistent nature of the toolset suggests months of undetected collection prior to discovery. The compromise of credentials via LSA Secret extraction may further enable lateral movement into connected government or alliance networks.
Recommended Actions
Key Takeaways & Next Steps
- • Apply Zero Trust Segmentation (microsegmentation and identity-based policy) to restrict Exchange server outbound and inbound network access strictly to known, authorized endpoints — this would have blocked CerealNeuron's passive listener from being reachable by unauthorized operator ingress, even on Exchange-mimicking HTTPS paths, by enforcing explicit allow-lists at the network layer.
- • Deploy East-West Traffic Security controls to monitor and enforce workload-to-workload communication policies within the government network; Active Directory enumeration, WMI queries, and Exchange Web Services lateral queries from the Exchange server to internal hosts would have surfaced as anomalous east-west flows eligible for detection and blocking.
- • Enforce Egress Security and Policy Enforcement with FQDN and application-layer filtering on all outbound traffic from Exchange servers; while Turla avoided external C2, enforcing strict outbound allow-lists and DLP-aware egress controls would limit staging exfiltration and any residual outbound data movement to only explicitly authorized destinations.
- • Leverage Multicloud Visibility and Control (centralized traffic observability and anomaly detection) to baseline normal Exchange process behavior and flag deviations such as EdgeTransport.exe making unexpected internal API calls, spawning unusual child processes, or accessing file paths inconsistent with normal mail flow operations.
- • Implement Inline IPS (Suricata-based inspection) on traffic entering and leaving the Exchange server perimeter to detect known exploit patterns associated with Exchange vulnerability exploitation during initial compromise, and to identify malformed or anomalous HTTPS request patterns on Exchange-mimicking paths that deviate from legitimate OWA, Autodiscover, and ActiveSync traffic signatures.



