Skip to navigation

Threat reportMalwareTL-2026-3608

Agent.BTZ USB-borne worm infection of US Central Command and DoD networks (2008, Operation Buckshot Yankee) - retrospective on Air Force removable-media mission-planning practices

lowRESOLVED

A 2026-10-15 retrospective (The Register) recounts how Air Force reliance on USB drives and CDs to move mission-planning data between classified and unclassified systems preceded the 2008 Agent.BTZ infection of US DoD networks, which began with an infected USB drive attached to a laptop with Central Command access.

Key facts

IdentifiersTL-2026-3608
Also known asOperation Buckshot Yankee, Agent.btz
SeverityLOW
Affected productsMicrosoft Windows (systems with autorun.inf handling enabled); US Department of Defense Central Command-connected laptops and DoD networks incl. SIPRNet/JWICS as publicly reported
Nation-state nexusRussia
MalwareAgent.btz - S0092, SillyFDC, Trojan-Downloader.Win32.Agent.sxi, Turla, Voronezh.1600, Worm.Win32.Orbina
ToolsTurla
MITRE ATT&CK techniquesT1005 Data from Local System, T1025 Data from Removable Media, T1052.001 Exfiltration Over Physical Medium: Exfiltration over USB, T1074.001 Data Staged: Local Data Staging, T1091 Replication Through Removable Media, T1092 Communication Through Removable Media
MotivationESPIONAGE
Target sectorsgovernment administration, defense, military
Target regionsNorth America, Middle East
Detection rules9 (1 shown free)
Sources6 cited sources

Detection coverage

As of 2026-10-15, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-3608 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Agent.BTZ Component Names in Process Command Lines (Post-Exploitation)

Detects process creation whose command line references Agent.BTZ components (winview.ocx, wmcache.nld, mswmpdat.tlb, mssysmgr.ocx, fa.tmp, thumb.dd, sunstore.dmp). Covers loading the OCX via rundll32/regsvr32 and the secondary-infection copy of thumb.dd to mssysmgr.ocx described by Securelist.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1091, T1005, T1074.001, T1218.011
  • Data sources: sysmon (EventCode 1), microsoft_defender_for_endpoint (DeviceProcessEvents)
  • Severity: high
  • Confidence: high

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h
| where match(CommandLine,"(?i)(winview\.ocx|wmcache\.nld|mswmpdat\.tlb|mssysmgr\.ocx|thumb\.dd|fa\.tmp|sunstore\.dmp)")
| eval tool=lower(replace(Image, "^.*\\\\", ""))
| stats count min(_time) AS first_seen values(CommandLine) AS cmdlines values(ParentImage) AS parents by Computer, User, tool
| convert ctime(first_seen)

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where ProcessCommandLine has_any ("winview.ocx", "wmcache.nld", "mswmpdat.tlb", "mssysmgr.ocx", "thumb.dd", "fa.tmp", "sunstore.dmp")
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA256

Sigma

title: Agent.BTZ Component Names in Process Command Line
id: 8d21b7a4-5c3e-4f60-9b1a-2e4c6d8f0a52
status: experimental
description: Detects process command lines referencing Agent.BTZ components such as winview.ocx, wmcache.nld, mswmpdat.tlb, mssysmgr.ocx, thumb.dd, fa.tmp or sunstore.dmp.
references:
    - https://securelist.com/agent-btz-a-source-of-inspiration/58551/
    - https://attack.mitre.org/software/S0092/
author: Threadlinqs Team
date: 2026/10/15
tags:
    - attack.lateral_movement
    - attack.t1091
    - attack.collection
    - attack.t1005
    - attack.t1074.001
    - attack.defense_evasion
    - attack.t1218.011
    - attack.s0092
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        CommandLine|contains:
            - 'thumb.dd'
            - 'winview.ocx'
            - 'wmcache.nld'
            - 'mswmpdat.tlb'
            - 'mssysmgr.ocx'
            - 'fa.tmp'
            - 'sunstore.dmp'
    condition: selection
falsepositives:
    - Malware analysts or EDR tooling referencing sample filenames
    - Administrators searching for these filenames during hunting
level: high

Known false positives:

  • Hunting commands run by SOC analysts that search for these filenames
  • Antivirus or EDR scanners passing IOC filenames on the command line

