PUP.MSIL.DllInject.WK
Table of Contents
Analysis Report
General information
| Family Name: | PUP.MSIL.DllInject.WK |
|---|---|
| Signature status: | Self Signed |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
927dd942cf5db4949163ed415fb8c03e
SHA1:
a3674ef114c32f869fcae4fd2dd61eab15157c69
SHA256:
0B4224919520E5EAF9E5F9D0EBEF212354A22C64D39D2B9C5A9E3BC95E94C9FF
File Size:
899.58 KB, 899584 bytes
|
|
MD5:
241e5ca05a00ea176be45149eecb60fe
SHA1:
5d5b11040c3142392312e9fb7555ccfcbb9d0960
SHA256:
C5089BDBAE908F2A251E71A22BEAE3E6784E51CA226D09C7F2023DD2837E33BD
File Size:
1.35 MB, 1349120 bytes
|
|
MD5:
8c9971457a5bdf85446121c64266666d
SHA1:
9a5c863933db2129286db3c61dbafa1e5b8fe063
SHA256:
E97DA92217E0BC1999680F162A27856FD070EF332F2D77E50E2837ED8A1A21FD
File Size:
33.19 KB, 33192 bytes
|
Windows Portable Executable Attributes
- File doesn't have "Rich" header
- File doesn't have exports table
- File doesn't have relocations information
- File doesn't have security information
- File is .NET application
- File is 32-bit executable
- File is 64-bit executable
- File is either console or GUI application
- File is GUI application (IMAGE_SUBSYSTEM_WINDOWS_GUI)
- File is not packed
Show More
- 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.
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 |
|
| Company Name | HP |
| File Description |
|
| File Version |
|
| Internal Name |
|
| Legal Copyright |
|
| Original Filename |
|
| Product Name |
|
| 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 |
|---|---|---|
| CHASE\chase | CHASE\chase | Self Signed |
File Traits
- .NET
- HighEntropy
- Pastebin
- 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: | 35 |
|---|---|
| Potentially Malicious Blocks: | 10 |
| Whitelisted Blocks: | 21 |
| Unknown Blocks: | 4 |
Visual Map
0
?
0
0
?
0
0
x
0
x
0
0
0
0
0
0
0
?
x
0
0
0
0
0
x
0
x
x
x
x
x
x
?
0
0
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.- MSIL.Agent.FDT
- MSIL.DllInject.WK
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 |
|
| Anti Debug |
|
