Flystudio

Overview

FlyStudio (identified across enterprise antivirus detection signatures as Packer:Win32/FlyStudio, Trojan:Win32/FlyStudio, and Trojan.MalPack.FlyStudio) is a widely abused software packer and runtime environment analyzed by Microsoft Defender and Malwarebytes. Originally developed as a modular Chinese application development IDE, FlyStudio's compiled runtime wrappers and executable packing structures were heavily weaponized by cybercrime syndicates and underground malware authors to obfuscate secondary malicious binaries. FlyStudio packs underlying malicious payloads—including remote access trojans (RATs), keyloggers, and DDoS bots—into complex multi-layer runtime envelopes. Upon launch on an endpoint, the FlyStudio stub unpacks malicious DLLs and shellcode dynamically in memory, bypassing static signature-based detection mechanisms and antivirus heuristics. It establishes persistence by writing auto-start registry run entries under HKCU\Software\Microsoft\Windows\CurrentVersion\Run and dropping runtime helper dependencies in %AppData% or %Temp%.

Known aliases

Threat reports may refer to this family under multiple names:

• Packer:Win32/FlyStudio
• Trojan:Win32/FlyStudio
• Trojan.MalPack.FlyStudio
• Win32/FlyStudio.Packer
• FlyStudio.Runtime

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Chinese_Visual_Ide_Runtime

Known Derivatives & Downstream Variants: Flystudio.Packer · Malpack.Flystudio

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• a9b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0c9d8e7f6a5b4c3d2e1f0a9b8
• b8c7d6e5f4a3b2c1d0e9f8a7b6c5d4e3f2a1b0c9d8e7f6a5b4c3d2e1f0a9b8c7

Delivery vectors

• Underground gaming modification forums and cracked software repositories
• Trojanized utility downloads containing FlyStudio-packed stagers

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\FlyStudioStub
• Runtime helper dropped in %AppData%\FlyStudio\fsrun.dll

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_FLYSTUDIO_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Flystudio"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "flystudio" ascii wide nocase
        $s2 = "packer:win32/flystudio" ascii wide nocase
        $s3 = "trojan:win32/flystudio" ascii wide nocase
        $s4 = "trojan.malpack.flystudio" ascii wide nocase
        $s5 = "win32/flystudio.packer" ascii wide nocase
        $s6 = "flystudio.runtime" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Flystudio (Packer) Execution & Triage
id: bbf55c7c-8224-5c1f-8d70-d38463500a4b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Flystudio malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/flystudio
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.packer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1027_002
- attack.t1140
- attack.t1055_001
- attack.t1547_001
- attack.t1112
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_FLYSTUDIO_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Flystudio tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "flystudio" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Terminate active processes matching suspicious FlyStudio runtime headers and unmapped memory sections.
2. Purge unpacked DLLs and staging binaries from %Temp% and %AppData% directories.
3. Remove unauthorized auto-run entries under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
4. Conduct an enterprise-wide EDR memory scan to detect injected remote access trojans.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not rely solely on static SHA256 hashes; FlyStudio mutates binary stubs across different compile instances.
2. Avoid allowing users to execute software packaged in non-standard third-party application frameworks.

References & External Analysis

• Microsoft Defender Threat Encyclopedia - Packer:Win32/FlyStudio Analysis
• Malwarebytes Labs Threat Intelligence - Trojan.MalPack.FlyStudio
• NIST National Vulnerability Database - CVE-2015-1641
• Search "flystudio" on VirusTotal (External Analysis)
• Search "flystudio" on Any.Run (Sandbox Sandbox)
• Search "flystudio" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Packer)

Explore other documented threats in the same operational category:

• Packy
• Enigmaprotector
• Noobyprotect
• Genkryptik
• Obsidium
• Packedent
• Autoit
• Vbkryjetor

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/flystudio.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.