Vobfus
Table of Contents
Overview
Vobfus (also documented across antimalware products as Win32/Vobfus, Worm:Win32/Vobfus, and WORM_VOBFUS) is a pervasive Windows worm and trojan loader developed in Visual Basic that emerged in 2012. Renowned for its symbiotic infection relationship with the Beebone (Changeup/AAEH) botnet, Vobfus and Beebone form a mutual downloading loop: Vobfus downloads Beebone, which in turn downloads updated, heavily obfuscated variants of Vobfus, thwarting conventional antivirus disinfection. Vobfus spreads rapidly by copying itself to connected removable USB flash drives and network shares, frequently weaponizing Windows Shell LNK shortcut flaws such as CVE-2010-2568 alongside autorun.inf files. Upon infecting an endpoint, Vobfus modifies the registry to hide operating system files and extension names, disables Windows Update and security services, and reaches out to remote C2 infrastructure via encrypted HTTP traffic to stage secondary payloads, including ransomware, banking trojans, and password stealers. The botnet was targeted in a major coordinated international law enforcement takedown by the FBI, Europol, and CISA.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Visual Basic Worm Frameworks
Known Derivatives & Downstream Variants: Vobfus.A · Vobfus.B · Vobfus Beebone
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 |
|---|---|---|---|
T1091 | Replication Through Removable Media | Lateral Movement | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1059.003 | Command and Scripting Interpreter: Windows Command Shell | Execution | ATT&CK ↗ |
T1027 | Obfuscated Files or Information | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
- 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):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-BDA | Binary De-obfuscation & Unpacking | Analyze | T1027 | Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation. |
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-RMC | Removable Media Access Control | Harden | T1091 | Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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 ↗).
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.
5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d
Delivery vectors
Infected USB storage drives utilizing malicious LNK files exploiting CVE-2010-2568Secondary payload drops initiated by Beebone (Changeup) botnet nodes
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\VobfusWorm%APPDATA%\Roaming\vobfus.exe
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_VOBFUS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Vobfus"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "vobfus" ascii wide nocase
$s2 = "win32/vobfus" ascii wide nocase
$s3 = "worm:win32/vobfus" ascii wide nocase
$s4 = "worm_vobfus" ascii wide nocase
$s5 = "beebone worm" ascii wide nocase
$s6 = "vobfus.a" 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 - Vobfus (Worm) Execution & Triage
id: 5eaa6aa4-7794-512c-892e-08b8c79f16c4
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Vobfus 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/vobfus
- 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.worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1091
- attack.t1105
- attack.t1547_001
- attack.t1059_003
- attack.t1027
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_VOBFUS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Vobfus 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 = "vobfus" 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.
- Isolate the infected endpoint from corporate networks and disconnect all attached USB storage drives immediately.
- Simultaneously terminate both Vobfus and Beebone processes to break the mutual downloading loop.
- Restore Explorer registry settings to show hidden files and file extensions.
- Delete worm binaries from %APPDATA% and remove persistence keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
- Format and sanitize all removable flash media that were connected to the infected workstation.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not connect infected USB flash drives to uninfected administrative workstations without write-protection.
- Avoid attempting partial manual disinfection without killing both Vobfus and Beebone processes simultaneously.
References & External Analysis
- Microsoft Defender Security Intelligence - Worm:Win32/Vobfus
- Federal Bureau of Investigation - International Beebone Botnet Takedown
- Trend Micro Threat Encyclopedia - WORM_VOBFUS
- NIST National Vulnerability Database - CVE-2010-2568
- Search "vobfus" on VirusTotal (External Analysis)
- Search "vobfus" on Any.Run (Sandbox Sandbox)
- Search "vobfus" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is the Vobfus worm family?
Vobfus is a Visual Basic worm and downloader that spreads via USB drives and formed a symbiotic infection loop with Beebone.
What was the Vobfus-Beebone symbiotic relationship?
Vobfus downloaded Beebone, and Beebone downloaded fresh polymorphic copies of Vobfus, continuously reinfecting systems if only one was cleaned.
How does Vobfus spread across enterprise endpoints?
It replicates onto removable USB drives using autorun.inf and LNK shortcuts exploiting CVE-2010-2568, and scans network shares.
What defense evasion techniques does Vobfus employ?
It modifies Windows Explorer registry settings to hide hidden files and file extensions, disables Windows Update, and terminates security tools.
How was the Vobfus/Beebone botnet disrupted?
In 2015, the FBI, Europol, and CISA executed an international coordinated operation seizing around 100 domain names to sinkhole the botnet.
How do I remove the Vobfus Worm from Windows?
Manual removal of Vobfus 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 Vobfus a virus or a Worm?
Vobfus is classified as a Worm. Unlike traditional viruses that infect files, modern malware like Vobfus typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Vobfus infection?
Symptoms of Vobfus 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 Worms
Want to prevent Vobfus and similar threats from compromising your organization? Read our comprehensive defensive guide: Worm & Virus Protection.
📣 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/vobfus.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.