High 4 Hunt LeadsIOCsTurlaCerealBleepingComputer

Turla Hid Inside Exchange to Copy Government Mail on NATO and the EU

ESET found Turla's new Cereal toolset on government Exchange servers in Kazakhstan and Romania, hooking mail flow from inside EdgeTransport.exe and using the victim's own server as its command channel.

Russia’s Turla has been reading government email from inside the mail server itself. BleepingComputer reports on new research from ESET, which found a modular .NET toolset it calls Cereal on Microsoft Exchange servers at a government body in Kazakhstan (found Nov. 28, 2025) and a government agency in Romania (compromised Dec. 23, 2025). In Romania it was set to copy emails exchanged with NATO and EU addresses. ESET attributes it to Turla with high confidence.

For defenders

No outside C2: the passive backdoor, CerealNeuron, waits for encrypted HTTPS requests on paths that look like Exchange traffic (/owa/sdds/, /autodiscover/proxyservice/, /Microsoft-Server-ActiveSync/integrated/api/) and redirects anything malformed to an Exchange error page (T1071.001 (Application Layer Protocol: Web Protocols)). The victim’s own Exchange server is the control point; ESET couldn’t identify operator IPs. A disk-only variant, CerealHermit, reads encrypted command files instead.

Mail theft: CerealBox is injected into EdgeTransport.exe and wraps the handlers of transport agents already loaded in memory, so no new agent shows up in Exchange config (T1055 (Process Injection), T1114 (Email Collection)). It keeps messages with .doc, .docx or .pdf attachments that match sender, recipient, subject or attachment lists, then compresses, encrypts and stages them on disk (T1074.001 (Data Staged: Local Data Staging)). ESET calls the technique new.

Loading: CerealLoader, the only component on disk unencrypted, posed as ncobjapi.dll or wbemcomn.dll in C:\Windows\System32\wbem\, loaded by WMI (T1574.001 (Hijack Execution Flow: DLL)), and as .NET native images such as Microsoft.Exchange.Search.Mdb.ni.dll that Exchange loads in place of the real library (T1574 (Hijack Execution Flow)).

Commands: each one is its own small encrypted .NET program (CerealRunner) run in memory: EWS mailbox pulls, Active Directory and DNS queries, WMI process and connection lists, LSA Secrets, snapshot and file listing, file reads and deletes (T1003.004 (OS Credential Dumping: LSA Secrets), T1087.002 (Account Discovery: Domain Account)). Initial access isn’t described. ESET’s 18 SHA1s are in its IOC repository; no network indicators exist.

Files
C:\Windows\System32\wbem\ncobjapi.dll (SHA1 5B94FE76EC4FEB0B5CB6EA3BCA4C48D2FE22597B)
C:\Windows\System32\wbem\wbemcomn.dll (SHA1 7AB784D0049890D9844AEE7F214BA173E3CC23BE)
Microsoft.Exchange.Search.Mdb.ni.dll (SHA1 1408A8F62B09A5AD0DFF279B2878D8F59F70A330)
Microsoft.Exchange.Data.Transport.ni.dll (SHA1 4A3C263977417FB6977B0E598C9E3BC5924F390C)
EdgeTransport.ni.exe (SHA1 5D80118B1EE974936322475F740AB3AEFF70B8F3)

What it means for you

This is espionage against governments, not something that touches home users. The worrying part is how quiet it is: email keeps flowing normally while copies of interesting messages are set aside. Organizations that run their own Exchange servers, especially in government or anything dealing with NATO and the EU, are the ones who should look.

Do this now

  1. Exchange admins: check C:\Windows\System32\wbem\ for unsigned ncobjapi.dll or wbemcomn.dll and match files against ESET’s hashes.
  2. Look for Exchange native images (*.ni.dll, *.ni.exe) that weren’t written by the .NET optimization service.
  3. Review IIS logs for requests to /owa/sdds/, /autodiscover/proxyservice/ and /Microsoft-Server-ActiveSync/integrated/api/.
  4. If you find a hit, don’t just remove the files: rotate service and admin credentials, since LSA Secrets were targeted.

