UNC3886

China-Nexus Espionage Threat Model - Network and Virtualization Infrastructure
JUNIPER / FORTINET / VMWAREINITIAL ACCESS CAVEATED BY SOURCEMANAGEMENT-PLANE RISKYARA + LOG ARTIFACTS13 SOURCE ARTICLES1,658 SOURCE-PACK ARTIFACTS
01

Executive Summary

Infrastructure-first

Not a single-incident model

UNC3886 is best read as an infrastructure-access actor model spanning network devices, security appliances, and virtualization control planes. It is not a single intrusion chronology or an endpoint-first malware brief.

Direct product scope

Juniper / Fortinet / VMware

The source pack directly supports Juniper routers and Junos OS, FortiGate, FortiManager, FortiAnalyzer, VMware ESXi, vCenter, VMware Tools, vSphere, and VMCI context.

Stealth and persistence

Backdoors in trusted surfaces

TINYSHELL-family router backdoors, malicious ESXi VIBs, VMCI backdoors, Fortinet scripts, and guest operations all point to durable access inside infrastructure administrators trust.

Source-backed

Strong but bounded corpus

The local context is a 13-file Google/Mandiant source pack. It is deep enough for a defensive model, but it is not a claim that every public UNC3886 source on the internet has been exhausted.

Source files
13
local Google/Mandiant pack
Direct relationships
122
UNC3886-scoped rows
Direct CVEs
6
actor-scoped model set
Tools / malware
19
deduped direct values
Targets
4 / 6
products / platforms

Defender takeaway

UNC3886 is best tested as a long-term infrastructure-access scenario. The highest-value exercise is not asking whether a workstation was compromised; it is asking whether routers, Fortinet management appliances, ESXi hosts, vCenter accounts, VMware Tools, and TACACS paths can prove what happened and what did not.

The local source pack also contains eight sector categories, five region categories, and five detection/log artifacts. Those values are useful for scoping hunts and tabletops, but the model keeps them separate from technical tradecraft so broad context does not become overconfident incident proof.

02

Evidence Boundaries

Observed / direct evidence

  • 122 UNC3886-scoped relationship rows directly support the actor model.
  • UNC3886 uses 19 deduped tools or malware families, including TINYSHELL, GHOSTTOWN, VIRTUALPITA, VIRTUALPIE, VIRTUALGATE, CASTLETAP, THINCRUST, TABLEFLIP, REPTILE, MEDUSA, SEAELF, MOPSLED, LOOKOVER, RIFLESPINE, INTFS, Nmap, VIRTUALSHINE, VIRTUALSPHERE, and VIRTUALPEER.
  • Direct product and platform scope covers Juniper routers, FortiGate, FortiManager, FortiAnalyzer, Junos OS, VMware ESXi, VMware vCenter, VMware Tools, vSphere, VMCI, and TACACS.
  • Actor-scoped CVEs include CVE-2025-21590, CVE-2022-41328, CVE-2023-34048, CVE-2023-20867, CVE-2022-22948, and CVE-2022-42475.

Context-only evidence

  • 2023 and 2025 zero-day review material explains exploitation patterns and ownership caveats, but broad trend rows do not become direct UNC3886 claims by default.
  • The VMware defensive companion contributes hardening checks, log paths, containment actions, and detection ideas rather than direct target attribution.
  • Ivanti exploitation reporting and Defense Industrial Base context are useful for sector and ecosystem awareness, but they stay outside the technical path unless UNC3886 is directly named.

Excluded from direct claims

  • UNC5221 is not treated as UNC3886.
  • BRICKSTORM is not promoted into UNC3886 tooling.
  • CVE-2025-0282 is not modeled as an UNC3886 exploit.
  • Broad zero-day trend rows remain context unless the local relationship row is explicitly scoped to UNC3886.
  • Salt Typhoon and Volt Typhoon appear only as distinction context, not as aliases.
