{
  "family": "indigorose",
  "sample_count": 1,
  "category": "trojan",
  "description": "<h3>Executive Summary</h3>\n\"IndigoRose\" refers to detections associated with AutoPlay Media Studio (and related products) developed by Indigo Rose Software. This is a legitimate, commercial rapid application development (RAD) tool used by software developers to create custom multimedia presentations, autorun menus for CD/DVDs, and software installers. However, because the tool allows for the easy compilation of executables that can silently launch embedded files and scripts, it is frequently abused by malware authors to bundle and distribute Trojans, making compiled IndigoRose executables highly suspect in enterprise environments.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nThe IndigoRose software itself is not malware. The threat arises when a threat actor uses the tool to compile a malicious package. This package is then distributed via phishing emails or fake software downloads.\n\nWhen a maliciously crafted IndigoRose executable is run:\n<ul>\n<li><strong>File Extraction and Execution:</strong> The compiled executable acts as a sophisticated \"dropper\" or binder. It silently extracts embedded files (the actual malware payload, such as a RAT or info-stealer) to temporary directories (e.g., `%TEMP%`).</li>\n<li><strong>Scripted Automation:</strong> The attacker utilizes the legitimate scripting capabilities of AutoPlay Media Studio (Lua-based) to automate the execution of the extracted malware, modify registry keys, or even disable specific security services before the payload runs.</li>\n<li><strong>Evasion by Association:</strong> Because the outer executable is compiled by a legitimate commercial tool, it often bypasses simplistic antivirus heuristics that are looking for standard malware packing techniques (like UPX).</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThe presence of an unverified executable compiled with IndigoRose is a significant security concern (Riskware). If the executable was not explicitly created by the internal IT team for administrative purposes, it must be assumed to be a malicious wrapper designed to bypass initial defenses and deploy a hidden payload.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Do Not Execute:</strong> If a suspicious IndigoRose executable (often disguised as a document or a \"Setup.exe\") is discovered, do not run it. Isolate the file immediately.</li>\n<li><strong>Forensic Unpacking:</strong> Security analysts must use specialized tools to unpack the IndigoRose container and analyze the embedded files and the internal Lua scripts to determine the true nature of the payload.</li>\n<li><strong>Network Isolation:</strong> If the file was inadvertently executed, immediately isolate the endpoint and perform a deep forensic scan to locate and eradicate the extracted secondary malware.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Riskware.IndigoRose",
    "Dropper.AutoPlay",
    "Win32/AutoPlay.Suspicious"
  ],
  "enrichment_level": "insufficient_information",
  "faq": [],
  "faq_count": 0,
  "mitre_attack": [
    "T1204.002",
    "T1027"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-07-02T07:08:57Z",
  "type": "Riskware / Dropper (Abused Tool)",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ]
}