Trojan.Kryptik.Gen.ECL
Threat Scorecard
EnigmaSoft Threat Scorecard
EnigmaSoft Threat Scorecards are assessment reports for different malware threats which have been collected and analyzed by our research team. EnigmaSoft Threat Scorecards evaluate and rank threats using several metrics including real-world and potential risk factors, trends, frequency, prevalence, and persistence. EnigmaSoft Threat Scorecards are updated regularly based on our research data and metrics and are useful for a wide range of computer users, from end users seeking solutions to remove malware from their systems to security experts analyzing threats.
EnigmaSoft Threat Scorecards display a variety of useful information, including:
Popularity Rank: The ranking of a particular threat in EnigmaSoft’s Threat Database.
Severity Level: The determined severity level of an object, represented numerically, based on our risk modeling process and research, as explained in our Threat Assessment Criteria.
Infected Computers: The number of confirmed and suspected cases of a particular threat detected on infected computers as reported by SpyHunter.
See also Threat Assessment Criteria.
| Popularity Rank: | 3,793 |
| Threat Level: | 80 % (High) |
| Infected Computers: | 65 |
| First Seen: | April 2, 2026 |
| Last Seen: | May 19, 2026 |
| OS(es) Affected: | Windows |
Table of Contents
Analysis Report
General information
| Family Name: | Trojan.Kryptik.Gen.ECL |
|---|---|
| Signature status: | Self Signed |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
71433eadba3f3f3d258e75d98841fa39
SHA1:
4deb46f25d9e030e273fc8ffb8ec8d092484126b
SHA256:
5A509D88669F780465BC59AD9BD092FC3AB4538B6B2653AD02173F1197C23FD1
File Size:
656.19 KB, 656192 bytes
|
|
MD5:
2784d93333fa8284267a70b25ed00706
SHA1:
3dcb019973629bcdb423ac6e0df1ef29c4fbd89f
SHA256:
05995356583300D087CB73DA34FC9722099C6229325CBE240BF6BA32AAC258A5
File Size:
658.76 KB, 658760 bytes
|
|
MD5:
b4e67369a59afe62a9cdd1880d2868ff
SHA1:
6c1922d307d988c619604f1f97795d33c94e290b
SHA256:
BB988E1314B4B3B7EDB504C609D75A1F0836E33A13A45642629072F29C27DFD6
File Size:
1.26 MB, 1256736 bytes
|
|
MD5:
a7b2e65ec3aed0ff8de3788dd56c6432
SHA1:
d035da4f55af9c977f622270ab52ee69faec1d87
SHA256:
F82D272A52C56F65D66AC665F3074639B93B61C094D27C75E0C77B9BAFFE896F
File Size:
733.44 KB, 733440 bytes
|
|
MD5:
8c0b07374898e76cadd6d36e68959682
SHA1:
c23da96e2e71d8487c839b75bfaad1e7f8b7a3a8
SHA256:
5EB440933EFC934628399697E2BCA83AC41CEFBB7C653DAE1B91113596C4755E
File Size:
757.22 KB, 757216 bytes
|
Show More
|
MD5:
49f217620e429887aaccfcfc5fe837d8
SHA1:
759d9d9f03b0747ab56ae978437c03ffc3c98519
SHA256:
28D0F6D874866FA512432E6490F3FD1113DC0EFD5A7E0E324437DA8D8B2C9CF7
File Size:
708.67 KB, 708672 bytes
|
|
MD5:
edf36c64fba1ac5955e842b4a0b89f3d
SHA1:
a06086c97524c14b6959e143998ce8204d966b26
SHA256:
C9E71805E48DAA579BFC7B3C429A86BA95AF99B9EAF6B96E8444F98240260919
File Size:
1.55 MB, 1545440 bytes
|
|
MD5:
8048bb94381a8409f1e152b1f9d2ed3b
SHA1:
a6e3fe879864165cd8ea696902cd1f4c2fb57137
SHA256:
30483602B9F632E1192985B58AA0E7F8EE2286DAEF6C35ABD13020779394E918
File Size:
1.47 MB, 1466688 bytes
|
|
MD5:
f351df6796ba968e79a8b66e76e3e1a7
SHA1:
48c301a649e49cc3022cef18f471f74e9fa3237f
SHA256:
0C9E772D8730204DD850797827745A27BDE599983D1EE070D0B61EA5FAEAF535
File Size:
647.37 KB, 647368 bytes
|
|
MD5:
eea70c7d057d2389cba091fe89e70270
SHA1:
f5c2038a96aae6758b6d95b091fba2ae4f20c8bd
SHA256:
FB8BDBA791F8C4DCD097785AC52105316BEA737360ACE0E5F78738286A190426
File Size:
675.26 KB, 675256 bytes
|
|
MD5:
0079349e533d6060bc6d731e0467ede7
SHA1:
c4f52c7603762413f46f8b5d42dfdd4f80f9ebb0
SHA256:
89B1B3C8CCDCA7046FE30361F1FD9E70BD501DAEA2A28988FFA028C3428C680B
File Size:
702.18 KB, 702176 bytes
|
|
MD5:
775d8202e41990a1e1f61b9342c5dcf4
SHA1:
d24094e6961b382c426cb4b149240daa554a3f77
SHA256:
9CEDC639B3247BEECB25B28B5F4A12E5586ED46DB140A5F1C09CA16F2781461B
File Size:
659.82 KB, 659824 bytes
|
Windows Portable Executable Attributes
- File doesn't have "Rich" header
- File has exports table
- File is 64-bit executable
- File is either console or GUI application
- File is GUI application (IMAGE_SUBSYSTEM_WINDOWS_GUI)
- File is Native application (NOT .NET application)
- File is not packed
- IMAGE_FILE_DLL is not set inside PE header (Executable)
- IMAGE_FILE_EXECUTABLE_IMAGE is set inside PE header (Executable Image)
File Icons
File Icons
This section displays icon resources found within family samples. Malware often replicates icons commonly associated with legitimate software to mislead users into believing the malware is safe.
Show More
14 additional icons are not displayed above.
Windows PE Version Information
Windows PE Version Information
This section displays values and attributes that have been set in the Windows file version information data structure for samples within this family. To mislead users, malware actors often add fake version information mimicking legitimate software.| Name | Value |
|---|---|
| Comments |
Show More
|
| Company Name |
Show More
|
| File Description |
Show More
|
| File Version |
Show More
|
| Internal Name |
Show More
|
| Legal Copyright |
Show More
|
| Legal Trademarks |
Show More
|
| Original Filename |
Show More
|
| Product Name |
Show More
|
| Product Version |
Show More
|
Digital Signatures
Digital Signatures
This section lists digital signatures that are attached to samples within this family. When analyzing and verifying digital signatures, it is important to confirm that the signature’s root authority is a well-known and trustworthy entity and that the status of the signature is good. Malware is often signed with non-trustworthy “Self Signed” digital signatures (which can be easily created by a malware author with no verification). Malware may also be signed by legitimate signatures that have an invalid status, and by signatures from questionable root authorities with fake or misleading “Signer” names.| Signer | Root | Status |
|---|---|---|
| Bahringer - Altenwerth | Bahringer - Altenwerth Intermediate CA 2 | Self Signed |
| Bergstrom - Toy | Bergstrom - Toy Intermediate CA 1 | Self Signed |
| Boehm - Stokes | Boehm - Stokes Intermediate CA 3 | Self Signed |
| Emard LLC | Emard LLC Intermediate CA 3 | Self Signed |
| Glover LLC | Glover LLC Intermediate CA 2 | Self Signed |
Show More
| Hahn Inc | Hahn Inc Intermediate CA 3 | Self Signed |
| Hodkiewicz and Sons | Hodkiewicz and Sons Intermediate CA 3 | Self Signed |
| King and Sons | King and Sons Intermediate CA 3 | Self Signed |
| Mueller LLC | Mueller LLC Intermediate CA 3 | Self Signed |
| Robel - Hilpert | Robel - Hilpert Intermediate CA 1 | Self Signed |
| Romaguera - Treutel | Romaguera - Treutel Intermediate CA 3 | Self Signed |
| Simonis and Sons | Simonis and Sons Intermediate CA 3 | Self Signed |
File Traits
- HighEntropy
- x64
Block Information
Block Information
During analysis, EnigmaSoft breaks file samples into logical blocks for classification and comparison with other samples. Blocks can be used to generate malware detection rules and to group file samples into families based on shared source code, functionality and other distinguishing attributes and characteristics. This section lists a summary of this block data, as well as its classification by EnigmaSoft. A visual representation of the block data is also displayed, where available.| Total Blocks: | 54 |
|---|---|
| Potentially Malicious Blocks: | 8 |
| Whitelisted Blocks: | 9 |
| Unknown Blocks: | 37 |
Visual Map
?
0
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
x
?
?
0
?
x
x
x
0
0
0
x
x
?
?
?
?
?
?
0
x
?
?
?
0
?
0
0
x
?
0 - Probable Safe Block
? - Unknown Block
x - Potentially Malicious Block
? - Unknown Block
x - Potentially Malicious Block
Similar Families
Similar Families
This section lists other families that share similarities with this family, based on EnigmaSoft’s analysis. Many malware families are created from the same malware toolkits and use the same packing and encryption techniques but uniquely extend functionality. Similar families may also share source code, attributes, icons, subcomponents, compromised and/or invalid digital signatures, and network characteristics. Researchers leverage these similarities to rapidly and effectively triage file samples and extend malware detection rules.Windows API Usage
Windows API Usage
This section lists Windows API calls that are used by the samples in this family. Windows API usage analysis is a valuable tool that can help identify malicious activity, such as keylogging, security privilege escalation, data encryption, data exfiltration, interference with antivirus software, and network request manipulation.| Category | API |
|---|---|
| Syscall Use |
|