Source article: Turla hackers use new Cereal malware to spy on govt Exchange servers
Publisher: BleepingComputer
Published: Nov. 10, 2026
URL: https://www.bleepingcomputer.com/news/security/turla-hackers-use-new-ceral-malware-to-spy-on-govt-exchange-servers/

Executive Summary

Turla, the Russian state espionage group widely assessed to be part of the FSB (also tracked as Snake, Secret Blizzard and Waterbug), has deployed a previously undocumented modular .NET toolset that ESET calls Cereal on the Microsoft Exchange servers of a national government body in Kazakhstan (found Nov. 28, 2025, with activity surging Jan. 15, 2026) and a governmental organization in Romania (compromised Dec. 23, 2025); ESET attributes it with high confidence, citing a component already publicly linked to Turla and the functional similarity of its backdoor to Turla’s older Neuron. How the operators first got onto the servers is not described. Once there, CerealLoader, the only component written to disk unencrypted, is planted where legitimate processes will load it: as ncobjapi.dll or wbemcomn.dll in C:\Windows\System32\wbem\ for the WMI service, or as poisoned .NET native images (for example Microsoft.Exchange.Search.Mdb.ni.dll) that Exchange loads instead of the genuine assembly, executing native code through VTable Fixups before any .NET code runs. CerealLoader unpacks encrypted containers (CerealRunner, CerealSprinter, CerealIron, CerealMoth) that run payloads in memory, including CerealNeuron, a passive backdoor that listens on HTTPS paths imitating Outlook Web Access, Autodiscover and ActiveSync, and CerealHermit, a disk-based fallback that reads encrypted command files. Commands arrive as separately compiled CerealRunner programs that pull mailboxes over Exchange Web Services, query Active Directory, run WMI queries, extract LSA Secrets, list snapshots and read or delete staged files. CerealBox, injected into EdgeTransport.exe, wraps the handlers of transport agents already loaded in memory and silently stages copies of messages carrying .doc, .docx or .pdf attachments that match hardcoded sender, recipient, subject or attachment-name lists (in Romania, NATO and EU addresses), which the operators later exfiltrate and delete through CerealNeuron. There is no external command-and-control infrastructure: the victim’s internet-facing Exchange server is the control point, so the objective, long-term collection of diplomatic and government email, is achieved with almost no network footprint. Hunt leads, false positive expectations and indicators are detailed below; ESET published SHA1 hashes but no detection rules or network indicators.

ATT&CK chain: Persistence → Privilege Escalation → Defense Evasion → Credential Access → Discovery → Collection → Command and Control → Exfiltration

Hunt Lead Grid

Hunt Lead Level Hunt Lead Name ATT&CK Risk of False Positives
1 (Junior) CerealLoader Files in WBEM and Exchange Paths T1574.001 (Hijack Execution Flow: DLL), T1036.005 (Masquerading: Match Legitimate Resource Name or Location) Low. The genuine ncobjapi.dll and wbemcomn.dll are Microsoft-signed and ship with Windows; the lead anchors on ESET’s SHA1 values and on copies of those names that are unsigned or not signed by Microsoft.
2 (Pro) Exchange Native Image Cache Tampering T1574 (Hijack Execution Flow) Medium. The .NET optimization service legitimately rewrites native images after updates; the lead anchors on .ni.dll or .ni.exe files written by any process other than ngen.exe or mscorsvw.exe, and on native images whose size or signature does not match a fresh regeneration.
2 (Pro) Exchange Lookalike HTTPS Listener Paths T1071.001 (Application Layer Protocol: Web Protocols) Medium. The three paths sit under real Exchange virtual directories, so scanners and broken clients can request them; the lead anchors on the exact sub-paths ESET lists, on HTTP.sys URL registrations for them, and on repeated POSTs from the same external source.
3 (Elite) EdgeTransport In-Memory Tampering and Mail Staging T1055 (Process Injection), T1114 (Email Collection), T1074.001 (Data Staged: Local Data Staging) Medium. Legitimate transport agents, antivirus and archiving products also hook mail flow; the lead anchors on cross-process memory access into EdgeTransport.exe, unexpected in-memory modules, and EdgeTransport writing high-entropy files outside Exchange’s queue and log folders.

CerealLoader Files in WBEM and Exchange Paths

