Fspm
Table of Contents
Overview
Executive Summary
Fspm is a classification typically applied to a HackTool or localized exploit script designed to bypass security controls or facilitate unauthorized access, often specifically targeting misconfigurations or vulnerabilities in file sharing protocols or specific enterprise software suites. The presence of an Fspm tool indicates a targeted attempt by an attacker (or an unauthorized insider) to map, exploit, or extract data from network resources.Infection Vector and Technical Capabilities
Fspm tools are generally not self-spreading malware. They are explicitly downloaded and executed by an attacker who has already gained initial access to a network (e.g., via a compromised VPN or RDP session) and is attempting to move laterally or locate sensitive data. Capabilities vary based on the specific variant, but generally focus on network exploitation:- Protocol Scanning and Exploitation: The tool may rapidly scan the local subnet for specific open ports (like SMB/445 or FTP/21) and attempt to exploit known vulnerabilities or misconfigurations (such as anonymous access or weak default credentials).
- Share Enumeration: Fspm tools often automate the process of mapping hidden or administrative network shares (e.g., `C$`, `ADMIN$`), allowing the attacker to locate file servers, backup repositories, or user directories that should be restricted.
- Brute-Forcing: Some variants include localized brute-forcing capabilities, attempting a rapid dictionary attack against identified services using a hardcoded list of common corporate passwords.
Threat Assessment
The detection of an Fspm tool is a critical security event indicating active, post-compromise lateral movement and reconnaissance. The attacker is actively mapping the internal network topology and attempting to identify targets for data exfiltration or ransomware deployment.Incident Response and Remediation
- Immediate Endpoint Isolation: The endpoint where the Fspm tool was executed must be isolated from the network immediately to halt the active reconnaissance and prevent further lateral movement.
- Hunt for Lateral Movement (Network Logs): Security analysts must review internal firewall logs, Windows Event Logs (specifically Event ID 4624 - Successful Logon), and EDR telemetry to trace the network connections initiated by the tool. Identify any internal servers or shares the attacker successfully accessed.
- Re-imaging and Credential Audit: The compromised machine must be wiped and re-imaged from a known-good baseline. A comprehensive audit of network share permissions and service account credentials is required to remediate the vulnerabilities the tool was attempting to exploit.
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:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1046 | Network Service Discovery | discovery | ATT&CK ↗ |
T1135 | Network Share Discovery | Discovery | ATT&CK ↗ |
T1110.001 | Brute Force: Password Guessing | Initial Access | ATT&CK ↗ |
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-PSA | Port Scan Analysis | Detect | T1046 | Deploy network intrusion detection (NIDS) to identify sequential TCP SYN scans and unauthorized subnet reconnaissance. |
D3-AL | Account Lockout Policy | Harden | T1110.001 | Enforce progressive delay and lockout thresholds on failed authentication attempts to thwart brute-force password guessing. |
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_FSPM_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fspm"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fspm" ascii wide nocase
$s2 = "hacktool.fspm" ascii wide nocase
$s3 = "exploit.win32.fspm" ascii wide nocase
$s4 = "tool.networkscanner" 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 - Fspm (Ransomware) Execution & Triage
id: 4a8b00d2-f97e-5453-b89f-c64f29b284cb
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fspm 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/fspm
- 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.t1046
- attack.t1135
- attack.t1110_001
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_FSPM_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fspm 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 = "fspm" 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.
- Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Fspm from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
- Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Fspm symmetric encryption keys or uncompiled payload components may still reside in memory.
- 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 Fspm to inhibit recovery.
- 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.
- Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Fspm 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.
- Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Fspm.
- Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
- Do not connect clean backup drives or external storage to the affected network until Fspm eradication is completely verified.
References & External Analysis
- Search "fspm" on VirusTotal (External Analysis)
- Search "fspm" on Any.Run (Sandbox Sandbox)
- Search "fspm" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Fspm and what threat category does it belong to?
Fspm is classified as a Ransomware. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Fspm establish persistence and evade defensive controls?
Fspm typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Fspm compromise?
Security teams responding to Fspm should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What cryptographic algorithms and file targeting techniques does HackTool.Fspm employ during execution?
HackTool.Fspm typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options.
Are decryptors available for HackTool.Fspm, and what is the recommended recovery procedure?
Decryption availability for HackTool.Fspm depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups.
How do I remove Fspm from Windows?
Manual removal of Fspm 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.
What are the main symptoms of a Fspm infection?
Symptoms of Fspm 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 Fspm 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/fspm.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.