Skip to content
All posts

Turla Cereal Malware Hit Exchange Servers: What to Check

November 20, 2026 · Team PlayCISO
TL;DR · the short version

On 10 November 2026 ESET published Cereal, a modular, mostly in-memory .NET toolset it found on Microsoft Exchange servers at a national government organisation in Kazakhstan (compromised since at least 28 November 2025) and one in Romania (since at least 23 December 2025). ESET attributes it to the Russia-aligned group Turla "with high confidence". The victim's own Exchange server acts as the control point: a passive backdoor waits for encrypted requests on Exchange-looking web paths, and an injected module filters mail inside the transport service. In Romania it was set to pick out messages to or from NATO and EU addresses. Initial access is unknown. On 19 November ReversingLabs added 12 related loaders and hunting advice. Exchange owners should look for unexpected HTTP.sys listeners, Windows libraries in the wrong folders, hand-placed .NET native images and unexpected code in EdgeTransport.exe.

Put it into practice
Turn the Cereal reports into a hunt plan
Practise writing testable hunt hypotheses with the right data sources and owners, then apply the same discipline to your Exchange servers.
Review hunt plans

On 10 November 2026, ESET Research disclosed Cereal, a set of malicious tools it found running on Microsoft Exchange servers at a national government organisation in Kazakhstan (compromised since at least 28 November 2025) and one in Romania (since at least 23 December 2025). ESET says: "We attribute Cereal, with high confidence, to the Russia-aligned APT group Turla." In the Romanian case the mail-collection module was set to pick out messages to or from NATO and EU institutional addresses. How the attackers got in is not known. On 19 November, ReversingLabs added 12 related loaders, older traces and hunting advice.

Who this is for: security leaders and Exchange administrators in government, defence, diplomacy and any organisation that still runs Exchange Server on premises, especially those that exchange mail with NATO, the EU or Central Asian governments.

Based on ESET's blog post and white paper (read in full on 20 November 2026) and ReversingLabs' follow-up of 19 November. PlayCISO is not affiliated with either company. Hashes, the exact URL paths the backdoor listens on and other indicators are not repeated here: take them from ESET's IoC repository, linked from its post.

Confirmed vs not yet known (20 Nov 2026)

  • Reported by ESET: two confirmed compromises, both national government organisations, one in Kazakhstan and one in Romania; Cereal found only on Exchange servers; NATO and EU addresses on the Romanian collection list; the components and techniques below.
  • Attribution, as ESET words it: Turla, "with high confidence", based on Cereal running alongside a loader already publicly attributed to Turla and CerealNeuron's similarity to Neuron, which the UK NCSC attributed to Turla in 2017. ESET describes Turla as "thought to be part of" Russia's FSB.
  • Not known: the initial access method (ESET: "We were unable to determine" it, though a vulnerability in the internet-facing Exchange servers is possible), what was actually exfiltrated, and whether other organisations are affected.
  • ReversingLabs' additions are hunting leads, not new victims: it says its work "does not establish additional victims or a new initial-access method", and that its first-seen dates are not proof of deployment.
  • Not a NATO or EU breach: the reports describe collection of mail exchanged with those institutions on the victims' servers, not a compromise of NATO or EU systems.

How Cereal works, at a defender's level

ESET named the tools "Cereal" because they lean heavily on .NET serialisation: most pieces are never written to disk as normal programs but decrypted, deserialised and run in memory by other pieces. What matters for defenders:

  • No outside command server. CerealNeuron is a passive backdoor. It does not beacon out; it waits for encrypted, integrity-checked requests and runs the small .NET programs they carry. ESET: "the victim's own Exchange server is abused as an operator-accessible control point." Outbound C2 detection will not see it.
  • It hides among Exchange's own web paths. Per ESET's white paper, CerealNeuron uses the Windows HttpListener class to claim URL prefixes on port 443 that look like OWA, Autodiscover and ActiveSync paths. Invalid requests are redirected to what look like normal Exchange error pages. This is a listener, not an ASPX web shell dropped into an IIS folder, and ReversingLabs warns that "IIS site logs alone may not show requests served by an independent HTTP.sys listener."
  • A fallback with no network at all. CerealHermit reads encrypted command files from disk and writes encrypted results back.
  • Mail theft inside the transport pipeline. CerealBox is injected into EdgeTransport.exe, the Exchange transport service, and picks messages with .doc, .docx or .pdf attachments that match lists of senders, recipients, subjects and attachment names. ESET calls it "a novel technique". It does not register a new transport agent; it hooks agents that are already loaded, so the Exchange transport agent list looks normal. Selected mail is compressed, encrypted and staged in files for later collection.
  • Loading without an obvious executable. CerealLoader was planted as a copy of a Windows library in System32\wbem so that the legitimate WMI provider host (WmiPrvSE.exe) loads it (DLL search-order hijacking), and in other cases copied by hand into the .NET native image cache under names mimicking Exchange libraries, so Exchange processes load it themselves.
  • What the operators ran. ESET lists Exchange Web Services mailbox searches and message retrieval, Active Directory and WMI queries, reading LSA secrets, listing volume shadow copies, and reading or deleting files.

