Turla uses a new Cereal toolset to collect email from Exchange servers
The Russia-aligned group Turla used a new toolset called Cereal to collect email from government Exchange servers in Kazakhstan and Romania, according to ESET findings reported by The Hacker News.
On this page
What changed
According to The Hacker News, the Russia-aligned state-sponsored group Turla, also known as Snake, is using a previously undocumented toolset called Cereal to break into Microsoft Exchange servers and collect email. ESET observed the toolset against two governmental entities in Kazakhstan and Romania in late 2025. According to BleepingComputer, the Romanian government organization was compromised on December 23rd, 2025. BleepingComputer also reports that Turla is linked to Russia’s Federal Security Service (FSB).
How the toolset works
CerealBox is the email harvesting module: it injects into the Exchange transport service, EdgeTransport.exe, to process, filter and collect messages. CerealNeuron is a passive backdoor that runs on a compromised Exchange server and listens for incoming web requests on paths that look like regular Exchange traffic. CerealHermit, a variant of CerealNeuron, reads commands from encrypted files on disk and has no network functionality of its own. The report describes the framework as eight moving parts that work together. It also notes that the toolset uses no external command-and-control infrastructure and instead abuses the compromised Exchange server for that purpose. The initial access vector is unknown.
Why it matters
The report describes Cereal as “a carefully constructed instrument for long-term, stealthy cyber espionage”. CerealBox was configured at the Romanian government organization to gather emails involving NATO and European Union institutional addresses.
What to do
According to BleepingComputer, ESET has shared an extended list of indicators of compromise (IoCs, artifacts such as file names, hashes or network patterns that suggest a compromise) on its GitHub page. Review that list against the Exchange servers in scope. The cited sources do not describe the initial access vector, so they give no configuration change that would have blocked it.
Sources
Related reading
3 postsDiscussion
Spotted an error? Send corrections to [email protected] .