BoundaryIncluded valuesHow to use it
Direct relationship corpus122 actor-scoped rows across uses, targets_product, targets_platform, exploits, abuses_service, detected_by, targets_sector, targets_region, and distinct_from.Use these rows as the article's primary evidence inventory.
Modeled pathInitial access, management-plane pivot, and mission outcomes are ordered for defender testing.Use the path as a tabletop and hunt model, not as a confirmed incident timeline.
Context-only sources2023-zero-day-trends, investigating-ivanti-exploitation-persistence, zero-days-exploited-2022, defensive hardening material, and broad sector reporting.Use for caveats, response priorities, and scoping; do not convert to direct actor behavior without an UNC3886-scoped row.

Reading rule

Green means directly extracted or quote-backed. Amber means modeled or caveated. Red means a useful validation gap. This page is an analyst-facing model for defenders, not a chronology.

Primary source anchors: Cloaked and Covert | Ghost in the Router | Fortinet malware ecosystem | ESXi hypervisor persistence

03

Actor & Asset Model

Actor frame

UNC3886 is treated as a China-nexus espionage actor with a demonstrated focus on stealthy, long-term access to network and virtualization technologies. Public reporting explicitly separates some activity from Volt Typhoon and Salt Typhoon overlap claims.

Assets at risk

The core assets are management-plane systems: Juniper routers, Fortinet security appliances, ESXi hosts, vCenter, VMware Tools, VMCI, TACACS, and the credentials or service accounts that administer them.

Trust boundary

The model centers on three boundaries: external or partner reachability into appliances, appliance-to-management-plane access, and ESXi-host-to-guest-VM operations through VMware Tools or VMCI.

04

Threat Model Detail

Scope

This is the working threat model for UNC3886 across the source-pack articles. It converts normalized product, platform, detection, and hardening details into a defensive model while preserving caveats around broad trend context.

StageAsset / surfaceEntry pointPreconditionsTrust boundary crossedAbuse caseTelemetry and controls
Caveated initial accessInternet-facing or partner-reachable appliances and virtualization servicesPublic-facing exploitation context including Juniper, Fortinet, VMware, and edge appliance reporting.Management service reachable; vulnerable version or privileged access path exists.External or semi-trusted path into infrastructure administration.Convert a perimeter or appliance weakness into long-term management-plane access.Exposure review, emergency patching, appliance access allowlists, edge/VPN correlation, and source-specific CVE validation.
Identity controlTACACS, vCenter service accounts, ESXi credentials, Fortinet administrator pathsValid credentials, backdoored TACACS binary, or privileged service-account use.Credentials are reusable or management authentication lacks strong monitoring.Authenticated infrastructure identity into downstream control surfaces.Blend into legitimate network and virtualization administration.TACACS logs, vCenter events, ESXi authentication records, service-account review, MFA where supported, and privileged access separation.
ExecutionJunos shell, Fortinet appliances, ESXi hosts, guest VMsShell commands, scripts, process injection, VMware Tools Guest Operations, or appliance file writes.The actor has privileged device or management-plane access.Management access into code execution on infrastructure systems.Run commands where endpoint tooling may not exist or may be blind.Junos shell audit, Fortinet file/process telemetry, ESXi hostd/vmsvc logs, VMware Tools debug logging, and guest process telemetry.
PersistenceRouters, ESXi boot profiles, VMCI sockets, Fortinet scripts and servicesTINYSHELL backdoors, malicious VIBs, VMCI backdoors, CASTLETAP/TABLEFLIP/THINCRUST components, or Fortinet script persistence.Write access to durable appliance, host, or service paths.Runtime compromise into persistent infrastructure foothold.Maintain stealthy access inside devices that are hard to reimage, inspect, or instrument.Known-good baselines, VIB inventory, VMCI socket review, Junos and Fortinet filesystem comparison, YARA scanning, and service-state hardening.
Discovery and lateral movementvCenter, ESXi, guest VMs, network device management, authentication servicesVMware Tools operations, VMCI, SSH, TACACS, Nmap, appliance-to-management paths.Network segmentation permits management-plane reachability.One infrastructure surface into another management or guest context.Identify systems, move through virtualization paths, and reach protected workloads without normal endpoint paths.East-west management flows, vCenter task history, ESXi shell/SSH logs, VMCI activity, and appliance-to-vCenter traffic.
Data access and mission impactProtected workloads, guest VMs, telecom/technology/government environments, DIB targetsManagement-plane privileges or host-to-guest control.Compromised infrastructure has enough access to inspect, stage, or influence sensitive systems.Infrastructure control plane into enterprise data or operational continuity.Collect data, maintain covert access, or preserve strategic espionage reach.Guest access logs, SaaS/document repository review, privileged session correlation, and containment paths that protect operations.
Detection and hardening layerYARA rules, VMware logs, Junos/Fortinet integrity checks, ESXi servicesDetection artifacts do not prove compromise by themselves; they define what should be queryable.Logs and files are retained and can be collected without destroying evidence.Evidence capture into response decision-making.Turn source-pack artifacts into actionable hunt and hardening work.M_Hunting_TINYSHELL_5, M_Utility_GHOSTTOWN_1, M_APT_VIRTUALPITA_1, M_Hunting_Backdoor_CASTLETAP_1, /var/log/hostd.log, /tmp/vmsvc.log, /Windows/Temp/vmsvc.log, and ESXi lockdown/firewall/SSH checks.

