Skip to main content
Sector público-ENS9 min

Turla Cereal malware: how it turns Exchange servers into espionage nodes

A Russia-linked espionage group has used the mail server of public administrations as both command centre and message-theft point. Its orders are camouflaged as employees checking their email.

Photo of Gorka Gonzalo
Gorka GonzaloFounder & CEO
Isometric illustration of a mail server connected to a network of nodes, symbolising espionage with Turla's Cereal malware on Exchange.

The Turla Cereal malware lets the Russia-linked cyberespionage group turn Exchange servers at public bodies into its own espionage tool. According to ESET's analyses reported by BleepingComputer [1] and Help Net Security [2], it is a modular .NET toolset that receives commands through the internet-exposed Exchange server itself, disguised as ordinary mail traffic, and copies the messages the attacker is interested in.

That is why defence cannot stop at the perimeter: you also have to watch how the mail server itself behaves.

Cereal uses Exchange itself as its command and collection channel

An external command-and-control server gives defenders a destination to investigate or block. Cereal does away with that component. According to ESET's description as reported by Help Net Security, the operators send their instructions directly to the victim's Exchange server, which is already published on the internet, and disguise them as routine Outlook Web Access, Autodiscover and ActiveSync requests [2]. To anyone watching the network, what happens looks like employees checking their email.

The toolset has several parts. CerealNeuron, the main backdoor, waits for encrypted web requests on paths that imitate legitimate Exchange services, such as /owa/sdds/ or /autodiscover/proxyservice/; if the request passes its integrity checks, it decrypts and runs it, and if not, it returns a normal-looking error page, according to Help Net Security [2]. Each command arrives as a small .NET program compiled for a single task: extracting mailboxes, querying Active Directory, obtaining locally stored credentials, or reading and deleting files, as BleepingComputer [1] and Help Net Security [2] detail. BleepingComputer reports that ESET did not observe any external command-and-control infrastructure: the compromised server was the only control point [1]. The same outlet describes a variant, CerealHermit, which does not use the network and reads encrypted commands from files on disk, and suggests it could serve as a fallback [1].

Collection is handled by CerealBox. Instead of registering a new transport agent, something that would be visible in the Exchange configuration, it injects itself into the EdgeTransport.exe process, the one that moves mail, and wraps the handlers of the agents already loaded in memory, according to Help Net Security [2]. Mail keeps flowing and no new transport agent appears. The same outlet explains that CerealBox keeps messages with .doc, .docx or .pdf attachments that match fixed lists of senders, recipients, subjects or file names, then compresses and encrypts them and leaves them staged on disk for the operators to collect [2]. ESET maintains, again according to Help Net Security, that this kind of hooking from inside the transport service had not previously been documented in any malware family [2].

ESET found it at public bodies in Kazakhstan and Romania

BleepingComputer explains that ESET researchers documented the attacks in late 2025: first at a government body in Kazakhstan and, a month later, at a government agency in Romania [1]. The sources describe the victims as government bodies in Kazakhstan and Romania.

The most detailed timeline comes from Help Net Security: ESET found the toolset on 28 November 2025 at the Kazakh body and, after refining its detections, located the Romanian victim, compromised on 23 December 2025 [2]. BleepingComputer quotes the researchers giving that same compromise date for Romania [1]. Help Net Security adds that activity in Kazakhstan picked up again on 15 January 2026, the day after the Old New Year, an informal holiday still celebrated in Russia [2]. It is worth cross-checking these chronological details against ESET's original report.

As for attribution, Help Net Security notes that ESET attributes Cereal to Turla with high confidence, based on a component publicly linked to the group that was used alongside Cereal and on similarities with earlier Turla malware [2]. BleepingComputer describes Turla, also known as Snake, Secret Blizzard or Waterbug, as a cyberespionage group linked to Russia's Federal Security Service (FSB) [1].

A public-administration Exchange server has everything a spy looks for

What matters to an administration is not only the technical sophistication but the choice of target. As an editorial analysis framework, you can examine the trust placed in the server, its exposure to the internet and the correspondence it concentrates. It is worth checking whether the trust placed in the server is reducing scrutiny of its activity. In the attacks described, the operators sent commands to the victim's internet-exposed Exchange server. And it processes correspondence that may be of interest to the attacker.

In the case described, Cereal receives commands through the compromised Exchange server and copies messages from the mail flow itself. According to BleepingComputer, ESET describes the toolset as designed for stealthy, long-term cyberespionage, with a small footprint on disk and relying on infrastructure less likely to be detected and blocked [1].

The Romanian case shows how that access is exploited. According to BleepingComputer [1] and Help Net Security [2], in Romania the collection module was configured to select correspondence exchanged with NATO and EU addresses. The aim was not to empty the mailbox but to filter what had strategic interest. ESET researcher Matías Porolli illustrates it in Help Net Security with a scene: an official writes to a colleague at a military alliance, the message leaves normally and, before it leaves the building, a piece of code examines it and keeps a copy for third parties [2].

Mail can keep flowing normally while CerealBox copies the selected messages. That is precisely why the problem is one of visibility, not of negligence.

Attacking mail is nothing new for Turla: Cereal continues a line of years

That Turla targets mail servers fits its track record. Trend Micro considers the Turla APT a highly sophisticated advanced persistent threat group, with suspected activity since at least 2004, and cites a 2018 intelligence report according to which the group used the Neuron and Nautilus tools against Windows machines, with particular attention to mail and web servers [4].

