Spywork

Overview

Executive Summary

Technical Capabilities and Behavior

• Keylogging: Recording every keystroke to capture passwords, banking details, and confidential communications.
• Screen Capture: Taking periodic screenshots of the desktop, particularly when specific applications (like banking portals or email clients) are brought into focus.
• Clipboard Monitoring: Stealing data copied to the clipboard, frequently targeting cryptocurrency wallet addresses and passwords.

Risk Assessment

Eradication and Incident Response

• Memory Forensics: Because Spywork heavily utilizes process injection, memory analysis is often required to identify the injected threads and trace the malware back to its source executable.
• Credential Rotation: Upon detection, all passwords and authentication tokens utilized on the infected machine must be immediately revoked and rotated.
• Network Segmentation: Isolate the compromised host to prevent the spyware from harvesting lateral movement credentials or network maps.

Known aliases

Threat reports may refer to this family under multiple names:

• Spyware.Spywork
• TrojanSpy.Spywork
• Win32/Spywork

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:

• T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
• T1113: Monitor for frequent or unauthorized screen captures or clipboard reads. Restrict background applications from accessing desktop APIs.

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

title: SystemHelpDesk Detection - Spywork (Advanced Threat) Execution & Triage
id: 2551e93f-41f0-5c23-a4c5-6a7f2035bdd6
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Spywork 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/spywork
- 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.t1056_001
- attack.t1113
- attack.t1055
- attack.t1115
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: high

rule MALWARE_WIN_SPYWORK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Spywork 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 = "spywork" 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. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Spywork adversary activity.
2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Spywork C2 infrastructure IP/domain lists.
3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Spywork.
4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Spywork operators.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Spywork dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Spywork until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Advanced Threat)

Explore other documented threats in the same operational category:

• Oneclickdownloader
• Installmetrix
• Progressive
• Malxmr
• Scramupx
• Popwin
• Smbd
• Peed

Machine-readable

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