Primary assumptions

  • At least one management surface is reachable by the actor.
  • Appliance and virtualization logs are incomplete unless explicitly retained.
  • Infrastructure administrators can safely collect evidence without wiping volatile state.

Key abuse cases

  • Use router or appliance access to harvest credentials and suppress logs.
  • Use ESXi/vCenter privileges to execute commands through VMware Tools.
  • Use VMCI or malicious VIBs for stealthy host-to-guest persistence.
  • Use Fortinet management appliances as a bridge to ESXi or vCenter.

Decision points

  • Can the team prove which appliance or host was first touched?
  • Can logs connect service-account use to Guest Operations or shell execution?
  • Can defenders distinguish expected administration from actor tradecraft?
05

Attack Chain - Evidence-Aware Model

STEP 01
caveated
Initial Access
Exploit or reach high-trust appliance and virtualization management surfaces. The first entry path remains source-dependent.
T1190
STEP 02
observed
Identity Control
Use legitimate credentials or authentication services such as TACACS, vCenter, ESXi, and Fortinet administration.
T1078 / TACACS
STEP 03
observed
Execution
Run shell commands, scripts, process injection, or VMware Tools Guest Operations from trusted infrastructure contexts.
T1059 / Guest Ops
STEP 04
observed
Persistence
Install router backdoors, malicious VIBs, VMCI backdoors, or Fortinet appliance persistence.
TINYSHELL / VIB / VMCI
STEP 05
modeled
Management Pivot
Move from appliances or ESXi hosts into vCenter, guest VMs, authentication services, or adjacent management networks.
T1021 / VMCI
STEP 06
gap
Mission Outcomes
Collection, staging, exfiltration, and operational impact require victim-specific evidence before promotion.
validation gaps
06

Technical & Forensic Anchors

Juniper / Junos OS

Review shell access, process injection, Veriexec bypass context, disabled logging mechanisms, TACACS binary integrity, and TINYSHELL-family artifacts on router filesystems and memory.

VMware / ESXi

Review vCenter tasks, ESXi authentication, boot profiles, VIB inventory, VMCI sockets, VMware Tools Guest Operations, /var/log/hostd.log, and guest process telemetry.

Fortinet appliances

Review FortiGate, FortiManager, and FortiAnalyzer command execution, file writes, scripts, SSH connections, THINCRUST/CASTLETAP/TABLEFLIP artifacts, and follow-on ESXi access.

Malware and Tool Behavior Notes

