{
  "family": "cryptredol",
  "sample_count": 1,
  "category": "ransomware",
  "description": "Ransomware:Win32/Cryptredol is a destructive malware strain with a dual-impact payload: it functions primarily as ransomware, encrypting victim data (`T1486`), but often includes a secondary cryptomining component (`T1496`) designed to monetize the system's hardware resources while the victim decides whether to pay the ransom. This dual-pronged attack maximizes the attacker's return on investment.<br><br><b>Understanding Cryptredol (Ransom-Miner)</b><br>To an end-user, the infection is catastrophic. Files become inaccessible, appended with a random extension, and the computer's fans spin loudly as the hidden miner consumes all available CPU power. For an organization, it requires immediate network isolation to prevent the rapid lateral spread of the encryption routine.<br><br><b>Execution and Dual-Payload Mechanics</b><br>Cryptredol is typically delivered via exploit kits or weaponized RDP access. Upon execution, it first disables Volume Shadow Copies (`vssadmin.exe delete shadows`) (`T1490`) to prevent easy data recovery. It then drops a secondary payload (often a variant of XMRig) to begin mining Monero (`T1496`) in the background. Simultaneously, it rapidly traverses local drives and mapped network shares, utilizing strong algorithms like AES or RSA to encrypt files (`T1486`). A ransom note is dropped in every affected directory.<br><br><b>Indicators of Compromise & Impact</b><br>The impact is total loss of data availability combined with severe system resource degradation. Host-based IoCs include the sudden renaming of thousands of files, the presence of ransom notes, EDR alerts for rapid file modification operations, and persistent 100% CPU utilization by unknown processes. System logs will show the execution of commands designed to inhibit system recovery. Network IoCs include connections to cryptocurrency mining pools (Stratum protocol) and a brief burst of traffic to a C2 server to transmit the victim's unique encryption ID.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1496",
    "T1012",
    "T1486",
    "T1490"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1486",
      "name": "Data Encrypted for Impact (The core ransomware function)",
      "tactic": "Impact"
    },
    {
      "id": "T1496",
      "name": "Resource Hijacking (The secondary cryptomining function)",
      "tactic": "Impact"
    },
    {
      "id": "T1490",
      "name": "Inhibit System Recovery (Deleting Shadow Copies)",
      "tactic": "Impact"
    },
    {
      "id": "T1012",
      "name": "Query Registry (Identifying mounted drives and network shares to encrypt)",
      "tactic": "Discovery"
    }
  ],
  "containment_steps": [
    "Isolate the infected machine from the network immediately—pull the ethernet cable or disable the Wi-Fi adapter to stop the encryption from spreading to network shares.",
    "Do not immediately reboot the machine; if the encryption process is active, rebooting may finalize the damage or destroy volatile memory keys.",
    "Identify the initial infection vector (e.g., exposed RDP) to prevent further compromise.",
    "Restore operations from known-good, offline backups; paying the ransom is highly discouraged as it funds criminal enterprises."
  ],
  "what_to_avoid": [
    "Do not connect backup drives to the infected machine until it has been completely wiped and reimaged, as the ransomware will encrypt the backups.",
    "Avoid assuming the threat is just a miner based on CPU usage; always check for encrypted files and dropped ransom notes."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}