Skip to main content

Worked Examples: Actor Research

Purpose

Show the minimum evidence structure for an actor profile that supports defensive action. Section A uses a fully synthetic teaching example. Section B uses MuddyWater / TEMP.Zagros as a real public-source case — every claim in Section B is traceable to a public government advisory or authoritative vendor report and is labeled accordingly.


Section A — Synthetic Teaching Example

Alias Table

AliasSourceEvidence LabelCaveat
Example ClusterVendor A reportReportedVendor-specific naming.
Example KittenVendor B reportReportedMay overlap partially, not necessarily one-to-one.
Public persona nameGovernment advisoryReportedPersona is not automatically the operational cluster.

Source Chronology

DateSourceClaimUse
2024-09-19Primary vendor reportDescribes persistent access tooling.Tool and TTP evidence.
2025-03-10Government advisoryDescribes sector targeting.Relevance and defensive prioritization.
2026-05-16Local reviewNo new primary source found.Freshness and gap statement.

Actor Claim Table

ClaimEvidence LabelConfidenceFreshness DateDetection Implication
Actor uses webshells on edge servers.ReportedMedium2026-05-16Monitor web root file creation and server process anomalies.
Actor is linked to a specific sponsor.AssessedLow/Medium2026-05-16Do not use sponsor claim as detection logic.
Actor targets the local sector.ReportedMedium2026-05-16Prioritize relevance scoring and telemetry review.

TTP Mapping With Evidence

TechniqueBehavior EvidenceMapping ConfidenceQualityRejected Alternative
T1505.003 Server Software Component: Web ShellSource reports webshell persistence on internet-facing server.MediumM2T1190 rejected for this row because exploitation was not described in enough detail.

Section B — Real Public-Source Case: MuddyWater / TEMP.Zagros

Scope and caveat: This section uses only public, TLP:CLEAR sources: the joint CISA/NSA/FBI/CNMF advisory (February 2022), MITRE ATT&CK actor page, and publicly available vendor reporting. Every claim carries an evidence label. This is an analyst tradecraft exercise using public defensive intelligence. It is not an attribution determination.

Sources used:

Source IDPublisherTitleDateReliability
SRC-MW-001CISA / NSA / FBI / CNMFIranian Government-Sponsored APT Actor Threatens Public and Private Sectors2022-02-24A
SRC-MW-002MITRE ATT&CKMuddyWater (G0069)OngoingA
SRC-MW-003Multiple vendors (Trend Micro, Talos)Referenced from CISA advisory and MITRE pageVariousB–C

PIR / SIR Framing

Decision owner: Detection Engineering Lead
Decision: Which MuddyWater behaviors from public reporting are observable with current
endpoint, email, identity, and DNS telemetry, and should any enter a 30-day
hunt backlog?

PIR-001: Which reported MuddyWater initial access, execution, and persistence behaviors
are relevant to an organization with Windows endpoints, Microsoft 365,
and internet-facing remote access services?

SIR-001: What initial access vectors does MuddyWater use according to primary reporting?
SIR-002: What execution and persistence techniques are described with behavior evidence?
SIR-003: Which techniques have sufficient telemetry to support a hunt hypothesis?
SIR-004: Which are only actor-level claims without observable procedure evidence?

Alias Table

AliasSourceEvidence LabelCaveat
MuddyWaterMultiple vendors; referenced in CISA advisoryReportedVendor-assigned; not universally standardized
TEMP.ZagrosMandiant / FireEye historical reportingReportedMandiant-specific naming convention
Static KittenCrowdStrikeReportedCrowdStrike-specific naming convention
SeedwormSymantecReportedSymantec-specific naming convention
MercuryMicrosoftReportedMicrosoft-specific naming convention
Earth VetalaTrend MicroReportedTrend Micro-specific naming convention