Turla has a history here: ESET notes the group's earlier LightNeuron backdoor, documented in 2019, also used a compromised Exchange server as its hub. Cereal shows the same idea, with less to see on disk and in configuration.

Useful next, if this was relevant to you

Showing 1 of 3: Breach Cost Calculator

Timeline

DateEventSource
27 Apr 2022Compilation date of the earliest CerealLoader ESET found; it was uploaded to VirusTotal from Kazakhstan on 11 May 2022ESET white paper
11 May 2022One ESET-listed loader is already in ReversingLabs' file corpusReversingLabs
18 Nov 2025A related loader candidate first reaches ReversingLabs, ten days before ESET's first detectionReversingLabs
28 Nov 2025ESET detects the toolset at a national government organisation in Kazakhstan (compromised since at least this date)ESET white paper
23 Dec 2025A national government organisation in Romania is compromised from this date at the latest; ESET finds it after tuning detectionsESET white paper
15 Jan 2026Operator activity increases in KazakhstanESET white paper
20 Jan 2026Operator activity increases in RomaniaESET white paper
4 Mar 2026A loader candidate carries a "BlankPage" classification in ReversingLabs' reputation data, months before disclosureReversingLabs
10 Nov 2026ESET publishes the blog post and white paper, with IoCsESET / WeLiveSecurity
19 Nov 2026ReversingLabs publishes 12 related loaders and hunting guidanceReversingLabs

Exchange checks for administrators

These follow from what ESET and ReversingLabs describe. Run them on every Exchange server, starting with internet-facing ones, and compare against a known-good server of the same build.

  1. Load ESET's indicators and detections first. They are in ESET's IoC repository, linked from its post, and cover hashes and file names this article does not repeat.
  2. List HTTP.sys listeners. netsh http show servicestate shows request queues and the processes that own them; netsh http show urlacl shows URL reservations. On an Exchange server the owners should be IIS worker processes and Exchange services you can name. Any other process holding a prefix under /owa, /autodiscover or /Microsoft-Server-ActiveSync is a finding. ReversingLabs recommends checking live HTTP.sys listeners for exactly this reason.
  3. Compare front-door logs with IIS logs. ReversingLabs advises reviewing reverse-proxy and WAF logs for the reported CerealNeuron paths. Requests your load balancer or WAF saw that IIS never logged deserve a look.
  4. Look for Windows libraries in the wrong place. Search System32\wbem and Exchange service folders for DLLs that carry the names of Windows libraries normally found elsewhere, and for managed (.NET) DLLs where only native ones belong. ReversingLabs: compare against a known-good Exchange host.
  5. Check the .NET native image cache. Files in C:\Windows\assembly\NativeImages_* with Exchange-like names that were not produced by Ngen (ESET says the planted ones lack the structure of real native images) are suspect.
  6. Watch module loads, not just the agent list. Get-TransportAgent is still worth running, but CerealBox hooks existing agents. Review modules and injected code in EdgeTransport.exe and WmiPrvSE.exe with your EDR, and alert on new unsigned or unexpected managed code in Exchange processes.
  7. Keep the classic web shell check. Cereal is not an ASPX web shell, but initial access is unknown and Exchange compromises often involve one. Review recently written .aspx files in the Exchange and IIS web folders as usual.
  8. Look for staged mail. Compressed or encrypted files written by Exchange processes outside normal queue and log folders may be CerealBox output awaiting collection.
  9. Treat YARA hits carefully. ReversingLabs says an early rule matched many legitimate Microsoft-signed Exchange assemblies. Baseline any rule before it drives alerts, and hunt across all the family's names (CerealLoader, BlankPage, CerealMood and other vendor labels).

