Fosniw

Overview

Executive Summary

Propagation and Execution Lifecycle

• Network Share Exploitation: The primary propagation method for Fosniw involves aggressively scanning the local area network (LAN) for open Server Message Block (SMB) network shares. It attempts to brute-force weak administrator credentials or exploit unpatched SMB vulnerabilities to copy its executable to adjacent servers and workstations.
• System Modification and Hiding: Once resident on a new host, the worm copies itself to the Windows System directory and modifies the Registry (e.g., `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run`) to ensure it executes upon every reboot. It frequently alters system policies to disable Task Manager and Registry Editor to hinder manual removal.
• Trojan Functionality: After establishing persistence and continuing its lateral movement, Fosniw connects to a command-and-control (C2) server. It typically acts as a downloader, receiving instructions to pull down and execute secondary payloads, which range from cryptominers to destructive ransomware.

Threat Assessment

Eradication and Incident Response

• Immediate Network Segmentation: Do not just isolate the initially infected machine. Physically or logically segment the affected VLAN to halt the lateral spread of the worm via SMB.
• Credential Auditing: The worm's ability to spread implies weak or default passwords on network shares. Conduct an immediate audit of service accounts and administrative credentials, enforcing complex passwords.
• Enterprise-Wide Sweeps: Conduct a massive forensic sweep across all endpoints and network shares to identify the Fosniw executable, remove its persistence mechanisms, and ensure no secondary payloads were deployed prior to containment.

Known aliases

Threat reports may refer to this family under multiple names:

• Worm.Fosniw
• Trojan.Fosniw
• W32/Fosniw

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.
• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

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_FOSNIW_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Fosniw"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "fosniw" ascii wide nocase
        $s2 = "worm.fosniw" ascii wide nocase
        $s3 = "trojan.fosniw" ascii wide nocase
        $s4 = "w32/fosniw" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Fosniw (Ransomware) Execution & Triage
id: 91b71bc9-fb6f-5e6e-9611-e2c2d0636459
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Fosniw 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/fosniw
- 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.t1091
- attack.t1547_001
- attack.t1059
- attack.t1105
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

rule MALWARE_WIN_FOSNIW_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fosniw 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 = "fosniw" 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. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Fosniw from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Fosniw symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Fosniw to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Fosniw binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Fosniw.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Fosniw eradication is completely verified.

References & External Analysis

• Search "fosniw" on VirusTotal (External Analysis)
• Search "fosniw" on Any.Run (Sandbox Sandbox)
• Search "fosniw" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Jo0Br8Hglsii
• Sisbot
• Fayu
• Omyaamfbexii
• Gpukj
• Plugs
• Hoax
• Pintu

Machine-readable

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