Alias caveat (Reported / Medium confidence): CISA advisory (SRC-MW-001) uses the MuddyWater label and attributes it to Iran's Ministry of Intelligence and Security (MOIS). MITRE ATT&CK (SRC-MW-002) aggregates the above aliases under G0069. Vendor alias equivalence is source-reported; independent forensic confirmation of full cluster equivalence is not always documented in public reporting. Do not merge aliases across vendors without checking each vendor's stated rationale.

ClaimEvidence LabelSourceConfidence
MuddyWater is assessed to be a subordinate element of Iran's Ministry of Intelligence and Security (MOIS)AssessedSRC-MW-001 (joint US government advisory)Medium confidence — government attribution statement; public forensic chain is not fully published.

Caveat: The government attribution statement is the strongest public basis for sponsor assessment. It does not include full forensic chain disclosure, as is normal for government advisories. Do not treat the sponsor claim as Observed; it is a government assessment (Reported/Assessed). An alternative hypothesis — contracted operator with MOIS affiliation — is not ruled out by public evidence.

Source Chronology

DateSourcePrimary ClaimEvidence LabelDownstream Use
2022-02-24CISA/NSA/FBI/CNMF advisoryBroad TTP and IOC disclosureReportedInitial access, execution, persistence hunt candidates
OngoingMITRE ATT&CK G0069Technique aggregation from multiple reporting streamsReported/AssessedATT&CK mapping validation
2026-05-16Local reviewNo new primary source found in 2025–2026 periodGapFreshness caveat; reassess before operational use

Actor Claim Table

ClaimEvidence LabelSourceConfidenceDetection Implication
Uses spear-phishing emails with malicious links or attachments for initial accessReportedSRC-MW-001MediumEmail gateway log review; phishing attachment hunt
Uses commercial and open-source remote administration tools (RATs) including ScreenConnect, RemoteUtilitiesReportedSRC-MW-001MediumNon-IT host RMM install hunt; HUNT-MW-001
Uses PowerShell-based tools and scripts for execution and C2ReportedSRC-MW-001, SRC-MW-002MediumPowerShell commandline logging; obfuscation patterns
Uses custom backdoors and off-the-shelf tools (e.g., Mori, POWERSTATS)ReportedSRC-MW-001, SRC-MW-002MediumFile hash and behavior hunting; tool association requires freshness date
Targets government, defense, energy, financial, and telecom sectors globallyReportedSRC-MW-001MediumSector relevance for prioritization
Sponsor is MOISAssessed (government advisory)SRC-MW-001MediumAffects escalation and reporting; not used for detection logic
Uses DNS-based C2ReportedSRC-MW-002 (technique T1071.004)Low-MediumDNS query anomaly hunting; confidence limited because procedure details are aggregated

ATT&CK Mapping With Evidence and Quality

Technique IDTechnique NameBehavior EvidenceEvidence LabelMapping ConfidenceQualityRejected / Downgraded
T1566.001Spear-Phishing AttachmentAdvisory describes attachment deliveryReportedMediumM2T1566.002 (link) added as separate row — both are described
T1566.002Spear-Phishing LinkAdvisory describes link deliveryReportedMediumM2Not rejected; both observed
T1059.001PowerShellAdvisory describes PowerShell-based tools and scriptsReportedMediumM2CommandLine details not fully provided; procedure is partially described
T1021.001Remote Services: Remote Desktop ProtocolAdvisory mentions RDP useReportedLow-MediumM1Advisory does not specify RDP as primary vector; mapped at actor level
T1219Remote Access SoftwareAdvisory specifically names commercial RATs including ScreenConnectReportedHighM3Strong behavioral description; specific tool named
T1071.004Application Layer Protocol: DNSMITRE aggregation; procedure details not fully specified in primary sourceReportedLowM1Not directly described in the CISA advisory with procedure detail; aggregated from multiple vendor reporting
T1053.005Scheduled Task/Job: Scheduled TaskAdvisory describes persistence via scheduled tasksReportedMediumM2Specific scheduling pattern not provided

Mapping quality legend: M1 = actor-level claim only; M2 = behavior described without full procedure; M3 = specific procedure or tool described.

