Sysn

Category: trojan · Aliases: Trojan:Win32/Sysn, Trojan.Win32.Sysn, Trojan.Win32.Sysna, Swisyn, Win32/Sysn · Sample count (EMBER 2018): 99 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Persistence, Defense EvasionFirst seen: 2011Actor: Unknown / CybercriminalIndustry: Global / Opportunistic, Enterprise Workstations, Financial InstitutionsMotivation: Payload Delivery🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Sysn (cataloged across security intelligence as Trojan:Win32/Sysn, Trojan.Win32.Sysna, and Swisyn) is a resilient family of Delphi-based Windows trojans and payload loaders active since 2011.

Table of Contents

Overview

Sysn (cataloged across security intelligence as Trojan:Win32/Sysn, Trojan.Win32.Sysna, and Swisyn) is a resilient family of Delphi-based Windows trojans and payload loaders active since 2011. Characterized by aggressive defense evasion and system modification capabilities, Sysn is distributed via weaponized spearphishing attachments, trojanized key generators, and drive-by web exploit kits. Upon execution on a compromised endpoint, Sysn deploys dynamic API hashing and multi-layered binary packing to evade static signature detection. It systematically impairs host security controls: modifying the Windows Registry to disable the Windows Firewall (DisableFirewall), terminating security monitoring services, and altering the local HOSTS file (C:\Windows\System32\drivers\etc\hosts) to redirect antivirus update domains and security vendor websites to loopback (127.0.0.1). Sysn establishes persistence by installing a rogue Windows Service (T1543.003) or modifying Registry Run keys, subsequently initiating encrypted HTTP beaconing to command-and-control servers to download and execute secondary malware payloads including information stealers and banking trojans.

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: Delphi Trojan Dropper Families

Known Derivatives & Downstream Variants: Sysn.A · Sysna.B · Swisyn Loader

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-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.

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_SYSN_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sysn"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sysn" ascii wide nocase
        $s2 = "trojan:win32/sysn" ascii wide nocase
        $s3 = "trojan.win32.sysn" ascii wide nocase
        $s4 = "trojan.win32.sysna" ascii wide nocase
        $s5 = "swisyn" ascii wide nocase
        $s6 = "win32/sysn" 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 - Sysn (Trojan) Execution & Triage
id: e5d43bb9-a9df-5fcf-af7b-b8bcef3247d9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sysn 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/sysn
- 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.t1543_003
- attack.t1562_001
- attack.t1112
- attack.t1562_004
- 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_SYSN_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sysn 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 = "sysn" 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. Immediately isolate the compromised endpoint from the network to halt C2 communications and secondary malware downloads.
  2. Audit the Windows HOSTS file (C:\Windows\System32\drivers\etc\hosts) and remove malicious entries blocking security vendor domains.
  3. Re-enable and reset Windows Firewall policies using 'netsh advfirewall reset' to restore network boundary defenses.
  4. Audit Windows Services using 'sc.exe' and Registry Run keys to identify and delete rogue Sysn service registrations.

What to Avoid

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

  1. Do not trust local endpoint security alerts during triage, as Sysn is specifically designed to tamper with native security logging.
  2. Avoid relying solely on automated file deletion without inspecting the modified system services and firewall configurations.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Sysn?

Sysn is a Delphi-based Windows trojan and loader that disables firewalls, modifies HOSTS files, and downloads secondary malware.

How does Sysn impair host defensive tools?

It modifies registry policies to disable Windows Firewall and alters the local HOSTS file to block security vendor update servers.

What distribution vectors are used by Sysn?

It is distributed through weaponized email attachments, software cracks, keygens, and exploit kit landing pages.

How does Sysn establish persistence across reboots?

It installs rogue background Windows Services and creates autostart entries under CurrentVersion\Run.

What remediation steps should be taken for a Sysn compromise?

Isolate the endpoint, restore the Windows HOSTS file, reset firewall policies, and run full offline antimalware remediation.

How do I remove the Sysn Trojan from Windows?

Manual removal of Sysn 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.

Is Sysn a virus or a Trojan?

Sysn is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Sysn typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Sysn infection?

Symptoms of Sysn 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 Sysn 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 Threat Intelligence Team.

Machine-readable

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