Sality

Overview

Sality is one of the most durable, resilient, and historically significant polymorphic file infectors and botnets in cybersecurity history. First identified around 2003 in Russia, Sality evolved over two decades from a rudimentary PE file virus into an advanced, decentralized cybercrime utility used for distributed cryptocurrency mining, credential theft, spam proxying, and malware-as-a-service distribution. Sality's extraordinary longevity stems from its polymorphic engine: every newly infected executable (.exe, .scr) is rewritten with unique junk code, register renaming, and randomized entry point obfuscation (EPO) to defeat static antivirus signatures. In 2011, Sality underwent a major architectural leap by abandoning centralized C2 servers in favor of a completely decentralized peer-to-peer (P2P) network communicating over UDP. Sality nodes exchange encrypted peer lists and cryptographically signed command packages directly with other infected endpoints, rendering traditional domain takedowns and sinkholes completely ineffective.

Known aliases

Threat reports may refer to this family under multiple names:

• Sality
• win32.sality
• sality.ae
• sality.gen
• kuku
• sality_p2p

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

• Eastern European Cybercrime Developers (Sality Syndicate) High confidence
  Basis: Active continuously since 2003 as a modular polymorphic infector and malware distribution botnet. Transitioned in 2011 to an advanced peer-to-peer (P2P) UDP mesh protocol that proved resilient against multiple industry-wide sinkholing attempts. [source]

Family Pedigree & Lineage

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

Known Derivatives & Downstream Variants: Sality.Ae · Sality.Og · Sality_P2P

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):

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

• CVE-2010-2568 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

Network detection ideas

• Detect anomalous high-frequency outbound UDP traffic on non-standard ports from individual desktop endpoints
• Alert on DNS queries to public IP reflector services used by Sality nodes to determine external NAT status
• Monitor local disk write activity for bulk modification of .exe and .scr files across network shares

Sources: CISA Advisory AA20-302A, Symantec Sality P2P Threat Analysis

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.

• 0f6222bfa8952467d027e8529348d6132646d5ee3269b2d887349176ca0cf508
• c687e35b7193dc58f7004f2c918ef929c5cbe83e4a9e25d2c2084c8a82cf61a2

Delivery vectors

• Removable USB storage devices spreading via autorun.inf and .lnk exploits
• Network share crawling infecting accessible executable binaries

Persistence mechanisms

• System driver hook installing a kernel-mode rootkit component
• Registry Run and SafeBoot keys modified to disable security services

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_SALITY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sality"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sality" ascii wide nocase
        $s2 = "sality" ascii wide nocase
        $s3 = "win32.sality" ascii wide nocase
        $s4 = "sality.ae" ascii wide nocase
        $s5 = "sality.gen" ascii wide nocase
        $s6 = "kuku" ascii wide nocase
        $s7 = "sality_p2p" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Sality (File Infector) Execution & Triage
id: d4c9af91-ef9c-5b22-9e0b-76fd4a2333de
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sality 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/sality
- 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.file-infector
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1027_001
- attack.t1562_001
- attack.t1055
- attack.t1090_001
- 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

rule MALWARE_WIN_SALITY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sality 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 = "sality" 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. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Sality from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Sality into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Sality persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Sality execution timeframe.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Sality dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Sality until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Malpedia (Fraunhofer FKIE): Sality (win.sality)
• CISA Advisory: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities)
• Search "sality" on VirusTotal (External Analysis)
• Search "sality" on Any.Run (Sandbox Sandbox)
• Search "sality" on MalwareBazaar (Malware Samples)

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities) ↗

Frequently Asked Questions

Related Threats (Category: File Infector)

Explore other documented threats in the same operational category:

• Pioneer
• Neshta
• Xpaj
• Virut
• Coma
• Aliser
• Jeefo
• Sivis

Machine-readable

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