Family / toolRole in this modelBehavioral notesEvidence boundary
TINYSHELLRouter backdoor family anchor.Reported as TINYSHELL-based backdoors on Juniper Junos OS routers with active/passive capabilities and logging-disruption context.Use for router persistence, memory review, YARA scanning, and TACACS/logging validation.
GHOSTTOWNAnti-forensics utility.Useful as a detection and log-integrity validation point in the Juniper router context.Supports forensic review and YARA hunting; not a standalone initial access claim.
VIRTUALPITA / VIRTUALPIE / VIRTUALGATEVMware ecosystem persistence and execution context.Tied to ESXi/vCenter/VMware Tools tradecraft, malicious VIBs, guest operations, and host-to-guest control paths.Use for ESXi boot profile, VIB inventory, VMCI, and VMware Tools investigations.
THINCRUST / CASTLETAP / TABLEFLIPFortinet malware ecosystem.Supports Fortinet appliance exploitation, persistence, command execution, and follow-on virtualization access review.Keep Fortinet appliance evidence separate from VMware-only detections unless logs connect the stages.
REPTILE / MEDUSA / SEAELFRootkit/loader and persistence context.Appears in network-device and cross-platform UNC3886 reporting as part of a broader stealth ecosystem.Use for host integrity and persistence review, not for over-promoting every observed host action.
MOPSLED / LOOKOVER / VIRTUALSHINE / VIRTUALSPHERE / VIRTUALPEERAdditional operations context.Useful for tool clustering, source-pack memory, and hunting pivots across reports.Treat as source-backed tool context; require incident logs before path-specific conclusions.

Activity Timeline

TimeframeWhat it means for defendersEvidence status
Late 2021 onwardVMware vCenter exploitation context includes CVE-2023-34048 and long-running access concerns.source-backed context
2022ESXi hypervisor persistence reporting describes malicious VIBs and VMware guest operations.source-backed context
2023Fortinet and VMware reporting expands the model into FortiGate/FortiManager/FortiAnalyzer and ESXi/vCenter paths.source-backed context
Mid 2024Mandiant reports discovery of custom backdoors on Juniper Junos OS routers attributed to UNC3886.source-backed context
2025 source reportingJuniper, VMware, and zero-day review material reinforces product/platform scoping and caveats.current source-pack context
07

Relationship Graph

What the graph shows

This graph shows source-backed entity relationships and one modeled management-plane pivot. It is meant for analyst reasoning, not a timeline.

primary actorUNC3886

China-nexus espionage actor with a focus on virtualization technologies, network devices, and security appliances.

targets
relationship-backedJuniper routers / Junos OS / Fortinet / VMware ESXi / vCenter / VMCI

Direct product and platform relationships from operational articles.

uses
toolingTINYSHELL / GHOSTTOWN / VIRTUALPITA / CASTLETAP / THINCRUST / TABLEFLIP

Malware and utilities tied to router, Fortinet, ESXi, and VMware operations.

requires validation for
modeledManagement-plane pivot and mission outcomes

Movement into guest VMs, sensitive workloads, SaaS/document access, or exfiltration should only be promoted with environment-specific logs.

RelationshipSource layerProvenanceConfidenceEvidence note
UNC3886 targets Juniper routers / Junos OSJuniper articleexplicithighBackdoors operating on Juniper Networks Junos OS routers are attributed to UNC3886 in the source pack.
UNC3886 targets FortiGate / FortiManager / FortiAnalyzerFortinet articleexplicithighFortinet appliance exploitation and custom malware are direct product context for the actor.
UNC3886 targets VMware ESXi / vCenter / VMware Tools / VMCIVMware articlesexplicithighESXi, vCenter, VMware Tools, vSphere, and VMCI appear as direct platform relationships.
UNC3886 abuses TACACSJuniper articleexplicithighTACACS daemon replacement and credential capture are identity-control evidence.
UNC5221 / BRICKSTORM context is separatecaveatcontext onlyn/aKeep BRICKSTORM, CVE-2025-0282, and UNC5221 material out of direct UNC3886 rows unless a source explicitly scopes the relationship to UNC3886.
08

