Trojan.MSIL.Agent.DFBT
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: | 5,886 |
| Threat Level: | 80 % (High) |
| Infected Computers: | 55 |
| First Seen: | September 4, 2024 |
| Last Seen: | April 1, 2026 |
| OS(es) Affected: | Windows |
Table of Contents
Analysis Report
General information
| Family Name: | Trojan.MSIL.Agent.DFBT |
|---|---|
| Signature status: | No Signature |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
81d51adc1067e977b29d461075091b2f
SHA1:
744e71bcf0e7187ce947f0088b108b47a8a09d6a
SHA256:
33B83A32E17806140E2E99397974D210DB7C94560F8803F73B97BF5FEF98D6D5
File Size:
8.28 MB, 8282984 bytes
|
|
MD5:
f679ae28d32f3bb14c8cb5020725e9a5
SHA1:
0befd07485a56738436e9ad934019d0f8c0fbfa1
SHA256:
5C14003550212647545BCB85B4216F2724AAEC5955053E2B1292378D80B691A2
File Size:
356.35 KB, 356352 bytes
|
|
MD5:
2975494480b7b60382400bc88405db93
SHA1:
6ca6695028837e8719416e690b7e67125071236c
SHA256:
B2CD625F472B59C1E340FED80291A7BC7E24C42088A7E1D544B3C6D597CA2B9E
File Size:
356.35 KB, 356352 bytes
|
|
MD5:
bd1647fad75490031a8dae1a74118f9c
SHA1:
c4f3eeda32d983dfe13e5c9365c7494086f78668
SHA256:
328E9D4BD8B41DA5A82744EE197FCA16207AEACC2E5F78595B0A1620F486FD3A
File Size:
356.35 KB, 356352 bytes
|
|
MD5:
fe51eec5ec596cfc31fb4b3dc37a441f
SHA1:
c588cb2f2522d57958c327a98d3d40a03546b882
SHA256:
2595333E4294FB73CA5AA5DCE8DD672E941712EF6690966569102E8E0451FFA9
File Size:
356.35 KB, 356352 bytes
|
Windows Portable Executable Attributes
- File doesn't have "Rich" header
- File doesn't have debug information
- File doesn't have exports table
- File doesn't have security information
- File has exports table
- File is .NET application
- File is 32-bit executable
- File is 64-bit executable
- File is console application (IMAGE_SUBSYSTEM_WINDOWS_CUI)
- File is either console or GUI application
Show More
- File is GUI application (IMAGE_SUBSYSTEM_WINDOWS_GUI)
- 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)
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 |
|---|---|
| Assembly Version |
|
| File Version |
|
| Internal Name |
|
| Original Filename |
|
| Product Version |
|
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 |
|---|---|---|
| Valve Corp. | DigiCert Trusted Root G4 | Hash Mismatch |
File Traits
- .NET
- dll
- ntdll
- RijndaelManaged
- Run
- x64
- x86
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: | 762 |
|---|---|
| Potentially Malicious Blocks: | 312 |
| Whitelisted Blocks: | 371 |
| Unknown Blocks: | 79 |
Visual Map
?
x
x
x
?
x
0
0
0
x
x
?
x
x
x
x
x
x
0
x
0
0
0
x
x
0
x
x
0
0
0
0
x
0
0
?
0
0
0
0
0
x
x
x
0
0
0
x
x
x
0
0
0
0
x
0
0
0
x
x
x
x
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
x
x
0
0
x
x
0
0
x
0
x
0
0
x
x
x
0
0
0
0
0
0
0
0
0
0
x
x
x
0
x
x
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
x
0
0
0
0
0
0
0
x
x
x
x
0
0
x
x
x
0
0
0
x
0
x
x
x
0
x
x
x
0
x
x
0
0
?
?
x
?
0
x
x
x
x
x
0
0
x
0
x
0
x
0
0
?
x
x
?
x
?
x
x
x
x
x
x
x
x
0
0
x
x
x
x
0
x
x
x
0
0
0
?
?
?
?
x
x
x
x
x
0
x
x
x
x
x
x
x
x
x
x
?
?
?
?
0
0
x
x
?
?
x
x
x
x
x
?
?
?
0
?
x
x
0
x
0
0
0
0
0
x
x
0
0
0
0
0
0
x
x
0
0
0
0
0
0
x
x
x
x
x
?
0
?
?
x
?
?
?
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
x
x
x
x
0
x
x
x
x
0
0
x
x
0
0
0
x
0
0
0
0
x
0
0
x
x
x
x
0
x
x
0
x
0
x
0
0
0
0
x
0
x
x
0
0
x
x
x
0
0
0
0
0
x
0
0
0
0
0
x
0
x
x
?
?
?
x
x
x
x
?
x
0
x
0
x
x
x
x
0
0
x
0
x
0
0
0
x
0
x
x
x
x
x
0
x
x
0
0
0
0
x
0
x
x
0
x
x
0
x
x
x
0
x
0
0
0
0
0
x
x
x
x
x
0
x
?
x
x
x
0
0
0
0
0
0
x
0
x
x
x
x
x
0
0
0
x
0
x
x
0
0
0
x
0
x
x
x
x
x
0
x
0
0
0
0
x
0
x
0
x
0
x
x
0
0
x
0
0
0
x
x
x
0
0
0
0
x
?
?
?
?
x
x
0
x
0
x
x
x
x
x
0
?
?
?
x
x
x
x
0
x
x
?
x
x
x
0
x
x
x
x
x
?
x
x
x
x
0
x
x
0
0
x
x
x
x
x
x
x
x
x
x
x
x
0
x
x
?
0
x
x
0
x
x
?
?
?
0
x
?
?
?
?
?
?
?
?
?
x
x
x
x
x
?
?
?
?
0
?
x
?
?
x
?
?
x
?
?
?
x
x
0
?
?
?
?
?
?
x
x
x
?
x
0
x
0
x
0
x
?
0
x
0
0
?
x
?
0
0
0
0
0
0
x
x
0
x
x
0
0
x
0
x
x
0
0
x
0
0
0
x
0
0
0
0
0
0
0
0
0
0
0
0
x
x
0
x
x
0
0
0
0
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
0
x
0
0
0
x
0
0
0
0
0
0
0
0
0 - Probable Safe Block
? - Unknown Block
x - Potentially Malicious Block
? - Unknown Block
x - Potentially Malicious Block
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 |
Show More
|
| User Data Access |
|
| Encryption Used |
|