Tuning notes: Exclude SOC jump hosts and the EDR scanner process. fa.tmp is generic enough to warrant pairing with a rundll32/regsvr32/cmd parent in noisy estates.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Executable Launched from Non-System Volume by Explorer — Removable-Media Execution (Exploitation) · unlock with TL Creds
  • Agent.BTZ Log/Component Files Written to Windows System Directories (Post-Exploitation) · unlock with TL Creds
  • rundll32/regsvr32 Outbound Connection to Public IP — Agent.BTZ Remote C2 (C2) · unlock with TL Creds
  • USB Mass-Storage Device Recognised — Removable-Media Insertion on Protected Host (Exploitation) · unlock with TL Creds
  • Archiving or Bulk-Copy Utility Reading from Non-System Drive — Removable-Media Collection (Post-Exploitation) · unlock with TL Creds
  • [indicator] Container Written — Agent.BTZ Communication and Exfiltration via Removable Media (C2) · unlock with TL Creds
  • Agent.BTZ USB Worm — [indicator] Drop and Known Artifact Filenames (Exploitation) · unlock with TL Creds
  • Worm Replication to Removable Drive — [indicator] Plus Payload at Drive Root (Lateral Movement) · unlock with TL Creds

Indicators of compromise

As of 2026-10-15, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-3608.

15 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Removal took 14 months and the Pentagon banned USB drives in 2008, permitting them again in 2010 under restricted circumstances.

This record is a historical retrospective, not a new campaign. The Register (2026-10-15) quotes Justin Henkel, SolarWinds CISO and former Air Force IT security, describing a practice dating to the early 2000s of moving mission-planning data between classified and unclassified systems on CDs and USB drives. Pilots used the same devices for both purposes and, per Henkel, did not understand that a USB drive could be written to with malware. Drives were also bought from local Middle Eastern vendors rather than official channels, a supply-chain exposure; Henkel said it was harder to bring a US computer into the country than to buy locally.

In 2008 an infected USB drive connected to a laptop with US Central Command access led to infection of DoD networks with Agent.BTZ, a worm able to harvest information from infected machines and communicate with remote servers. The Register reports it took 14 months to remove the malware from Pentagon systems, that the Pentagon banned USB drives in 2008 and allowed them again in 2010 under certain circumstances, and that a 2016 FBI/DHS report attributed the malware to one or more Russian groups (as stated in the article).

Public technical analysis (Kaspersky Securelist) describes Agent.btz as a variant of the SillyFDC family that spreads by copying itself to other USB drives via autorun.inf, stores harvested system data in a container file (thumb.dd) on removable drives for exfiltration when direct C2 is unavailable, and uses log/component names such as winview.ocx, wmcache.nld and mswmpdat.tlb. Kaspersky found that later Turla (Snake/Uroburos) samples reuse the same XOR key and file names, linking the two codebases. Public reporting dates the Pentagon incident to November 2008 (Operation Buckshot Yankee) and credits it as one driver for creation of US Cyber Command in 2010. No CVE, network IOCs or new exploitation are associated with this retrospective; the value for defenders is removable-media and cross-domain transfer control lessons.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System; T1025 Data from Removable Media; T1074.001 Data Staged: Local Data Staging

Exfiltration

T1052.001 Exfiltration Over Physical Medium: Exfiltration over USB

Initial Access

T1091 Replication Through Removable Media

Lateral Movement

T1091 Replication Through Removable Media

Command and Control

T1092 Communication Through Removable Media

Remediation

Immediate actions

  • Disable autorun/autoplay for removable media on all endpoints
  • Block or tightly control USB mass-storage devices on classified and sensitive networks
  • Hunt for Agent.btz artifacts: thumb.dd, winview.ocx, wmcache.nld, mswmpdat.tlb, mssysmgr.ocx, fa.tmp

Workarounds

  • Enforce device-control policy allowing only approved, encrypted, registered removable media

Longer-term hardening

  • Use dedicated, scanned, one-direction cross-domain transfer solutions instead of shared USB drives
  • Procure removable media only from vetted supply chains; do not use locally purchased drives
  • Train personnel on the risk of reusing the same device across classified and unclassified systems

Affected and fixed versions

  • Microsoft — Windows (systems with autorun.inf handling enabled)
    Vulnerable versions: Systems in US DoD networks in 2008
  • US Department of Defense — Central Command-connected laptops and DoD networks incl. SIPRNet/JWICS as publicly reported
    Vulnerable versions: 2008

Timeline

  • Initial Agent.btz variant created, per Kaspersky Securelist analysis (year-level precision)
  • Pentagon bans USB drives following the Agent.btz infection
  • Agent.btz detected on DoD networks after an infected USB drive was connected to a laptop with US Central Command access (month-level date per public reporting)
  • USB drives permitted again under restricted circumstances (public reporting dates the ban as November 2008 to February 2010)
  • US Cyber Command reached initial operating capability; public reporting cites the 2008 incident as one driver for its creation (year 2010 per sources; date approximate)
  • FBI/DHS report attributes Agent.BTZ to one or more Russian groups, as stated by The Register (year-level precision)
  • The Register publishes Justin Henkel's account of Air Force USB/CD mission-planning practices and the Agent.BTZ infection

Sources cited

Previous and next in malware

Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats