LiveActive security incident?Get immediate response
MITRE ATT&CK® Malware

S0611: Clop

Clop is a ransomware family that was first observed in February 2019 and has been used against retail, transportation and logistics, education, manufacturing, engineering, automotive, energy, financial, aerospace, telecommunications, professional and legal services, healthcare, and high tech industries. Clop is a variant of the CryptoMix ransomware.[1][2][3]

EnterpriseS0611MalwareObject v1.0Modified
Discuss defensive coverageBack to ATT&CK
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceMedium

Clop is a Windows ransomware family documented by ATT&CK and associated with activity across many industries. Its defensive significance is not just encryption: the mapped behaviors include discovery of processes, files, shares, security software, registry modification, abuse of command shell and msiexec, service stopping, recovery inhibition, tool impairment, and data encryption for impact. For leaders, this makes Clop a useful ransomware readiness benchmark: can the organization detect preparation, containment blockers, and recovery sabotage before encryption becomes a business-continuity event?

Executive priority

Prioritize Clop as a resilience and evidence-readiness use case for Windows environments. The key business questions are whether critical file shares are monitored, whether recovery mechanisms are protected from tampering, whether SOC teams can see service stops and security-tool degradation, and whether incident responders can quickly identify affected hosts and preserve audit-quality evidence. ATT&CK also relates Clop to TA505, a cyber criminal group known for ransomware campaigns involving Clop, so threat intelligence teams should treat it as relevant context without assuming attribution in any local incident.

Technical view

Validate coverage against the ATT&CK relationships rather than relying on a single ransomware signature. For Windows endpoints, test visibility for cmd.exe execution, msiexec.exe abuse, registry changes, process and file discovery, network share discovery, security software discovery, service stop activity, recovery-inhibition behavior, security tool modification, packed or obfuscated binaries, code-signing metadata, time-based anti-analysis checks, and high-volume file encryption patterns. Because ATT&CK provides no official detection text for this object, SOC teams should map local analytics to the related techniques and verify that logs survive tool tampering and service disruption.

Likely telemetry

  • Windows endpoint process creation and command-line logs
  • Msiexec execution and parent-child process relationships
  • Registry modification events
  • File and directory enumeration activity
  • Network share and SMB access/enumeration telemetry

Detection direction

  • Do not depend only on ransomware hash or signature matching; the object maps to packing, obfuscation, and code-signing-related defense evasion.
  • Correlate discovery activity with later impact behaviors: process discovery, security software discovery, file/share enumeration, service stops, and recovery inhibition are more meaningful together than alone.
  • Tune false positives for legitimate administration tools such as cmd.exe, reg, service control, and msiexec by baselining expected administrators, software deployment systems, paths, and timing.
  • Confirm alerts still fire when security tools or logging agents are stopped, modified, or degraded.
  • Use the TA505 relationship as threat-intelligence context, not as automatic attribution for any observed activity.

Mitigation priorities

  • Harden and monitor Windows endpoints and servers that host business-critical files and shares.
  • Protect backups and recovery features from endpoint-level tampering, and test restore procedures independently of production hosts.
  • Restrict and monitor administrative utilities and living-off-the-land execution paths such as command shell, registry tools, service control, and msiexec where operationally feasible.
  • Ensure endpoint security tooling, logging agents, and alert pipelines have tamper monitoring and operational health checks.
  • Segment access to shared storage and critical services so discovery and encryption on one host does not automatically create enterprise-wide impact.
Additional notes and limits

ATT&CK lists Clop as a Windows ransomware family and a CryptoMix variant first observed in February 2019, with cited reporting across retail, transportation and logistics, education, manufacturing, engineering, automotive, energy, financial, aerospace, telecommunications, professional and legal services, healthcare, and high tech industries. The most useful defensive value comes from the mapped techniques and the TA505 relationship, which together support ransomware preparedness, SOC validation, and incident-response planning.

No official ATT&CK detection guidance is provided for this object, and tactics are not specified on the malware object itself. Platform scope should be treated as Windows for Clop based on the supplied object, even though some related technique descriptions list additional platforms. Local telemetry, asset criticality, backup architecture, and control configuration are required to determine actual exposure or detection coverage.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

Clop

Clop is a ransomware family that was first observed in February 2019 and has been used against retail, transportation and logistics, education, manufacturing, engineering, automotive, energy, financial, aerospace, telecommunications, professional and legal services, healthcare, and high tech industries. Clop is a variant of the CryptoMix ransomware.[1][2][3]

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

17 rows
DomainIDNameRelationship / procedure
EnterpriseT1518.001Security Software DiscoverySub-technique

Clop can search for processes with antivirus and antimalware product names.[1][2]

EnterpriseT1489Service Stop

Clop can kill several processes and services related to backups and security solutions.[3][1]

EnterpriseT1140Deobfuscate/Decode Files or Information

Clop has used a simple XOR operation to decrypt strings.[1]

EnterpriseT1106Native API

Clop has used built-in API functions such as WNetOpenEnumW(), WNetEnumResourceW(), WNetCloseEnum(), GetProcAddress(), and VirtualAlloc().[1][2]

EnterpriseT1497.003Time Based ChecksSub-technique

Clop has used the sleep command to avoid sandbox detection.[3]

EnterpriseT1027.002Software PackingSub-technique

Clop has been packed to help avoid detection.[1][2]

EnterpriseT1614.001System Language DiscoverySub-technique

