Join our Newsletter — 33% off our NHI Course

Could APT36’s Windows-Linux persistence endure cleanup?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: APT36-style campaigns are built for quiet, durable access across Windows and Linux targets in Indian government and defense environments, according to Aryaka. Endpoint alerts alone will miss footholds that survive reboot and cleanup, so teams need correlated visibility across processes, services and network sessions.

Editorial analysis by NHI Mgmt Group, based on content published by Aryaka: “Espionage Without Noise: Understanding APT36’s Enduring Campaigns”.

Key questions

Q: Why do living-off-the-land techniques make long-term access harder to remove?

A: Because they blend malicious activity into trusted operating system behaviour.

Q: What signs show that persistence is working across multiple platforms?

A: Look for repeated reappearance of the same access pattern after reboot, cleanup or account changes, especially when Windows and Linux telemetry show similar tasking behaviour.

Q: What is the first control gap that espionage ecosystems usually exploit?

A: They exploit the gap between initial delivery and durable persistence.

Practitioner guidance

  • Deploy process-lineage monitoring for native utilities Instrument mshta.exe, script hosts and deserialisation-related execution paths so phishing-delivered payloads are visible even when no malicious file persists on disk.
  • Hunt for cross-platform persistence artefacts Build detections for startup folders, scheduled tasks and systemd user services that can preserve access after reboot or cleanup.
  • Correlate endpoint and network telemetry Tie process creation, service installation and outbound WebSocket sessions together so covert command-and-control cannot hide behind normal protocol use.

Bottom line: This campaign pattern shows that espionage actors are optimising for quiet, durable access rather than immediate disruption.

Glossary terms: Living Off The Land Technique, Systemd Persistence, Command And Control Channel, Memory-Resident Execution

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Espionage ecosystems are a governance problem, not just a malware problem. The article describes a cluster of operators that adapt tools, delivery methods and persistence across platforms while keeping the same strategic objective. That means security teams are dealing with a sustained access model, not a one-off intrusion. Detection, containment and identity governance all need to assume that the adversary is optimising for endurance, not speed.

A few things that frame the scale:

  • 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: How should security teams balance endpoint detection with network visibility against espionage campaigns?

A: Use both, but do not let either one become the sole source of truth. Endpoint telemetry exposes process ancestry, service creation and memory execution, while network telemetry reveals tasking, heartbeat traffic and structured exfiltration. Together they show whether an implant is merely present or actively being operated.

👉 Read our full editorial: Espionage ecosystems are refining persistence across Windows and Linux


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.