ZDNet published ESET's research on LightNeuron, a backdoor designed specifically for Microsoft Exchange that worked as a mail transfer agent (MTA) [3]. ESET researcher Matthieu Faou explained to that outlet at the time that Neuron was not designed to interact with Exchange, whereas LightNeuron integrated directly into its workflow [3]. Its operators did not connect to the server: they sent emails with PDF or JPG attachments in which they hid commands using steganography, according to the same source [3]. ZDNet also reported that, according to ESET, Turla had been using LightNeuron since 2014 [3].

It is important not to confuse the two tools: LightNeuron belongs to earlier research and Cereal is something else. The command channel changes, from email attachments to web requests that imitate Exchange services; in addition, CerealBox injects itself into EdgeTransport.exe without registering a new transport agent. Even the pattern of pauses is reminiscent of the earlier one: in 2019, according to ZDNet, ESET observed a pause in activity between 28 December 2018 and 14 January [3], and now Help Net Security links the resurgence in Kazakhstan to the end of the Old New Year [2]. The technique evolves; the objective, government email, stays the same.

So the earlier Turla Exchange backdoor and today's Exchange server espionage malware share a target, even if they differ in method.

Telling legitimate traffic from malicious traffic means looking at behaviour, not just the path

Since the commands imitate requests to OWA, Autodiscover or ActiveSync, it is worth weighing the operational impact of blocking those services or the destination server. Help Net Security also reports that ESET could not identify the IP addresses from which the operators connected [2].

As an analytical criterion from the editorial team, and not as a finding from the sources, the useful question becomes what is normal on that server. It is worth comparing the volume, origin and frequency of requests to those paths against the body's baseline; looking for unusual paths that receive repeated requests answered with errors; and hunting for server activity that does not correspond to any real user, such as Active Directory queries or mailbox accesses launched from Exchange itself.

The sources provided describe some technical traits, but they do not replace the full indicators of compromise: BleepingComputer states that ESET has published an extended list on its GitHub page [1], and that is where to go for the finer checks. To analyse possible deviations across large volumes of logs, it is worth defining review criteria and requiring an analyst to validate the alerts.

What to review on an internet-exposed Exchange server

The following checks are general recommendations from the editorial team based on what ESET describes:

  1. Exposure inventory. Which Exchange servers are published on the internet and which services each one offers.
  2. Unrecognised components. According to Help Net Security, Cereal's loader posed as ncobjapi.dll in the wbem folder of System32 and, in another chain, as wbemcomn.dll; the operators also dropped copies in the .NET native image cache with names such as Microsoft.Exchange.Search.Mdb.ni.dll [2]. It is worth reviewing those locations against the known configuration.
  3. Monitoring of OWA, Autodiscover and ActiveSync. Make sure logs of those requests exist, are retained and are reviewed regularly.
  4. Cross-checking against indicators. Compare the indicators published by ESET with your own logs.
  5. Administration. Who can administer the server, from where and with what controls.

None of this works as a one-off review. Faced with tools designed to stay for a long time, it is worth demanding continuous monitoring from your own team or from the provider you hire.

What evidence to ask for from a provider managing Exchange for an administration subject to the ENS

If a body delegates the administration of its email to a provider, it is worth agreeing in advance what evidence that provider must deliver. Trust in the provider should rest on concrete evidence and not on generic statements. The table sets out a proposal from the editorial team:

Evidence to requestWhat it shows
Up-to-date inventory of Exchange servers and their internet exposureThat it is known what is published and what attack surface it presents
Server activity logs retained and accessible to the bodyThat what happened can be reconstructed if there is an incident
Incident response procedure with committed timeframesThat there is a plan and people responsible when something fails
Documented patching processThat known vulnerabilities are fixed in an orderly way
Evidence of continuous monitoring of server behaviourThat anomalous activity would be detected even if it imitates legitimate traffic
Record of review of published threat indicatorsThat campaigns such as Cereal are checked against your own systems

How these pieces of evidence translate into specific obligations depends on each system and each contract, so it is advisable to confirm the interpretation with legal counsel. The requirements of the Spanish National Security Framework (ENS) for public-sector suppliers offer a starting point for structuring that conversation with the provider.

A trusted server stops being trusted if nobody checks what it does

Cereal shows that an attacker can hide in a mail server's normal traffic without leaving any infrastructure of their own in view. In that scenario, defence depends on knowing how the server behaves and being able to prove it with evidence, not on assuming it is reliable simply because it is your own. For public bodies and providers, it is worth coordinating documented monitoring with a review of the applicable compliance obligations. If you want to put this in order, alignment with the Spanish National Security Framework (ENS) is a good starting point.

Sources

  1. Turla hackers use new Cereal malware to spy on govt Exchange servers — BleepingComputer, 2026-11-10
  2. Turla’s Cereal malware turns victims’ Exchange servers into spy hubs — Help Net Security, 2026-11-10
  3. Russian cyberspies are using one hell of a clever Microsoft Exchange backdoor — ZDNet, 2019-05-07
  4. Examining the Activities of the Turla APT Group — Trend Micro, 2023-09-22

Self-check your ENS category

Find out which ENS category (basic/medium/high) applies to you and which controls are still missing, in 2 minutes.

Take the self-check

Was this article useful?

Photo of Gorka Gonzalo

Gorka Gonzalo

Founder & CEO

Founded Hodeitek in 2023 and runs the company, after more than 8 years in pentesting, Red Team, OT/ICS auditing, and SOC leadership. A cybersecurity and AI expert, he sets the technical and product direction of HodeiShield and personally leads the most critical engagements — from defense strategy to applying AI in threat detection. He is the client's direct point of contact: whoever scopes the work also answers for the result.