CerealLoader is the one Cereal component that exists on disk as a recognizable .NET file, and ESET saw it under several legitimate-looking names: ncobjapi.dll and wbemcomn.dll inside C:\Windows\System32\wbem\, where the Windows Management Instrumentation service loads them automatically and the malicious DLL forwards real function calls so WMI keeps working; version.dll (two samples); Microsoft.Search.Platform.dll and Microsoft.Ceres.dll, both Exchange search component names; iph.dat; and native image files named Microsoft.Exchange.Data.Transport.ni.dll, Microsoft.Exchange.Search.Mdb.ni.dll, EdgeTransport.ni.exe and Microsoft.Exchange.EdgeSyncSvc.ni.exe. ESET also lists x86 and x64 bootstrapper DLLs and the encrypted CerealRunner, CerealSprinter, CerealHermit, CerealIron and CerealMoth samples. The detection logic is a hash sweep of every Exchange server for the 18 SHA1 values in the appendix, plus a signature check on every file with these names in the WBEM folder and the Exchange installation and native image directories, flagging any that are unsigned, not signed by Microsoft, or whose image is a .NET assembly when the genuine file is native.

Use EDR file inventory, a scripted Authenticode check run through your endpoint management tool, and Sysmon image-load events (event ID 7) for WmiPrvSE.exe and the Exchange services. Sweep back as far as telemetry allows and at least to November 2025, since ESET dates the earliest known compromise to then and the toolset is built for long-term presence; a live file-system query also catches older implants that are still loaded. Scope first to all Exchange servers (Mailbox and Edge Transport roles), then to other servers running WMI-heavy management software, because the WBEM sideload is not Exchange-specific. Do not allowlist by file name, since every name here is legitimate; allowlist by Microsoft signature and the expected file version for your Windows and Exchange build. Hash blocking is a useful supplement, not the primary control, because ESET describes many near-identical samples compiled per task. Any confirmed hit should be treated as a full compromise of that Exchange server and escalated to incident response, with credential rotation, because LSA Secrets extraction is one of the observed commands.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Persistence, Privilege Escalation, Defense Evasion → T1574.001 (Hijack Execution Flow: DLL); Defense Evasion → T1036.005 (Masquerading: Match Legitimate Resource Name or Location)

Sources: “Exchange for breakfast: Turla’s Cereal tricks are not for kids”, ESET (Matías Porolli), Nov. 2026, https://www.welivesecurity.com/en/eset-research/exchange-for-breakfast-turlas-cereal-tricks-are-not-for-kids/ (additional source, same campaign); “Exchange for breakfast: Turla’s Cereal tricks are not for kids – Indicators of Compromise”, ESET malware-ioc repository, Nov. 2026, https://github.com/eset/malware-ioc/tree/master/turla (additional source, same campaign); source article (above)

Exchange Native Image Cache Tampering

To speed up startup, .NET keeps precompiled native images of common assemblies in a system cache and loads them in preference to JIT-compiling the managed assembly. The operators placed CerealLoader files in that cache under names such as Microsoft.Exchange.Search.Mdb.ni.dll, so that when an Exchange service asked for the library the runtime loaded the malicious file; because it contains no real replacement code, .NET silently falls back to the genuine library, but only after the attacker’s native entry point has run. In one sample the payload only activated when the parent process was Exchange’s search service. The detection logic is a file-creation and modification monitor on the native image directories (the NativeImages_v4.0.30319_32 and NativeImages_v4.0.30319_64 folders under C:\Windows\assembly) for any .ni.dll or .ni.exe whose writing process is not ngen.exe or mscorsvw.exe, combined with an image-load rule that flags an Exchange process loading a native image that was created or changed outside a patch window.

Use EDR or Sysmon file-create (event ID 11) and image-load (event ID 7) telemetry on Exchange servers, and correlate with your patch and cumulative-update schedule, since a CU legitimately triggers mass native image regeneration. Sweep back to at least November 2025. Scope to Exchange servers first, then any server whose critical service is .NET-based. For tuning, suppress writes by the signed .NET optimization binaries from their system path, never by file name, and expect bursts after .NET or Exchange updates; a single native image changed on a quiet day is the signal. Deleting the native image cache wholesale is the wrong first response, because it destroys evidence and the loader can simply be replanted; collect the files first, then regenerate the cache with ngen after eradication. Hits should be triaged together with the first lead, and any confirmed tampered native image is an escalation. The technique generalizes beyond Cereal, since native image hijacking works against any .NET service and is rarely monitored.

