Skorik

Category: trojan · Aliases: Trojan:Win32/Skorik, Trojan.Win32.Skorik, Win32/Skorik · Sample count (EMBER 2018): 70 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2013Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Unauthorized Access & Payload Staging🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 8.1
Executive Summary
Skorik (cataloged in threat research and antivirus vendor databases under detections including Trojan:Win32/Skorik and Trojan.Win32.Skorik) is a Windows trojan and surveillance stager active since 2013.

Table of Contents

Overview

Skorik (cataloged in threat research and antivirus vendor databases under detections including Trojan:Win32/Skorik and Trojan.Win32.Skorik) is a Windows trojan and surveillance stager active since 2013. Designed to compromise host integrity and facilitate persistent unauthorized access, Skorik is typically distributed through malicious spam attachments, cracked software packages, and deceptive file-sharing networks. Upon execution, Skorik creates hidden binaries in the %AppData% directory, modifies Windows registry Run keys for automatic persistence, and injects malicious execution threads into legitimate system processes like explorer.exe. It establishes outbound command-and-control communication over HTTP/HTTPS, enabling remote operators to upload and download files, gather detailed operating system configurations, and deploy secondary malware payloads such as keyloggers and cryptocurrency miners.

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: Win32 Trojan Loader Architectures

Known Derivatives & Downstream Variants: Skorik.A · Skorik.B

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-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-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

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_SKORIK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Skorik"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "skorik" ascii wide nocase
        $s2 = "trojan:win32/skorik" ascii wide nocase
        $s3 = "trojan.win32.skorik" ascii wide nocase
        $s4 = "win32/skorik" 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 - Skorik (Trojan) Execution & Triage
id: b74e0831-690f-5627-9edf-2d7718d70d68
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Skorik 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/skorik
- 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.t1059_003
- attack.t1055
- attack.t1547_001
- attack.t1105
- attack.t1082
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_SKORIK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Skorik 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 = "skorik" 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. Instantly isolate the endpoint from the network to sever the attacker's interactive, remote-control session.
  2. Capture a full forensic memory image of the machine to extract the decrypted Skorik payload and its C2 configuration.
  3. Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Skorik persistence mechanisms.
  4. Assume total endpoint compromise; perform a clean OS rebuild and force password resets for all accounts that accessed the machine.

What to Avoid

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

  1. Do not leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or move laterally.
  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/Skorik?

Skorik is a Windows trojan that establishes autostart persistence, injects into processes, and downloads secondary payloads.

How does Skorik infect host endpoints?

Through malicious email attachments, torrent downloads, and deceptive software packages.

What persistence mechanisms are used by Skorik?

It drops hidden executables in %AppData% and registers registry Run keys to start automatically on login.

What malicious actions can remote operators execute via Skorik?

They can collect system telemetry, upload/download arbitrary files, and stage secondary malware.

How do administrators remove Skorik from an infected computer?

Isolate the machine, delete startup keys under CurrentVersion\Run, and run a complete offline antimalware scan.

How do I remove the Skorik Trojan from Windows?

Manual removal of Skorik 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 Skorik a virus or a Trojan?

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

What are the main symptoms of a Skorik infection?

Symptoms of Skorik 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 Skorik 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/skorik.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.