Middle East oil, gas and telecom — built for one region.
Also tracked as COBALT LYCEUM · HEXANE · UNC1530 · Spirlin · MYSTICDOME · siamesekitten · Chrono Kitten · Storm-0133 · Lyceum · Siamesekitten · Hexane · Cobalt Lyceum
Summary
LYCEUM is a threat actor attributed to Iran (Islamic Republic of), assessed as espionage-motivated. Its recorded targeting runs to government, energy, high-tech, telecomms and adjacent sectors across 2 countries in the open reporting we hold — Middle East among them.
Across 36 attributed ATT&CK techniques we resolve 9 distinct behaviours — the things they do that a detection can be written against. The two that account for most of their observed tradecraft are discovery command burst on one host and persistence pointing into world-writable staging. Their toolkit is 12 named items: 5 we see only in this actor's reporting and 7 commodity or dual-use. That ratio is the point — the first group is what identifies them, the second is what they share with every other group and with red teams.
For a Gulf defender the relevant line is the victimology: Middle East appear in the reporting behind this record. That is evidence of past targeting, not a forecast, and it is drawn from what vendors chose to publish — an actor working quietly in a market nobody reports on looks identical to one that is absent.
As MITRE describes them: “Lyceum is an Iranian APT group that has been active since at least 2014. They primarily target Middle Eastern governments and organizations in the energy and telecommunications sectors. Lyceum is known for using cyber espionage techniques and has been linked to other Iranian threat groups such as APT34. They have developed and deployed malware families like Shark and Milan, and have been observed using DNS tunneling and HTTPfor command and control communication.” — MITRE ATT&CK, CC BY 4.0.
On the name. “LYCEUM” labels a cluster of related activity tracked under one name — not a verified organisation. Whether one team, several contractors or a rotating cast sits behind it is not something this record establishes, and the vendor names below are separate groupings that only mostly overlap.
02 — The detection plan
Most actor profiles hand you indicators that expire in days. These are the behaviours the actor cannot drop without changing how they operate, each with the reason it holds. Weight is our own: how much of the actor's observed tradecraft the behaviour accounts for.
The persistence mechanism and the directory it points at both outlive the payload. The discriminator is the TARGET PATH, not the task or key name, which the actor can change freely.
8 techniques · weight 5
The delivery wrapper changes constantly; an office, archive or browser process parenting a shell is the same shape across all of them.
8 techniques · weight 5
Defeats egress-domain control outright — the destination is a platform the estate already permits, so no blocklist and no TLD heuristic will see it.
7 techniques · weight 4
Kept separate from the LSASS rule because it needs different telemetry and tunes differently — a browser credential store read by a non-browser process is its own signal.
8 techniques · weight 4
The command-line SHAPE — the flag combination, not the payload — is stable for months to years and cheap to match.
8 techniques · weight 4
Visible only in identity telemetry, and the failure-then-success shape is what distinguishes it from ordinary user error.
6 techniques · weight 3
The set of system binaries that can fetch a file is small and changes with the OS, not with the actor.
5 techniques · weight 3
Lateral movement leaves a service-creation or admin-share write that is the same regardless of the tool that made it.
6 techniques · weight 3
No single discovery command is worth an alert. The DENSITY is — several distinct recon binaries on one host inside an hour is a shape ordinary use does not produce.
17 techniques · weight 2
No single behaviour here is worth waking someone. Summed weights of 6 on one host inside a window is an alert; 10 is an incident. The pair that most reliably means this actor rather than commodity crime is Persistence pointing into world-writable staging + User-facing application spawning an interpreter — seen together, treat as an incident regardless of total.
03 — Tooling
Purpose is derived, not asserted: each tool's own ATT&CK techniques are resolved to tactics, and the tactics it spends most of its techniques in are what it is for.
Actor-specific means we have no record of it outside this actor's reporting — those are the names that identify them. Commodity covers everything sold, published or shared: Cobalt Strike and Brute Ratel are licensed red-team software every pentester owns, Mimikatz and Impacket are public, and backdoors like ShadowPad circulate between unrelated groups. Finding a commodity tool tells you far less, which is exactly why the split is drawn. ATT&CK's own “malware vs tool” type answers a different question — whether the software is malicious — so it is not used for this.
Actor-specific — 5 items
Gathering data and moving data out.
Gathering data and remote control.
Gathering data and moving data out.
Gathering data and first access.
Gathering data and moving data out.
Commodity and dual-use — 7 items
Credential theft and gathering data.
Credential theft and gathering data.
Credential theft and moving between hosts.
Moving data out and moving between hosts.
We hold none. Our corpus carries 9,780 hashes, but they come from live feeds covering current commodity campaigns — not the decade-old actor-specific backdoors in the list above. ATT&CK itself publishes no sample hashes; it is a technique knowledge base. Where a sample would have to come from a third party’s family tag rather than from this actor’s reporting, we leave the row empty instead of implying an attribution we cannot support.
04 — Coverage, honestly counted
Of the techniques attributed to LYCEUM, 24 fold into the detection plan above, 10 describe preparation you cannot see from inside your network, and 2 are uncatalogued — we have not yet placed them. That last number is published on purpose; it is the honest size of the gap.
05 — The chain
The same techniques as above, sequenced. Useful for deciding where to spend a detection: the earlier a tactic sits, the more of the intrusion you still get to prevent.
06 — Tradecraft artefacts
Pulled from primary vendor research and kept attributed. These are hunt starting points, not detections — a path an actor used once is worth a query, not a rule.
| Artefact | Kind | First reported by | Date |
|---|---|---|---|
| %programdata%\WinDir\WinDirStat.exe | file path | Check Point Research | 2026-07-06 |
| %userprofile%\Desktop\Modules\cavern\ | file path | Check Point Research | 2026-07-06 |
| %appdata%\Local\LEAP | file path | ESET | 2025-06-05 |
| %appdata%\Local\Microsoft\InputPersonalization\TrainedDataStore.ps1 | file path | ESET | 2025-06-05 |
| %appdata%\Local\Microsoft\Windows\Ringtones\RingService.exe | file path | ESET | 2025-06-05 |
| %appdata%\Local\Microsoft\Windows\Shell\mspsrv.exe | file path | ESET | 2025-06-05 |
| %appdata%\Roaming\Microsoft\Windows\Start | file path | ESET | 2025-06-05 |
| %programdata%\VeeamUpdate | file path | ESET | 2025-06-05 |
| %programdata%\WebDeepPlayer.scr | file path | Unit 42 | 2026-03-16 |
| %programdata%\~tmp.log | file path | ESET | 2025-06-05 |
| HKCU\Software\Classes\.wdlp | registry | Unit 42 | 2026-03-16 |
| HKCU\Software\Microsoft\Windows\CurrentVe | registry | ESET | 2025-12-02 |
07 — Sourcing, graded
NATO Admiralty grading. The letter is the source's reliability, the number the credibility of the claim. We separate primary vendor research from outlets reporting on it, because ten articles derived from one report is one report.
| Grade | Source | Basis |
|---|---|---|
| B2 | MITRE actor record | 15 references across 13 distinct research hosts |
| B2 | ESET | 4 items — primary vendor research |
| B2 | Group-IB | 2 items — primary vendor research |
| B2 | Check Point Research | 2 items — primary vendor research |
| B2 | Unit 42 | 1 item — primary vendor research |
| C3 | BleepingComputer | 1 item — reporting on other vendors' research |
| C3 | SecurityWeek | 1 item — reporting on other vendors' research |
| C4 | otx | 7 indicators; 0 of 7 corroborated by a second source |
| C3 | article_auto | 1 indicators; 1 of 1 corroborated by a second source |
| — | Estate telemetry | no data — absent, not negative |
11 items · 6 outlets · 36% of reporting traces to a single outlet
08 — What we do not know
Every vendor profile has these. Most omit them, which leaves you unable to tell a quiet actor from an unobserved one.
No URI paths, headers or beacon sequences for any family we hold, and no URL indicators at all to derive them from — the indicator set is hashes, hosts and addresses.
09 — Outlook
Probability language is ICD 203. Likelihood and confidence are stated separately: how likely we think it is, and how good our basis is for thinking so.
11 — Related actors
Ranked by shared victimology first, shared attribution second. The reason is on each card.
The Gulf energy and telecom operator-set, worked continuously for a decade.
Saudi aviation and petrochemical, with a wiper in the toolkit.
Credential phishing at scale against Gulf government and academic mail.
10 — Primary sources
15 of them. Published in full so the page can be checked rather than believed.
Run it against your own estate
The library is the part we can publish. The platform runs the same detection plan against your own estate, tells you which of these behaviours you already cover, and retro-hunts the rest — on your hardware, with nothing leaving the building.