Snipr
Table of Contents
Overview
HackTool:Win32/Snipr is a classification for malicious tools specifically designed to automate 'Credential Stuffing' attacks. While not a virus that infects a host in the traditional sense, Snipr (and similar tools like SentryMBA or OpenBullet) are used by cybercriminals to take massive lists of leaked usernames and passwords from previous breaches and automatically test them against high-value targets like banking sites, streaming services, or corporate VPNs (`T1110.004`).
Understanding Snipr (Credential Stuffing)
To an end-user, they may suddenly find their Netflix or bank account compromised, even though they didn't click a phishing link (because they reused a password). For a SOC analyst, detecting Snipr on a corporate endpoint means an insider or an attacker who has already breached the perimeter is actively using the corporate network as a launchpad to conduct attacks against external (or internal) web applications.
Execution and Attack Mechanics
Snipr requires a 'combo list' (millions of `username:password` pairs) and a configuration file that tells the tool how to interact with the target website's login form. Upon execution, the attacker loads proxies (`T1090`) to distribute the login requests and hide their true IP address. Snipr then launches thousands of concurrent HTTP POST requests to the target login page (`T1110.004`). It analyzes the HTTP response codes or page text to determine if the login was successful, saving valid accounts to a 'hits' file.
Indicators of Compromise & Impact
The impact is the mass compromise of user accounts leading to fraud or unauthorized access. Host-based IoCs include the presence of the Snipr executable, large text files containing 'combo lists' (`username:password` pairs), and configuration files tailored to specific web applications. Network IoCs are highly visible if not proxied: a massive volume of outbound HTTP POST requests directed at a single URL (the login page of a target service), originating from the endpoint.
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 |
|---|---|---|---|
T1110.004 | Brute Force: Credential Stuffing (The core function of the Snipr tool) | Credential Access | ATT&CK ↗ |
T1090 | Proxy (Utilizing proxy lists to distribute the attack and evade rate limiting) | Command and Control | ATT&CK ↗ |
T1589.001 | Gather Victim Identity Information: Credentials (Relying on previously breached password lists) | Reconnaissance | 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-OAA | Outbound Network Traffic Filtering | Isolate | T1090 | Restrict outbound connections to known external proxy relays and enforce enterprise forward proxy authentication. |
D3-AL | Account Lockout Policy | Harden | T1110.004 | Enforce progressive rate limiting and account lockout policies to prevent credential brute-force attacks. |
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_SNIPR_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Snipr"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "snipr" 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 - Snipr (Advanced Threat) Execution & Triage
id: aac43c8e-fb47-5d2d-8e1b-4825d52b9a9b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Snipr malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/snipr
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1589_001
- attack.t1090
- attack.t1110_004
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_SNIPR_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Snipr 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 = "snipr" 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.
- Terminate the Snipr process and isolate the machine to stop the outbound credential stuffing attack.
- Investigate how the tool arrived on the system. If an employee downloaded it, treat it as a severe Acceptable Use Policy violation or insider threat.
- If the tool was targeting *internal* corporate applications, immediately review the authentication logs for those apps to identify any successfully compromised accounts.
- Ensure Multi-Factor Authentication (MFA) is strictly enforced on all external-facing corporate portals to neutralize the threat of credential stuffing.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the user's local passwords are secure just because the machine was running Snipr; the tool itself is often bundled with malware.
- Avoid allowing users to reuse corporate passwords on personal services.
References & External Analysis
- Search "snipr" on VirusTotal (External Analysis)
- Search "snipr" on Any.Run (Sandbox Sandbox)
- Search "snipr" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Snipr and what threat category does it belong to?
Snipr is classified as a Advanced Threat. 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 Snipr establish persistence and evade defensive controls?
Snipr 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 Snipr compromise?
Security teams responding to Snipr 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 lateral movement and credential access tactics does Snipr leverage in enterprise intrusions?
Snipr frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers.
How does Snipr maintain covert communications and evade perimeter network monitoring?
Snipr often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering.
How do I remove the Snipr Advanced_Threat from Windows?
Manual removal of Snipr 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 Snipr a virus or a Advanced_Threat?
Snipr is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Snipr typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Snipr infection?
Symptoms of Snipr 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 Advanced_Threats
Want to prevent Snipr 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/snipr.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.