Telemetry Requirements for Hunt Candidates

BehaviorData SourceRequired FieldsConfirmed AvailableGap
Commercial RAT install on non-IT hostEDR software inventoryproduct_name, install_time, host, userUnknown — validateNeed: confirm field population
PowerShell execution with obfuscationEDR process / Sysmon EventID 1CommandLine, ParentImage, UserUnknown — validateNeed: confirm command-line audit policy enabled
Phishing attachment — script spawnEmail gateway + EDRrecipient, attachment_hash, process_name, parentUnknown — validateNeed: email-to-EDR correlation
Unusual scheduled task creationWindows Security EventID 4698TaskName, TaskContent, SubjectUserNameUnknown — validateAudit policy may not capture task content

Hunt Hypotheses (DRL-1 Candidates)

HUNT-MW-001
Hypothesis: If MuddyWater-style RAT is used after phishing, then a non-IT endpoint
will show a new remote access software install followed by an external remote session
without a change ticket.
Source Claim: EV row for T1219 above (SRC-MW-001)
DRL: 1 (source-backed candidate; no telemetry mapping, no logic, no testing yet)
Next Step: Validate EDR software inventory fields and network session logging.

HUNT-MW-002
Hypothesis: If PowerShell-based tools are used for execution, then endpoints will show
PowerShell with unusual encoded or obfuscated command-line arguments.
Source Claim: EV row for T1059.001 above (SRC-MW-001)
DRL: 1 (source-backed candidate; no telemetry mapping, no logic, no testing yet)
Next Step: Confirm command-line audit policy enables CommandLine field in process events.

SOC Handoff Note (Illustrative — Not a Production Alert)

Handoff ID: SOC-MW-DRAFT-001
Status: DRL-1 candidate only — not approved for alerting
Alert Name: Non-IT Commercial RAT Install (MuddyWater-Style Behavior)
Why It Matters: Government advisory (SRC-MW-001) attributes commercial RAT use to a
state-sponsored actor targeting government, defense, and telecom.
First Checks: Host owner, business role, install source, ticket, remote session destination.
Required Logs: EDR software inventory, process events, network, identity, ticketing.
False Positives: Helpdesk deployment, vendor support, IT migration, remote work tooling.
Escalation: No ticket + external session + suspicious pre-install activity.
Gaps: Telemetry fields not yet validated. No historical baseline completed.
DRL: 1 — cannot be used as a production alert.

Executive Summary (Illustrative)

Decision: Approve two 30-day hunt hypotheses for MuddyWater-style behaviors.
Bottom Line: Public government reporting justifies a scoped hunt for commercial RAT
installation and PowerShell obfuscation. No production alerting yet.
Why Now: The 2022 CISA/NSA/FBI/CNMF advisory is the primary public source.
No 2025–2026 primary source was identified. Freshness is a risk.
Confidence: Medium — government advisory is reliable; telemetry not yet validated.
Business Impact: Commercial RATs could enable persistent unauthorized remote access.
Recommended Actions: (1) Validate telemetry fields. (2) Approve DRL-1 hunt candidates
for 30-day scoped run. (3) Reassess when new primary source appears.
Limitations: No local compromise evidence. No freshness confirmation for 2026.
Owner: Detection Engineering Lead and SOC Lead.

Gaps and Collection Tasks

GapImpactCollection PathOwner
No 2025–2026 primary source foundFreshness risk; actor behavior may have evolvedMonitor CISA, vendor advisories for updatesCTI Analyst
Telemetry fields unvalidatedBlocks hunt hypothesis promotion past DRL-1Schema validation by Detection EngineeringDetection Engineering
Alias equivalence not fully documentedAnalyst may accidentally merge separate clustersCheck each vendor's stated cluster rationaleCTI Analyst
DNS-based C2 procedure details thinLow-confidence mapping; may generate noisy huntsSeek more specific procedure reporting before huntingCTI Analyst

References