Hunt Lead Level: 2 (Pro)

ATT&CK: Persistence, Privilege Escalation, Defense Evasion → T1574 (Hijack Execution Flow) (no sub-technique covers .NET native image cache abuse)

Sources: ESET blog post (above), additional source; ESET IOC repository (above), additional source; source article (above)

Exchange Lookalike HTTPS Listener Paths

CerealNeuron makes no outbound connections. It registers listeners on the Exchange server for HTTPS paths designed to blend into normal Outlook Web Access, Autodiscover and ActiveSync traffic; ESET lists https://*:443/owa/sdds/, HTTPS://*:443/AUTODISCOVER/PROXYSERVICE/ and HTTPS://*:443/MICROSOFT-SERVER-ACTIVESYNC/INTEGRATED/API/. A request that is correctly encrypted and passes several integrity checks is decrypted and run as a CerealRunner command, with the encrypted output returned in the response; anything else is redirected to a legitimate-looking Exchange error page. ESET could not identify the operators’ source addresses. The detection logic has two parts: an inventory check of HTTP.sys URL reservations and active listeners on each Exchange server for these prefixes (they are not part of a standard Exchange install), and a web log hunt for requests to these exact sub-paths, especially POSTs with large bodies that return a redirect for most sources but a 200 for one.

Use IIS logs and the HTTPERR logs (HTTP.sys handles these listeners before IIS, so some requests may only appear there), the output of netsh http show urlacl and netsh http show servicestate, reverse proxy or load balancer logs in front of Exchange, and any TLS-inspecting gateway. Sweep back to November 2025 and keep the hunt recurring, since the backdoor is passive and could sit idle for weeks. Scope to internet-facing Exchange servers and their front-end proxies. False positives come from vulnerability scanners and misconfigured mobile clients probing ActiveSync; anchor on the exact sub-paths ESET lists and on a repeat source address, and do not block entire /owa, /autodiscover or /Microsoft-Server-ActiveSync directories, which would break mail for every user. Blocking by source IP is the wrong control here because ESET found no operator infrastructure to block. A listener registration for one of these prefixes is a confirmed implant and should be escalated immediately; repeated requests from one source to these paths, without a registration, should be triaged with the first lead before closing.

Hunt Lead Level: 2 (Pro)

ATT&CK: Command and Control → T1071.001 (Application Layer Protocol: Web Protocols)

Sources: ESET blog post (above), additional source; source article (above)

EdgeTransport In-Memory Tampering and Mail Staging

CerealBox reaches EdgeTransport.exe, Exchange’s mail-flow process, through a chain of nested Cereal components (CerealIron is the injector that lets .NET assemblies run inside non-.NET processes), then walks Exchange’s internal structures, finds the transport agents already loaded and wraps their handlers so its own logic runs first and control is handed back to the original code. No transport agent is registered, so Get-TransportAgent and configuration audits show nothing new; this is why ESET describes it as a technique not previously documented for any malware family, and why a transport-agent audit, the usual control for Turla’s earlier LightNeuron-style mail implants, is the wrong check on its own. Qualifying messages (a .doc, .docx or .pdf attachment plus a match on hardcoded sender, recipient, subject or attachment-name lists, minus ignore lists) are compressed, encrypted and written to staging files, which the operators later read and delete through CerealNeuron commands. The correlation to build joins three signals on one server: a process other than Exchange’s own services opening EdgeTransport.exe with memory-write or thread-creation rights (or EdgeTransport loading an in-memory, unbacked .NET module), EdgeTransport writing new high-entropy files outside its queue, log and temp folders, and later reads and deletions of those same files by a process launched via the Exchange worker or WMI chain.