ATT&CK Validation Matrix

How to read this matrix

Technique rows group source-pack behavior into validation work. Status describes how the row should be used by defenders, not whether it happened in every victim environment.

IDTechniqueStatusSource layersValidation note
T1190Exploit Public-Facing ApplicationcaveatedJuniper / Fortinet / VMware exploit reportingUse for exposure review and CVE scoping. Keep first entry caveated unless victim logs prove it.
T1078Valid Accountsobserved themeFortinet, Juniper, VMware contextMap TACACS, vCenter, ESXi, and appliance service accounts to owners and logs.
T1059Command and Scripting Interpreterobserved themeJunos shell, Fortinet scripts, VMware Guest OperationsCorrelate management authentication with shell, script, hostd/vmsvc, and guest process events.
T1547 / T1505Autostart or server software persistencemodeled from evidenceRouter backdoors, ESXi VIBs, Fortinet persistenceTurn source artifacts into known-good baseline checks for routers, appliances, and ESXi hosts.
T1021Remote Servicesmodeled from evidenceSSH, ESXi/vCenter, appliance management pathsUse as a trust-boundary test; require flow and auth logs before labeling movement.
T1016 / T1082 / T1083Discoveryobserved themeFortinet and VMware tradecraftCompare discovery commands with normal admin activity on appliances and hosts.
T1074 / T1560Staging and archive behaviorvalidation targetVMware/Fortinet source contextPromote only when staging or archive evidence appears in the victim timeline.
09

Detection & Controls

Juniper / TACACS

  • Run Juniper malware and integrity checks after upgrades.
  • Review TACACS daemon integrity and authentication gaps.
  • Hunt TINYSHELL and GHOSTTOWN YARA names where collection is possible.

VMware / ESXi

  • Review /var/log/hostd.log, /tmp/vmsvc.log, and /Windows/Temp/vmsvc.log.
  • Audit VIBs, boot profiles, VMCI sockets, VMware Tools Guest Operations, and vCenter service accounts.
  • Disable or restrict ESXi Shell, SSH, and unnecessary firewall exceptions.

Fortinet appliances

  • Review appliance file writes, scripts, and SSH connections to ESXi systems.
  • Hunt CASTLETAP, TABLEFLIP, THINCRUST, and REPTILE artifacts.
  • Separate Fortinet compromise evidence from follow-on VMware evidence until logs connect them.

Detection Engineering Matrix

ScenarioLogs neededAnalytic ideaExpected signalFalse positivesControl that breaks it
VMware Tools Guest Operations from unexpected service accountvCenter events, ESXi authentication, hostd/vmsvc logs, guest process logsCorrelate service-account login to Guest Operations and guest process execution in a tight window.Management-plane auth followed by VMware Tools activity and guest command execution.Authorized backup, patching, or orchestration jobs.Dedicated service accounts, least privilege, change-window correlation, and Guest Operations alerting.
Router logging disabled around TACACS activityJunos logs, syslog config, TACACS logs, file integrity records, memory capturesDetect log configuration tampering or missing intervals around privileged shell activity.Authentication activity plus log suppression, daemon replacement, or TINYSHELL hit.Maintenance windows or logging pipeline outages.Immutable log forwarding, TACACS binary integrity checks, and out-of-band router monitoring.
Fortinet appliance initiates ESXi accessFortinet appliance logs, SSH records, ESXi auth, network flowsAlert when Fortinet management infrastructure reaches ESXi/vCenter outside approved patterns.Suspicious file writes or commands on Fortinet followed by ESXi SSH/vCenter access.Documented admin workflows or vendor support.Segmentation, admin path allowlists, and appliance-to-virtualization access review.

Questions That Decide the Case

