Sivis

Category: file_infector · Aliases: Sivis, Win32.Sivis, Virus.Win32.Sivis, W32/Sivis · Sample count (EMBER 2018): 7,180 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: File_InfectorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2006Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Opportunistic🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Sivis (known across antivirus vendors as Win32.Sivis or W32/Sivis) is a classic Windows PE file infector that first surfaced around 2006.

Table of Contents

Overview

Sivis (known across antivirus vendors as Win32.Sivis or W32/Sivis) is a classic Windows PE file infector that first surfaced around 2006. Engineered during the peak era of Windows XP network worms, Sivis systematically searches all local fixed disks, mounted network volumes, and removable storage media for 32-bit executable files (.exe), modifying their header structures to prepend or append malicious viral code. Upon initial execution, Sivis attempts to neutralize defensive software: it terminates active antivirus and firewall processes, deletes security registry keys, and alters system policies to disable Windows Task Manager (DisableTaskMgr) and Registry Editor (DisableRegistryTools) to prevent administrative remediation. The virus establishes network connections to remote HTTP servers to download rogue software packages and adware while actively scanning internal networks to infect shared executable directories.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

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

→ Explore all Threat Actor & APT Campaign Profiles

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: Sivis.A · Sivis.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

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-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-RMCRemovable Media Access ControlHardenT1091Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media.
D3-SCASystem Call AnalysisDetectT1106Leverage kernel-mode EDR sensors to detect unhooked direct system calls (Syscalls) designed to circumvent user-mode API monitoring.
D3-WORMImmutable Backup StorageHardenT1485Store primary backups in Write-Once-Read-Many (WORM) cloud repositories protected by multi-party out-of-band credentials.

Exploited Vulnerabilities (CVEs)

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

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.

ProtocolsHTTP, TCP
Observed ports80, 8080
Infrastructure modelSimple C2 servers receiving victim IP beacons and serving secondary adware or rogue antivirus installers.
Encryption / encodingSimple XOR obfuscation and plaintext URL strings.
Traffic fingerprintHTTP GET requests requesting remote configuration files or executable drops disguised as media files.
Identifiable from traffic aloneMedium

Network detection ideas

Sources: CISA Advisory AA20-302A, Malpedia Sivis

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_SIVIS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sivis"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sivis" ascii wide nocase
        $s2 = "sivis" ascii wide nocase
        $s3 = "win32.sivis" ascii wide nocase
        $s4 = "virus.win32.sivis" ascii wide nocase
        $s5 = "w32/sivis" 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 - Sivis (File Infector) Execution & Triage
id: a3ab2d5c-8e05-5dbb-9fd4-ee664c7822aa
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sivis 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/sivis
- 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.t1055
- attack.t1106
- attack.t1091
- attack.t1485
- attack.t1140
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_SIVIS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sivis 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 = "sivis" 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 sever the endpoint from the network; Sivis will aggressively hunt for and infect executables on shared corporate network drives.
  2. Assume all <code>.exe</code> and <code>.scr</code> files on the host are compromised and potentially corrupted beyond repair.
  3. Do not attempt to 'clean' the files using standard AV, as this frequently destroys the legitimate application data appended to the virus.
  4. Perform a complete bare-metal rebuild of the operating system and restore applications from known-clean, read-only installation media.

What to Avoid

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

  1. Avoid backing up executable files from the infected machine; you will only be backing up the polymorphic viral payloads.
  2. Do not execute any diagnostic tools directly from the infected host, as they will likely become infected upon execution.

References & External Analysis

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

What is Sivis malware?

Sivis is a classic Windows PE file infector from 2006 that prepends malicious code to clean executables and disables administrative utilities like Task Manager.

How does Sivis prevent victims from removing it?

Sivis modifies registry policies to disable Task Manager (DisableTaskMgr) and Registry Editor (DisableRegistryTools), preventing users from seeing or stopping the malicious processes.

How does Sivis propagate?

Sivis infects all executable files (.exe) on local drives, connected USB flash drives, and unauthenticated network shares.

Can files infected by Sivis be repaired?

Antivirus cleaning utilities can sometimes strip the prepended viral code and restore the original entry point, though re-imaging is recommended for mission-critical systems.

How can modern defenders prevent Sivis infections?

Defenders should enforce Application Whitelisting (AppLocker/WDAC), restrict write access to shared folders, and block execution from external storage media.

How do I remove the Sivis File_Infector from Windows?

Manual removal of Sivis 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 Sivis a virus or a File_Infector?

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

What are the main symptoms of a Sivis infection?

Symptoms of Sivis 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 File_Infectors

Want to prevent Sivis and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

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