Use EDR process-access and memory telemetry (Sysmon event IDs 8 and 10 where EDR lacks it), .NET runtime ETW for assembly loads in EdgeTransport.exe, and file-create and file-delete events. Baseline EdgeTransport’s normal file writes and loaded modules for 30 days, then sweep back to November 2025. Scope to Mailbox and Edge Transport servers, starting with those handling mail for diplomatic, defense and government correspondents. Antivirus, journaling and archiving products also touch EdgeTransport; allowlist them by signed image path and vendor, and confirm their registered agents with Get-TransportAgent so that only unregistered behavior remains. Expect EDR visibility inside a .NET process to be imperfect, so give the file-staging and deletion leg weight in its own right. Any correlated hit means mail is being siphoned and should go straight to incident response, with an assessment of which correspondents were in the hardcoded lists; the approach generalizes to any implant that hooks a mail server in memory rather than through configuration.

Hunt Lead Level: 3 (Elite)

ATT&CK: Defense Evasion, Privilege Escalation → T1055 (Process Injection); Collection → T1114 (Email Collection); Collection → T1074.001 (Data Staged: Local Data Staging) (related: T1505.002 (Server Software Component: Transport Agent), not used directly, since no agent is registered)

Sources: ESET blog post (above), additional source; source article (above)

Hash Appendix

Cereal toolset

SHA1 values come from ESET’s malware-ioc repository (an additional source on the same campaign); ESET did not publish MD5 or SHA256 values, and an OTX AlienVault lookup of the ncobjapi.dll hash returned no record, so those are not available. The file names are those of legitimate Windows and Exchange components; these hashes are of ESET-identified malicious files, so do not block the names themselves.

MD5s

(not available)  # Microsoft.Exchange.Data.Transport.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # version.dll -> CerealLoader sample 1 (MSIL/Agent.YCC)
(not available)  # version.dll -> CerealLoader sample 2 (MSIL/Agent.YCC)
(not available)  # Microsoft.Search.Platform.dll -> CerealLoader (MSIL/Agent.YCA)
(not available)  # Microsoft.Ceres.dll -> CerealLoader (MSIL/Agent.YCA)
(not available)  # wbemcomn.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
(not available)  # EdgeTransport.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # iph.dat -> CerealLoader (MSIL/Agent.YCA)
(not available)  # ncobjapi.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
(not available)  # Microsoft.Exchange.Search.Mdb.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # Microsoft.Exchange.EdgeSyncSvc.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # CerealRunner -> encrypted command carrier (MSIL/Agent.YBZ)
(not available)  # CerealSprinter -> component loader (MSIL/Agent.YBZ)
(not available)  # CerealHermit -> disk-based backdoor variant (MSIL/Agent.YBZ)
(not available)  # CerealIron -> injector for non-.NET processes (MSIL/Agent.YBZ)
(not available)  # CerealMoth -> assembly and method runner (MSIL/Agent.YBZ)
(not available)  # bootstrapper DLL (x86) -> Win32/Agent.AIOQ
(not available)  # bootstrapper DLL (x64) -> Win32/Agent.AIOQ

SHA1s

4A3C263977417FB6977B0E598C9E3BC5924F390C  # Microsoft.Exchange.Data.Transport.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
7742C6B0AAF114335CEF7EBAB11290CB18A0B8B3  # version.dll -> CerealLoader sample 1 (MSIL/Agent.YCC)
AFE448DD95494CD14438F04F0C5F6B384664A3B7  # version.dll -> CerealLoader sample 2 (MSIL/Agent.YCC)
4A65040646E354303F067D47AA1C953D467F65CB  # Microsoft.Search.Platform.dll -> CerealLoader (MSIL/Agent.YCA)
D1E17520A2435EDCDCC47F582381416FBDF75F94  # Microsoft.Ceres.dll -> CerealLoader (MSIL/Agent.YCA)
7AB784D0049890D9844AEE7F214BA173E3CC23BE  # wbemcomn.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
5D80118B1EE974936322475F740AB3AEFF70B8F3  # EdgeTransport.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
D51C58C2E95D4561848E0A5A8B9FB33C847C50A4  # iph.dat -> CerealLoader (MSIL/Agent.YCA)
5B94FE76EC4FEB0B5CB6EA3BCA4C48D2FE22597B  # ncobjapi.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
1408A8F62B09A5AD0DFF279B2878D8F59F70A330  # Microsoft.Exchange.Search.Mdb.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
3D1A534CE0D0C293F62ECE556CBC6D0728213104  # Microsoft.Exchange.EdgeSyncSvc.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
AD85FBF2CC879D4325BCE1E6FB5F12AB59E3D387  # CerealRunner -> encrypted command carrier (MSIL/Agent.YBZ)
3EA03188DBA8898D97E965732C1D6A68C5437EDC  # CerealSprinter -> component loader (MSIL/Agent.YBZ)
3FBA18AF966DEACF7AE09E4D4238952DD90A6D6F  # CerealHermit -> disk-based backdoor variant (MSIL/Agent.YBZ)
EB9BA1DA5363F5D04E2F98673595FCE93F39A78E  # CerealIron -> injector for non-.NET processes (MSIL/Agent.YBZ)
0B4E4A1CE7FEE91BFC62B2A2EC572C325642BB60  # CerealMoth -> assembly and method runner (MSIL/Agent.YBZ)
A4E477CE257F2C635401EF554E05506C080967C0  # bootstrapper DLL (x86) -> Win32/Agent.AIOQ
A5BE8706032A0798FD63214A9F22EFA6309355F5  # bootstrapper DLL (x64) -> Win32/Agent.AIOQ

