Sixer

Category: ransomware · Aliases: Ransom:Win32/Sixer, Trojan-Ransom.Win32.Sixer, Win32/Sixer, Sixer Ransomware, Ransom.Sixer · Sample count (EMBER 2018): 16 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactActor: Unknown / CybercriminalIndustry: Healthcare, Critical Infrastructure, EnterpriseMotivation: Financial Extortion🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Sixer (classified in cybersecurity threat databases under designations including Ransom:Win32/Sixer, Trojan-Ransom.Win32.Sixer, and Win32/Sixer) is an evasive crypto-ransomware family designed to execute targeted file encryption across Windows endpoints.

Table of Contents

Overview

Sixer (classified in cybersecurity threat databases under designations including Ransom:Win32/Sixer, Trojan-Ransom.Win32.Sixer, and Win32/Sixer) is an evasive crypto-ransomware family designed to execute targeted file encryption across Windows endpoints. Distributed primarily via malicious email attachments, Trojanized freeware archives, and compromised remote access credentials, Sixer incorporates pre-execution evasion checks. It interrogates the system environment for the presence of analysis debuggers (via IsDebuggerPresent and CheckRemoteDebuggerPresent) and active sandbox hooks before deploying its payload. Sixer scans all local fixed disks, removable media, and mapped network drives, identifying high-value files based on an extensive extension list covering documents, databases, spreadsheets, source code, and media archives. It locks targets using AES-256 encryption, appending .sixer to filenames and dropping ransom notes titled READ_SIXER_DECRYPT.txt. Sixer executes administrative shell commands to delete Volume Shadow Copies and disable startup repair.

Known aliases

Threat reports may refer to this family under multiple names:

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-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
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-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

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_SIXER_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sixer"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sixer" ascii wide nocase
        $s2 = "ransom:win32/sixer" ascii wide nocase
        $s3 = "trojan-ransom.win32.sixer" ascii wide nocase
        $s4 = "win32/sixer" ascii wide nocase
        $s5 = "sixer ransomware" ascii wide nocase
        $s6 = "ransom.sixer" 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 - Sixer (Ransomware) Execution & Triage
id: 5784b6f4-0164-5e44-9aef-c7ec67c83590
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sixer malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/sixer
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1490
- attack.t1497_001
- attack.t1083
- attack.t1135
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_SIXER_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sixer 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 = "sixer" 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 immediately to prevent Sixer from downloading and executing its secondary payloads (e.g., ransomware).
  2. Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Sixer persistence mechanisms.
  3. Review firewall and proxy logs to identify the C2 domains Sixer attempted to contact, and block them enterprise-wide.
  4. Capture a live memory image (RAM dump) to extract the injected Sixer modules and identify the secondary payloads.

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 Sixer 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 Ransom:Win32/Sixer?

Sixer is a crypto-ransomware family that encrypts user documents, databases, and media on Windows systems using AES-256.

How does Sixer identify files to encrypt?

It checks file extensions against a hardcoded list of productivity formats, databases, archives, and developer code files.

What evasion techniques does Sixer employ?

It calls debugger detection APIs and checks for virtualization artifacts to evade sandbox analysis environments.

How does Sixer prevent local data recovery?

It deletes Windows Volume Shadow Copies via vssadmin and disables automatic recovery using bcdedit commands.

What is the recommended recovery plan for Sixer victims?

Disconnect infected machines from the local network, preserve encrypted files for future decryptor availability, and restore from backups.

How do I remove the Sixer Ransomware from Windows?

Manual removal of Sixer 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 Sixer a virus or a Ransomware?

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

What are the main symptoms of a Sixer infection?

Symptoms of Sixer 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 Ransomwares

Want to prevent Sixer and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

📣 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/sixer.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.