Picsys

Overview

PicSys (cataloged by security vendors under detections including Trojan:Win32/PicSys, Trojan.Win32.Picsys, and Worm.Win32.PICSYS) is a covert surveillance trojan and spyware threat active since 2011. Typically distributed via pirated software cracks, deceptive image-viewing utilities, and malicious spearphishing email attachments, PicSys is engineered to perform comprehensive endpoint surveillance without user detection. Once resident on Windows, PicSys drops persistence copies into system directories and hooks Windows message queues to record all user keystrokes (keylogging), captures periodic desktop screenshots during active user sessions, and monitors active application windows. Furthermore, PicSys compiles stolen system credentials, document files, and user telemetry into encrypted archives and exfiltrates them to attacker-controlled command-and-control servers via HTTP, FTP, or SMTP channels.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan:Win32/PicSys
• Trojan.Win32.Picsys
• Worm.Win32.PICSYS
• Win32/PicSys

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: Generic Win32 Spyware Families

Known Derivatives & Downstream Variants: Picsys.A · Picsys.B

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

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.

• 9b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c
• 4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b

Delivery vectors

• photo_viewer_setup.exe
• picsys_core.exe

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\PicSysAgent
• %AppData%\PicSys\picsys_svc.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:

rule MALWARE_WIN_PICSYS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Picsys"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "picsys" ascii wide nocase
        $s2 = "trojan:win32/picsys" ascii wide nocase
        $s3 = "trojan.win32.picsys" ascii wide nocase
        $s4 = "worm.win32.picsys" ascii wide nocase
        $s5 = "win32/picsys" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Picsys (Trojan) Execution & Triage
id: 18565ba9-d107-5db7-a4c1-5a8ab3fb18fb
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Picsys 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/picsys
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1204_002
- attack.t1059_003
- attack.t1547_001
- attack.t1056_001
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

rule MALWARE_WIN_PICSYS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Picsys 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 = "picsys" 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. Immediately isolate the endpoint; the aggressive system modifications make the machine fundamentally untrustworthy and likely open to secondary payloads.
2. Utilize EDR or offline registry analysis tools to identify and reverse the malicious registry modifications (especially those disabling security tools).
3. Audit the `HOSTS` file (`C:\Windows\System32\drivers\etc\hosts`) and remove any entries redirecting security vendor domains to `127.0.0.1`.
4. Due to the depth of the system modifications, the most secure remediation is a complete, clean rebuild of the operating system.

What to Avoid

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

1. Do not trust the endpoint's built-in security tools or logs; a Picsys infection is explicitly designed to disable or tamper with these mechanisms.
2. Avoid relying solely on automated AV removal, as the malware may have replaced legitimate system files that AV cannot safely delete.

References & External Analysis

• Kaspersky Threat Intelligence Portal - Trojan.Win32.Picsys
• Microsoft Defender Security Intelligence - Trojan:Win32/PicSys
• Search "picsys" on VirusTotal (External Analysis)
• Search "picsys" on Any.Run (Sandbox Sandbox)
• Search "picsys" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Zombierat
• Carambisdu
• Gamevance
• Napolar
• Guagua
• Genericrxce
• Ciadoor
• Imminent

Machine-readable

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