SHA256s

(not available)  # Microsoft.Exchange.Data.Transport.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # version.dll -> CerealLoader sample 1 (MSIL/Agent.YCC)
(not available)  # version.dll -> CerealLoader sample 2 (MSIL/Agent.YCC)
(not available)  # Microsoft.Search.Platform.dll -> CerealLoader (MSIL/Agent.YCA)
(not available)  # Microsoft.Ceres.dll -> CerealLoader (MSIL/Agent.YCA)
(not available)  # wbemcomn.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
(not available)  # EdgeTransport.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # iph.dat -> CerealLoader (MSIL/Agent.YCA)
(not available)  # ncobjapi.dll -> C:\Windows\System32\wbem\, CerealLoader (MSIL/Agent.YCA)
(not available)  # Microsoft.Exchange.Search.Mdb.ni.dll -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # Microsoft.Exchange.EdgeSyncSvc.ni.exe -> .NET native image cache, CerealLoader (MSIL/Agent.YCC)
(not available)  # CerealRunner -> encrypted command carrier (MSIL/Agent.YBZ)
(not available)  # CerealSprinter -> component loader (MSIL/Agent.YBZ)
(not available)  # CerealHermit -> disk-based backdoor variant (MSIL/Agent.YBZ)
(not available)  # CerealIron -> injector for non-.NET processes (MSIL/Agent.YBZ)
(not available)  # CerealMoth -> assembly and method runner (MSIL/Agent.YBZ)
(not available)  # bootstrapper DLL (x86) -> Win32/Agent.AIOQ
(not available)  # bootstrapper DLL (x64) -> Win32/Agent.AIOQ

References Appendix

  • “Turla hackers use new Cereal malware to spy on govt Exchange servers”, BleepingComputer, Nov. 10, 2026, https://www.bleepingcomputer.com/news/security/turla-hackers-use-new-ceral-malware-to-spy-on-govt-exchange-servers/ (source article; campaign summary)
  • “Exchange for breakfast: Turla’s Cereal tricks are not for kids”, ESET WeLiveSecurity (Matías Porolli), Nov. 2026, https://www.welivesecurity.com/en/eset-research/exchange-for-breakfast-turlas-cereal-tricks-are-not-for-kids/ (additional source; components, loading, listener paths, CerealBox, attribution)
  • “Exchange for breakfast: Turla’s Cereal tricks are not for kids – Indicators of Compromise”, ESET malware-ioc repository on GitHub, Nov. 2026, https://github.com/eset/malware-ioc/tree/master/turla (additional source; SHA1 hashes, file names, detection names)
  • OTX AlienVault indicator lookup for 5B94FE76EC4FEB0B5CB6EA3BCA4C48D2FE22597B, checked Nov. 10, 2026, https://otx.alienvault.com/indicator/file/5B94FE76EC4FEB0B5CB6EA3BCA4C48D2FE22597B (no record)
  • MITRE ATT&CK Enterprise technique pages linked above, MITRE, https://attack.mitre.org/

More from the Roundup