Fsysna

Category: trojan · Aliases: Fsysna, Trojan:Win32/Fsysna, Trojan.Win32.Fsysna, Win32/Fsysna, Trojan.Win32.FSYSNA, Fsysna Loader, Trojan:Win32/Fsysna.gen · Sample count (EMBER 2018): 427 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2015Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Trojan:Win32/Fsysna (documented across vendor telemetry as Trojan.Win32.Fsysna, Win32/Fsysna, or Trojan.Win32.FSYSNA) is a sophisticated multi-stage trojan loader, backdoor, and enterprise lateral movement tool analyzed extensively by NHS Digital and cybersecurity agencies.

Table of Contents

Overview

Trojan:Win32/Fsysna (documented across vendor telemetry as Trojan.Win32.Fsysna, Win32/Fsysna, or Trojan.Win32.FSYSNA) is a sophisticated multi-stage trojan loader, backdoor, and enterprise lateral movement tool analyzed extensively by NHS Digital and cybersecurity agencies. Used by cybercriminal syndicates to stage high-impact attacks against enterprise and healthcare infrastructures, Fsysna is engineered for stealth and persistence. Upon initial infection—frequently initiated through spear-phishing or compromised VPN/RDP credentials—Fsysna terminates competing malware and diagnostic processes using taskkill and WMI commands. It establishes persistent scheduled tasks, maps local subnets for lateral propagation via SMB, and communicates with remote C2 servers over encrypted protocols to deliver enterprise ransomware, banking stealers, or cryptominers.

Known aliases

Threat reports may refer to this family under multiple names:

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: Enterprise Loader And Lateral Movement Lineage

Known Derivatives & Downstream Variants: Trojan:Win32/Fsysna.Gen · Trojan.Win32.Fsysna.Fypf · Trojan.Win32.Fsysna.Ai

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-EDAExecutable Deobfuscation AnalysisDetectT1027.002Deploy static entropy scanners and dynamic memory-unpacking heuristics to identify obfuscated and packed PE structures.
D3-STMScheduled Task Creation AnalysisDetectT1053.005Audit task creation targeting system and hidden service directories; verify task author credentials.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RBIRemote Browser IsolationIsolateT1189Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints.

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

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

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Fsysna (Trojan) Execution & Triage
id: 69a527a1-e3f7-5cf6-955f-f4caf318bfca
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Fsysna 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/fsysna
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1105
- attack.t1021_002
- attack.t1562_001
- attack.t1059_003
- attack.t1547_001
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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_FSYSNA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fsysna 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 = "fsysna" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Isolate the endpoint from the network immediately to prevent Fsysna from successfully downloading and executing its secondary payloads.
  2. Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Fsysna persistence mechanisms.
  3. Review firewall and proxy logs to identify the C2 domains Fsysna attempted to contact, and block them enterprise-wide.
  4. Perform a full memory and disk scan with a reputable EDR solution to eradicate the dropped executables and injected processes.

What to Avoid

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

  1. Do not close an incident simply because the initial Fsysna dropper was quarantined; always verify if secondary payloads were downloaded.
  2. Avoid relying solely on manual file deletion, as the injected processes will likely just recreate the dropped binaries.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Fsysna?

Fsysna is an enterprise Trojan loader and backdoor used to deploy secondary payloads like ransomware and facilitate lateral network movement.

Why is Fsysna significant in enterprise environments?

Fsysna scans local networks for accessible SMB shares, harvests credentials, and terminates security software to deploy major ransomware.

How does Fsysna evade endpoint detection?

Fsysna uses process hollowing, terminates diagnostic processes via WMI, and uses encrypted C2 channels to blend with normal traffic.

What agencies have published advisories on Fsysna?

NHS Digital, Microsoft Defender, and Kaspersky have published technical advisories documenting Fsysna indicators and attack lifecycle.

How can organizations defend against Fsysna attacks?

Enforce network segmentation on SMB ports, mandate multi-factor authentication (MFA) on remote access, and deploy managed endpoint detection (EDR).

How do I remove Fsysna from Windows?

Manual removal of Fsysna is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

What are the main symptoms of a Fsysna infection?

Symptoms of Fsysna can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Trojans

Want to prevent Fsysna and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/fsysna.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.