QuestionEvidence that would confirmEvidence that would weaken
Was the first foothold external, partner-reachable, or already internal?Edge/VPN/appliance logs tied to the first suspicious management action.No perimeter or partner access records before authenticated internal activity.
Did appliance access become VMware control?vCenter or ESXi tasks, Guest Operations, VMCI activity, or service-account actions after appliance compromise.No vCenter/ESXi/guest activity connected to the appliance timeline.
Was persistence present on infrastructure systems?Malicious VIBs, router backdoors, Fortinet scripts, VMCI listeners, or YARA hits.Clean baselines, no unexplained service/file changes, and no detections in preserved evidence.
Did the actor reach data or mission systems?Staging, archive, document access, guest workload access, or unusual privileged sessions.No data-plane evidence after management-plane compromise.
10

Source Evidence Ledger

Deduped evidence view

Repeated claims are grouped here so readers can see how each source layer changes the model without turning context into incident proof. The local source pack has 122 direct UNC3886 relationship rows; the rows below group them by defensive meaning rather than repeating every extraction.

Claim groupSource layerRelationship basisEvidence boundaryHow to use it
Juniper router targetingNetwork device tradecrafttargets_product, targets_platform, uses, exploits, abuses_service, distinct_fromJuniper routers, Junos OS, TINYSHELL-family backdoors, GHOSTTOWN, TACACS, CVE-2025-21590, Salt Typhoon / Volt Typhoon distinction context.Primary evidence for router-focused persistence, TACACS review, Junos OS hardening, and source-specific caveats.
VMware privileged operationsVMware tradecrafttargets_platform, uses, exploits, detected_byVMware ESXi, vCenter, VMware Tools, vSphere, VMCI, malicious VIBs, VIRTUALPITA, VIRTUALPIE, VIRTUALGATE, VMCI backdoors, and host/guest log paths.Primary evidence for hypervisor persistence, Guest Operations detection, host-to-guest validation, and management-plane containment exercises.
Fortinet appliance ecosystemFortinet tradecrafttargets_product, targets_platform, uses, exploits, targets_sectorFortiGate, FortiManager, FortiAnalyzer, THINCRUST, CASTLETAP, TABLEFLIP, REPTILE, and follow-on virtualization access context.Use for appliance forensics, Fortinet-to-VMware pivot validation, and separation of appliance compromise from downstream ESXi evidence.
Direct CVE modelActor-scoped exploit rowsexploitsSix direct CVEs are in the model: CVE-2022-22948, CVE-2022-41328, CVE-2022-42475, CVE-2023-20867, CVE-2023-34048, and CVE-2025-21590.Use these for actor-scoped exposure review. Treat all other CVEs as context until directly scoped to UNC3886.
Targeting contextSector and region rowstargets_sector, targets_regionDefense Industrial Base, aerospace, defense, energy, government, technology, telecommunications, utilities; Africa, Europe, North America, Oceania, Southeast Asia.Use for scoping tabletops and prioritizing environments. Do not treat sector and region rows as technical tradecraft.
Context-only source layersExcluded from direct claimszero direct UNC3886 rows or operational companion context2023-zero-day-trends, zero-days-exploited-2022, investigating-ivanti-exploitation-persistence, and VMware defensive hardening content are useful but bounded.Use for caveats, exclusions, and response guidance. Do not promote UNC5221, BRICKSTORM, CVE-2025-0282, or broad trend claims into UNC3886 behavior.

Direct vs Context CVE Boundary

CVEStatus in this articleSource layerBoundary note
CVE-2022-22948direct UNC3886VMware / operations source layersActor-scoped exploit row; keep in the direct exposure model.
CVE-2022-41328direct UNC3886Fortinet and operations source layersActor-scoped exploit row; use for Fortinet appliance exposure review.
CVE-2022-42475direct UNC3886Fortinet / zero-day review source layersActor-scoped exploit row; keep direct but cite source boundaries.
CVE-2023-20867direct UNC3886VMware source layersActor-scoped exploit row; use for VMware Tools / Guest Operations review.
CVE-2023-34048direct UNC3886VMware vCenter source layersActor-scoped exploit row; use for vCenter exposure and historical access checks.
CVE-2025-21590direct UNC3886Juniper router source layerActor-scoped exploit row; use for Junos OS and router integrity review.
CVE-2025-0282context only / excludedIvanti / UNC5221 contextDo not model as an UNC3886 exploit from this local pack.
Other broad zero-day rowscontext only2022/2023/2025 trend reportsUseful for exploitation background and ownership caveats; not direct actor evidence unless scoped to UNC3886.
11

