Computty
Table of Contents
Overview
Executive Summary
Computty (often detected as HackTool.PuTTY.Modified or Trojan.PuTTY) is a malicious modification of the legitimate, highly popular open-source SSH and Telnet client, PuTTY. Threat actors take the legitimate PuTTY source code, inject malicious functionality (usually a credential stealer or a backdoor), recompile it, and distribute it to system administrators, allowing the attackers to intercept highly privileged authentication credentials.Infection Vector and Technical Capabilities
The modified PuTTY executable is typically distributed via spear-phishing campaigns targeting IT staff, or by hosting the backdoored software on lookalike "typosquatting" domains designed to mimic the official PuTTY download page. Upon execution, the tool functions exactly like the legitimate PuTTY client, allowing the administrator to successfully connect to remote servers. However, it operates with severe malicious intent:- Credential Harvesting: The core malicious functionality is to intercept the usernames, passwords, and SSH private keys entered by the administrator when authenticating to a remote server.
- Covert Exfiltration: The stolen credentials are silently logged and periodically transmitted to an attacker-controlled command-and-control (C2) server, usually over HTTP or SMTP to blend in with normal traffic.
- Evasion: Because the underlying code is the legitimate PuTTY client, the backdoored executable often evades basic signature-based antivirus detection, appearing as a standard administrative tool.
Threat Assessment
The compromise of an administrative tool like PuTTY is a catastrophic security incident. By stealing SSH credentials, the attackers gain direct, highly privileged access to the organization's core infrastructure (Linux servers, firewalls, routers), entirely bypassing perimeter defenses and multi-factor authentication (if keys are stolen).Incident Response and Remediation
- Immediate Global Key Rotation: If a modified PuTTY executable is discovered, assume that every server the administrator connected to has been compromised. Immediately revoke and regenerate all SSH keys and passwords associated with that administrator.
- Endpoint Sweeps and File Hashing: Utilize enterprise EDR to sweep the network for the specific hash of the modified PuTTY binary. Remove the malicious executable and enforce the usage of centrally deployed, verified IT tools.
- Network Segmentation and MFA: Enforce Multi-Factor Authentication (MFA) for all administrative SSH connections, ensuring that stolen credentials alone are insufficient for access.
Known aliases
Threat reports may refer to this family under multiple names:
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 |
|---|---|---|---|
T1552.004 | Unsecured Credentials: Private Keys | Credential Access | ATT&CK ↗ |
T1056.001 | Keylogging | Credential Access | ATT&CK ↗ |
T1556 | Modify Authentication Process | Credential Access | ATT&CK ↗ |
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.
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-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-APA | Authentication Process Auditing | Detect | T1556 | Verify cryptographic signatures of Windows authentication packages and security support providers (SSPs). |
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_COMPUTTY_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Computty"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "computty" ascii wide nocase
$s2 = "hacktool.putty" ascii wide nocase
$s3 = "trojan.putty.modified" ascii wide nocase
$s4 = "pws.putty" 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 - Computty (Trojan) Execution & Triage
id: 83f77af8-1d95-580b-b26c-fdd469e89e39
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Computty 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/computty
- 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.t1552_004
- attack.t1056_001
- attack.t1556
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_COMPUTTY_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Computty 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 = "computty" 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.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Computty from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Computty into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Computty persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Computty execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Computty dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Computty until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "computty" on VirusTotal (External Analysis)
- Search "computty" on Any.Run (Sandbox Sandbox)
- Search "computty" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Computty and what threat category does it belong to?
Computty is classified as a Trojan. 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 Computty establish persistence and evade defensive controls?
Computty 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 Computty compromise?
Security teams responding to Computty 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 secondary payloads and staging behaviors are commonly associated with HackTool.PuTTY?
HackTool.PuTTY frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for HackTool.PuTTY across enterprise endpoints?
Defenders should hunt for HackTool.PuTTY by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove Computty from Windows?
Manual removal of Computty 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.
What are the main symptoms of a Computty infection?
Symptoms of Computty 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 Trojans
Want to prevent Computty and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 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/computty.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.