Hermes

Category: ransomware · Aliases: Hermes, Hermes 2.1, Ransom.Hermes, Trojan-Ransom.Win32.Hermes · Sample count (EMBER 2018): 7 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Initial-Access, Execution, Defense-Evasion, ImpactFirst seen: 2017Actor: Lazarus Group (APT38) ↗Actor: Hermes OperatorsIndustry: banking, financial_services, fintech, critical_infrastructureMotivation: Financial Extortion & Distraction Sabotage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Ransom:Win32/Hermes is a targeted, destructive ransomware strain first observed in early 2017 across Russian cybercrime underground forums.

Table of Contents

Overview

Ransom:Win32/Hermes is a targeted, destructive ransomware strain first observed in early 2017 across Russian cybercrime underground forums. In October 2017, Hermes rose to global prominence when it was deployed by the North Korean state-sponsored threat group Lazarus Group (specifically APT38 / Hidden Cobra) during the high-profile cyber heist against Taiwan's Far Eastern International Bank (FEIB). In that intrusion, Lazarus leveraged Hermes as a diversionary wiper-ransomware payload to paralyze incident responders, obscure forensic artifact trails, and destroy local system logs while operators executed fraudulent SWIFT interbank transactions totaling $60 million. Hermes is historically significant as the direct technological predecessor and codebase progenitor for Ryuk ransomware, which emerged in mid-2018 when the Wizard Spider cybercrime syndicate adapted Hermes' source code for targeted enterprise big-game hunting. Hermes employs RSA-2048 public key encryption paired with per-file AES-256-CBC symmetric keys, terminates critical database and backup services via batch script command loops (HERMES.bat), and securely destroys Shadow Copies through vssadmin and bcdedit system manipulation.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Known Derivatives & Downstream Variants: Hermes 2.1 (Taiwan Feib Heist) · Ryuk (Direct Successor) · Conti (Lineage)

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTPS, HTTP
Observed ports443, 80
Identifiable from traffic aloneMedium

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_HERMES_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Hermes"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "hermes" ascii wide nocase
        $s2 = "hermes" ascii wide nocase
        $s3 = "hermes 2.1" ascii wide nocase
        $s4 = "ransom.hermes" ascii wide nocase
        $s5 = "trojan-ransom.win32.hermes" 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 - Hermes (Ransomware) Execution & Triage
id: d9cfc5fd-05e0-593e-bc9f-55a46f6059f9
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Hermes malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/hermes
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1070_001
- attack.t1490
- attack.t1059_003
- attack.t1566_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_HERMES_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Hermes 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 = "hermes" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Segregate SWIFT messaging terminals and financial transaction hosts onto isolated, air-gapped VLANs.
  2. Deploy endpoint detection agents to identify and block batch script execution invoking vssadmin delete shadows.
  3. Inspect perimeter firewalls for anomalous outbound connections to known Lazarus Group command infrastructure.
  4. Enforce security updates for Microsoft Office equation editor vulnerabilities CVE-2017-0199 and CVE-2017-11882.

What to Avoid

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

  1. Do not allow direct internet access from financial processing or SWIFT financial network environments.
  2. Avoid running endpoint backups on mapped, write-accessible network shares accessible to ransomware operators.
  3. Never enable Office macro execution on inbound emails from external domains.

References & External Analysis

North American Authority Advisory (CISA / NIST)

The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: https://www.cisa.gov/news-events/cybersecurity-advisories/aa20-280a ↗

Frequently Asked Questions

What is Hermes ransomware?

Hermes is a targeted ransomware family first detected in 2017, known for its deployment in state-sponsored bank heists and for serving as the foundational codebase for Ryuk ransomware.

How was Hermes used in the Far Eastern International Bank (FEIB) heist?

Lazarus Group (APT38) deployed Hermes on FEIB network servers to destroy event logs and distract security analysts while the group executed $60 million in fraudulent SWIFT financial transfers.

What is the relationship between Hermes and Ryuk?

Ryuk ransomware was directly created from the Hermes 2.1 source code, retaining identical cryptographic file structures, encryption markers, and batch script execution commands.

What cryptographic algorithms are used by Hermes?

Hermes uses AES-256-CBC to encrypt file contents and RSA-2048 to encrypt the AES symmetric session keys, appending the 'HERMES' file marker.

What vulnerabilities were used to distribute Hermes?

Hermes payloads were delivered via spear-phishing emails containing malicious Microsoft Office attachments exploiting CVE-2017-0199 and CVE-2017-11882.

How do I remove the Hermes Ransomware from Windows?

Manual removal of Hermes 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 Hermes a virus or a Ransomware?

Hermes is classified as a Ransomware. Unlike traditional viruses that infect files, modern malware like Hermes typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Hermes infection?

Symptoms of Hermes 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 Ransomwares

Want to prevent Hermes and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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