Response Context

Why this section is separate

These are operational response priorities derived from source-pack hardening and detection material. They are not additional actor relationships.

Exposure

Management surfaces

Inventory internet-facing, partner-reachable, VPN-reachable, and broadly internal Juniper, Fortinet, ESXi, vCenter, and Ivanti management paths.

Ownership

Product accountability

Track Juniper, Fortinet, VMware, and Ivanti product ownership separately from endpoint patch programs. Infrastructure owners need clear containment authority.

Evidence retention

Collect before rebuild

Routers and hypervisors may lose volatile evidence quickly. Preserve logs, memory, VIB inventories, service states, and VMCI indicators before remediation.

Response itemOperational contextHow this changes the model
Router integrityUpgrade Juniper devices, run malware/integrity checks, and preserve TACACS/logging evidence.Turns Juniper context into a concrete triage and containment workflow.
ESXi hardeningReview ESXi Shell, SSH, firewall exceptions, lockdown mode, VIBs, VMCI, and VMware Tools operations.Converts VMware source-pack artifacts into a repeatable control backlog.
Fortinet containmentReview Fortinet management appliance logs, scripts, file writes, and downstream ESXi/vCenter access.Prevents appliance response from stopping before follow-on virtualization checks.
12

Technical Appendix

Purpose

This appendix keeps the heavier UNC3886 material: source roles, deduped products and platforms, CVE boundaries, log paths, YARA names, sectors, regions, and exclusions. It preserves rigor without slowing down the main threat model.

Full 13-Source Role Map

Local source fileRoleDirect UNC3886 rowsPredicates presentUse in this model
2023-zero-day-trendscontext only0noneUse only for broad zero-day trend context and attribution caution.
2025-zero-day-reviewlimited direct CVE context1exploits:1Use for one actor-scoped exploit row and broader trend caveats.
china-nexus-espionage-targets-juniper-routersnetwork device tradecraft14uses:6, targets_product:1, targets_platform:1, exploits:2, targets_sector:1, abuses_service:1, distinct_from:2Primary Juniper/Junos/TACACS/TINYSHELL source and Salt Typhoon / Volt Typhoon distinction anchor.
chinese-espionage-tacticsactor capability context14uses:7, exploits:2, targets_sector:4, distinct_from:1Use for broader China-nexus tradecraft context while preserving actor-specific boundaries.
chinese-vmware-exploitation-since-2021VMware exploitation context4targets_platform:2, exploits:2Use for VMware/vCenter exploit timing and historical exposure review.
esxi-hypervisors-malware-persistencehypervisor persistence8uses:3, targets_platform:5Primary ESXi, vCenter, VMware Tools, VMCI, malicious VIB, and virtualized persistence source.
fortinet-malware-ecosystemFortinet tradecraft19uses:7, targets_product:3, targets_platform:3, exploits:1, targets_sector:5Primary FortiGate/FortiManager/FortiAnalyzer source and appliance-to-VMware pivot context.
investigating-ivanti-exploitation-persistencecontext only0noneUse for Ivanti and UNC5221 exclusion context; do not promote CVE-2025-0282 into UNC3886.
threats-to-defense-industrial-basesector context7targets_sector:7Use for Defense Industrial Base and sector scoping only, not technical path evidence.
uncovering-unc3886-espionage-operationsprimary operations36uses:15, targets_product:1, targets_platform:4, exploits:5, targets_sector:5, targets_region:5, abuses_service:1Primary source-pack spine for cross-platform actor behavior, tools, products, platforms, regions, and caveats.
vmware-detection-containment-hardeningdefensive companion5detected_by:5Use for log paths, containment, and hardening checks; not direct target attribution.
vmware-esxi-zero-day-bypassVMware zero-day tradecraft14uses:4, targets_platform:5, exploits:2, targets_sector:3Use for ESXi/vCenter platform exposure, VMware bypass tradecraft, and related actor-scoped rows.
zero-days-exploited-2022context only0noneUse only for historical zero-day trend context and over-promotion control.