Clop has checked the keyboard language using the GetKeyboardLayout() function to avoid installation on Russian-language or other Commonwealth of Independent States-language machines; it will also check the GetTextCharset function.[1]

EnterpriseT1083File and Directory Discovery

Clop has searched folders and subfolders for files to encrypt.[1]

EnterpriseT1057Process Discovery

Clop can enumerate all processes on the victim's machine.[1]

EnterpriseT1059.003Windows Command ShellSub-technique

Clop can use cmd.exe to help execute commands on the system.[2]

EnterpriseT1553.002Code SigningSub-technique

Clop can use code signing to evade detection.[3]

EnterpriseT1112Modify Registry

Clop can make modifications to Registry keys.[2]

EnterpriseT1135Network Share Discovery

Clop can enumerate network shares.[1]

EnterpriseT1490Inhibit System Recovery

Clop can delete the shadow volumes with vssadmin Delete Shadows /all /quiet and can use bcdedit to disable recovery options.[1]

EnterpriseT1486Data Encrypted for Impact

Clop can encrypt files using AES, RSA, and RC4 and will add the ".clop" extension to encrypted files.[1][3][2]

EnterpriseT1685Disable or Modify Tools

Clop can uninstall or disable security products.[2]

EnterpriseT1218.007MsiexecSub-technique

Clop can use msiexec.exe to disable security tools on the system.[2]

Associated objects

Groups, software, and campaigns

GroupEnterprise

G0092: TA505

TA505 is a cyber criminal group that has been active since at least 2014. TA505 is known for frequently changing malware, driving global trends in criminal malware distribution, and ransomware campaigns involving Clop.[1][2][3][4][5]

Relationship explorer

All related ATT&CK context

uses · TechniqueT1518.001: Security Software DiscoveryEnterpriseuses · TechniqueT1489: Service StopEnterpriseuses · GroupG0092: TA505Enterpriseuses · TechniqueT1140: Deobfuscate/Decode Files or InformationEnterpriseuses · TechniqueT1106: Native APIEnterpriseuses · TechniqueT1497.003: Time Based ChecksEnterpriseuses · TechniqueT1027.002: Software PackingEnterpriseuses · TechniqueT1614.001: System Language DiscoveryEnterpriseuses · TechniqueT1083: File and Directory DiscoveryEnterpriseuses · TechniqueT1057: Process DiscoveryEnterpriseuses · TechniqueT1059.003: Windows Command ShellEnterpriseuses · TechniqueT1553.002: Code SigningEnterpriseuses · TechniqueT1112: Modify RegistryEnterpriseuses · TechniqueT1135: Network Share DiscoveryEnterpriseuses · TechniqueT1490: Inhibit System RecoveryEnterpriseuses · TechniqueT1486: Data Encrypted for ImpactEnterpriseuses · TechniqueT1685: Disable or Modify ToolsEnterpriseuses · TechniqueT1218.007: MsiexecEnterprise
Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
5d5bb2e6bbae3767...
Imported snapshots across ATT&CK releases(1)
ReleaseBundle importedObject versionModifiedStatusRaw hash
19.11.0Current bundle5d5bb2e6bbae…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Open mirrored raw JSONOpen MITRE-hosted copy
Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  2. [2]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  3. [3]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  4. [4]
    Clop

    (Citation: Mcafee Clop Aug 2019)(Citation: Cybereason Clop Dec 2020)

  5. [5]
    Clop

    (Citation: Mcafee Clop Aug 2019)(Citation: Cybereason Clop Dec 2020)

  6. [6]
    Clop

    (Citation: Mcafee Clop Aug 2019)(Citation: Cybereason Clop Dec 2020)

  7. [7]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  8. [8]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  9. [9]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  10. [10]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  11. [11]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  12. [12]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  13. [13]
    mitre-attackS0611
    Open source URL
  14. [14]
    mitre-attackS0611
    Open source URL
  15. [15]
    mitre-attackS0611
    Open source URL
  16. [16]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  17. [17]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  18. [18]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  19. [19]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  20. [20]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  21. [21]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  22. [22]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  23. [23]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  24. [24]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  25. [25]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  26. [26]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  27. [27]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  28. [28]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  29. [29]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  30. [30]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  31. [31]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  32. [32]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  33. [33]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  34. [34]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  35. [35]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  36. [36]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  37. [37]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  38. [38]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  39. [39]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  40. [40]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  41. [41]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  42. [42]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  43. [43]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  44. [44]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  45. [45]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  46. [46]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  47. [47]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  48. [48]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  49. [49]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  50. [50]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  51. [51]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  52. [52]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  53. [53]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  54. [54]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  55. [55]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  56. [56]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  57. [57]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  58. [58]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  59. [59]
    Mcafee Clop Aug 2019

    Mundo, A. (2019, August 1). Clop Ransomware. Retrieved May 10, 2021.

    Open source URL
  60. [60]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  61. [61]
    Unit42 Clop April 2021

    Santos, D. (2021, April 13). Threat Assessment: Clop Ransomware. Retrieved July 30, 2021.

    Open source URL
  62. [62]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
  63. [63]
    Cybereason Clop Dec 2020

    Cybereason Nocturnus. (2020, December 23). Cybereason vs. Clop Ransomware. Retrieved May 11, 2021.

    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.

Official MITRE ATT&CK siteOfficial STIX data repositoryMITRE ATT&CK terms of use