MEDIUMmalware·

SANSAR Linux Cryptomining Malware Uses Modified NVIDIA Library for Evasion

The REF3364 threat cluster is deploying SANSAR, a Rust-based Linux cryptomining toolkit, which utilizes the TOR network for command and control. A notable evasion technique involves modifying NVIDIA libraries to conceal high GPU resource consumption from detection tools. This activity is financially motivated, focusing on resource hijacking.

This report was researched and drafted by an AI agent and reviewed by a human analyst prior to publication. View the agent workflow →
Indicators of Compromise(1)
↓ Download STIX
Domainefxisnqldelyr5ra25oqfrsut54b34g26e7zrsiuupsoekjof2gho2id.onion

Overview

REF3364 is a financially motivated threat cluster operating a Linux-focused cryptocurrency mining campaign. Their primary tool, SANSAR, is a Rust-based orchestrator designed to manage CPU and GPU miners. A key evasion tactic employed by SANSAR involves tampering with NVIDIA libraries to obscure the true GPU workload, making detection more challenging for system administrators and security tools.

Technical Analysis

SANSAR functions as a Rust-based orchestrator, receiving commands and managing mining operations via the TOR anonymity network. It is designed to deploy and control both CPU and GPU miners on compromised Linux systems. The most distinctive technical aspect is its defense evasion capability: SANSAR modifies specific NVIDIA libraries. This modification is intended to manipulate system readings, thereby hiding the high GPU utilization that is characteristic of cryptocurrency mining activities. This makes it harder for standard monitoring tools to detect the resource hijacking.

Detection

  • Unusual Outbound Network Connections: Monitor for processes initiating connections to the TOR network, especially from non-standard user accounts or services.
  • Sustained High CPU Usage: While GPU activity is masked, sustained high CPU usage by unknown or suspicious processes can still indicate cryptomining activity.
  • Modified System Libraries: Hunt for unauthorized modifications to system libraries, particularly those related to NVIDIA drivers or graphics processing, in unexpected directories or with unusual timestamps.
  • Process Monitoring: Look for unusual processes running with high resource consumption, especially those without clear legitimate purposes or signed binaries.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Linux – Suspicious Outbound TOR Connection

title: Linux - Suspicious Outbound TOR Connection
id: 90e1f3b2-c5d0-4e3a-b8f4-6f9d2a1c2e3f
status: experimental
description: Detects processes making outbound connections to common TOR ports or known TOR network patterns. This could indicate C2 communication for SANSAR or other malware.
logsource:
  product: linux
  service: network_connections
detection:
  selection:
    dst_port:
      - 9001 # Common TOR relay port
      - 9030 # Common TOR relay port
      - 9050 # Common TOR SOCKS port
      - 9150 # Common TOR Browser SOCKS port
  condition: selection
level: high

Linux – Sustained High CPU Usage by Unusual Process

title: Linux - Sustained High CPU Usage by Unusual Process
id: 7a1b2c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects processes consuming a high percentage of CPU over a sustained period, which is indicative of cryptomining activity. While SANSAR hides GPU usage, CPU mining or other CPU-intensive tasks may still be visible.
logsource:
  product: linux
  service: process_monitoring
detection:
  selection:
    cpu_usage|gte: 80 # Adjust threshold as needed for environment
    process_name|exclude:
      - 'systemd'
      - 'kernel'
      - 'kworker'
      - 'Xorg'
      - 'gnome-shell'
      - 'firefox'
      - 'chrome'
      - 'java'
      - 'docker'
      - 'containerd'
      - 'kubelet'
  timeframe: 5m # Sustained for 5 minutes
  condition: selection
level: medium

Mitigations

  1. Regular Patching and Updates: Ensure all Linux systems and installed software are kept up-to-date with the latest security patches to prevent initial compromise.
  2. Strong Access Controls: Implement least privilege principles for user accounts and services. Restrict network access to only necessary ports and protocols.
  3. Network Segmentation: Segment networks to limit lateral movement and C2 communication if a system is compromised.
  4. Endpoint Detection and Response (EDR): Deploy EDR solutions capable of monitoring process activity, file integrity, and network connections for anomalous behavior.
  5. Audit Log Review: Regularly review system and application logs for signs of compromise, such as unusual commands, failed logins, or unauthorized file modifications.

References

  • https://thehackernews.com/2026/11/sansar-linux-cryptomining-malware-uses.html

Indicators of Compromise

Type Value Description
Domain efxisnqldelyr5ra25oqfrsut54b34g26e7zrsiuupsoekjof2gho2id.onion TOR C2 onion service address (via https://thehackernews.com/2026/11/sansar-linux-cryptomining-malware-uses.html)

MITRE ATT&CK

  • T1496 — Resource Hijacking
  • T1090.003 — Multi-hop Proxy
  • T1036.005 — Match Legitimate Resource Name or Location
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,535 input / 1,258 output tokens ·
Reviewed and approved by a human analyst before publication
#malware#cryptomining#defense-evasion#linux#medium#ransomware#rust#tor