Deduped Relationship Inventory

Relationship typeCountValuesBoundary
tools / malware19CASTLETAP; GHOSTTOWN; INTFS; LOOKOVER; MEDUSA; MOPSLED; Nmap; REPTILE; RIFLESPINE; SEAELF; TABLEFLIP; THINCRUST; TINYSHELL; VIRTUALGATE; VIRTUALPEER; VIRTUALPIE; VIRTUALPITA; VIRTUALSHINE; VIRTUALSPHEREDirect actor-scoped uses rows. These can drive hunts and family-specific evidence checks.
products4FortiAnalyzer; FortiGate; FortiManager; Juniper routersDirect target product rows. Use for asset inventory and owner assignment.
platforms6Junos OS; VMCI; VMware ESXi; VMware Tools; VMware vCenter; vSphereDirect platform rows. Use for management-plane and virtualization control checks.
services and detection paths6TACACS; /Windows/Temp/vmsvc.log; /tmp/vmsvc.log; /var/log; /var/log/hostd.log; /var/log/secureTACACS is direct abuse-service evidence; log paths are detection/hardening artifacts.
sectors8Defense Industrial Base; aerospace; defense; energy; government; technology; telecommunications; utilitiesTargeting context. Use for prioritization, not as technical tradecraft.
regions5Africa; Europe; North America; Oceania; Southeast AsiaTargeting context. Use for scoping and reporting, not as path evidence.
distinct-from context2Salt Typhoon; Volt TyphoonDistinction rows only. Do not treat as aliases or merged activity.

Selected Products, Platforms, and Artifacts

TypeValueUse
productJuniper routersRouter targeting and Junos OS forensic review.
platformJunos OSShell, Veriexec, process injection, and logging integrity.
productFortiGate / FortiManager / FortiAnalyzerFortinet appliance compromise and management-plane pivot review.
platformVMware ESXi / VMware vCenter / VMware Tools / vSphere / VMCIHypervisor persistence, Guest Operations, VMCI backdoors, and service-account controls.
serviceTACACSAuthentication review and credential-capture validation.

Selected Detection Artifacts

TypeValueSource layer
yara_ruleM_Hunting_TINYSHELL_5Juniper router context
yara_ruleM_Utility_GHOSTTOWN_1Juniper router context
yara_ruleM_APT_VIRTUALPITA_1VMware context
yara_ruleM_Hunting_Backdoor_CASTLETAP_1Fortinet context
log_path/var/log/hostd.logVMware hardening companion
log_path/tmp/vmsvc.logVMware hardening companion
log_path/Windows/Temp/vmsvc.logVMware hardening companion
log_path/var/log/secureVMware/Linux authentication review
log_path/var/logVMware/Linux and appliance log review root.

Context-Only Exclusions

Context valueStatusWhy it stays separate
Ivanti exploitation reportingcontext onlyThe local Ivanti source has zero direct UNC3886 relationship rows.
UNC5221excluded from UNC3886Use as separate actor context, not as an UNC3886 alias.
BRICKSTORMexcluded from direct toolingDo not add to the UNC3886 tools list from this local pack.
CVE-2025-0282excluded from direct exploit modelKeep with Ivanti / UNC5221 context unless a direct UNC3886 row exists.
broad zero-day trend rowscontext onlyUse for background and caveats; promote only when the relationship is explicitly scoped to UNC3886.