What security leaders should do this week

  • Hunt, don't panic. ReversingLabs recommends "a targeted hunt that combines published indicators with host inspection—not an assumption that every Exchange environment has been compromised."
  • Know where Exchange still runs on premises, which servers face the internet, and when each was last patched. ESET thinks an exposed server and a vulnerability are a plausible way in.
  • Ask for the checks above, with a named owner and a date. A passive backdoor with no outbound traffic will not show up in routine C2 or egress monitoring, so "no alerts" is not an answer.
  • If you exchange mail with NATO, EU institutions or Central Asian governments, brief the teams that do: the collection list in Romania was built around those correspondents.
  • If you find it, plan the response before you clean. ESET lists LSA secret extraction and Active Directory queries among the commands, so assume service-account and domain credentials reachable from the server are exposed. Preserve memory first (most of Cereal lives there), then rebuild rather than clean, and rotate credentials.
  • Decide whether to notify. Government and regulated organisations may need to tell their national CERT and the partners whose mail could have been staged.
  • Revisit the case for moving off on-premises Exchange or, at least, for reducing what is published to the internet. Every year it stays, it stays a target for groups like Turla.

Put it to work

  • APT Rosetta: Turla is Microsoft's Secret Blizzard and also appears as Venomous Bear, Snake and Uroburos. Match the names before you search your intel feeds.
  • Threat Hunt Plan Review: write the Exchange hunt as a testable hypothesis with data sources and an owner.
  • Detection Lab: practise turning behaviour like "a non-IIS process registers an OWA-looking listener" into a rule.
  • Nation-State Notification Lab: rehearse briefing the board when the finding is a state actor.
  • COLD RELIC reused stolen Workspace data: another Russia-nexus espionage case from the same week, against cloud mail instead of on-premises Exchange.

FAQ

What is Turla Cereal malware?

Cereal is the name ESET gave to a modular set of mostly in-memory .NET tools it found on Microsoft Exchange servers at two government organisations, one in Kazakhstan and one in Romania. The pieces include a loader (CerealLoader), a passive backdoor that waits for requests on Exchange-like web paths (CerealNeuron), a file-based variant of it (CerealHermit), an injector (CerealIron) and an email collector injected into the Exchange transport service (CerealBox). ESET published it on 10 November 2026.

Who is behind Cereal and how sure are the researchers?

ESET says: "We attribute Cereal, with high confidence, to the Russia-aligned APT group Turla." Its main reason is that Cereal was used alongside a loader component already publicly attributed to Turla, plus the similarity of CerealNeuron to Neuron, which the UK NCSC attributed to Turla in 2017. ESET describes Turla as thought to be part of Russia's FSB; that is ESET's profile of the group, not a separate finding about this campaign.

How did Turla get into the Exchange servers?

Nobody knows yet. ESET: "We were unable to determine the initial access method." It adds that because the Exchange servers were reachable from the internet, it is possible they were breached through a vulnerability. ReversingLabs says its own work does not establish a new initial-access method or any additional victims.

Is Cereal a web shell in OWA?

Not in the usual sense. The reports describe no ASPX web shell. CerealNeuron is a .NET program that uses the Windows HttpListener class to register its own URL prefixes on port 443 that look like Exchange paths (under OWA, Autodiscover and ActiveSync), and it answers bad requests with what look like normal Exchange error pages. ReversingLabs warns that "IIS site logs alone may not show requests served by an independent HTTP.sys listener." Keep checking for classic web shells too, but look for listeners as well.

Did Cereal steal NATO and EU emails?

ESET says that in the Romanian case CerealBox was configured to pick out messages sent to or received from NATO and EU institutional addresses, plus a small number of named individuals who appear to work with those institutions. It selects messages with .doc, .docx or .pdf attachments that match the operators' lists, then stages them for exfiltration. ESET has not published what was actually taken, and neither NATO nor the EU is described as compromised.

How do I check my Exchange server for Cereal?

Start with ESET's IoCs and detections. Then, from the reports: list HTTP.sys listeners and URL reservations and question any not owned by IIS or Exchange; compare reverse-proxy or WAF logs with IIS logs for requests IIS never recorded; look for Windows library names in unusual folders such as System32\wbem and for files in the .NET native image cache that were not produced by Ngen; and review modules loaded by EdgeTransport.exe and WmiPrvSE.exe against a known-good Exchange server. Checking the transport agent list is not enough, because CerealBox hooks existing agents rather than adding one.

Sources

This article is educational guidance for security leaders and Exchange administrators, not a threat-intelligence report. Indicators and detection details are in ESET's and ReversingLabs' publications; check them for updates before acting.

Turn the Cereal reports into a hunt plan
Practise writing testable hunt hypotheses with the right data sources and owners, then apply the same discipline to your Exchange servers.
Review hunt plans
Take this with you
How Cereal works, at a defender's level · Timeline · Exchange checks for administrators · What security leaders should do this week · Put it to work · Sources

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro