Edit tour
Windows
Analysis Report
VIP-#U4f1a#U5458#U7248.exe
Overview
General Information
Sample name: | VIP-#U4f1a#U5458#U7248.exerenamed because original name is a hash value |
Original sample name: | VIP-.exe |
Analysis ID: | 1569132 |
MD5: | 79e8c7fc08846104c300079e8f9cfff2 |
SHA1: | b9d9e952375e973d71a077973f6be03f6b9a1987 |
SHA256: | 0a1dc880d7c52be7311f2870481796bba315774f7c646876f88dc84837f3b4c0 |
Tags: | exefragtoruser-zhuzhu0009 |
Infos: | |
Detection
BlackMoon
Score: | 100 |
Range: | 0 - 100 |
Whitelisted: | false |
Confidence: | 100% |
Signatures
Antivirus / Scanner detection for submitted sample
Antivirus detection for dropped file
Malicious sample detected (through community Yara rule)
Multi AV Scanner detection for dropped file
Multi AV Scanner detection for submitted file
Yara detected BlackMoon Ransomware
AI detected suspicious sample
Allocates memory in foreign processes
Contains functionality to detect sleep reduction / modifications
Contains functionality to inject threads in other processes
Detected VMProtect packer
Found driver which could be used to inject code into processes
Injects a PE file into a foreign processes
Machine Learning detection for dropped file
Machine Learning detection for sample
Modifies the DNS server
Overwrites code with unconditional jumps - possibly settings hooks in foreign process
PE file has a writeable .text section
Sample is not signed and drops a device driver
Sample is protected by VMProtect
Tries to detect virtualization through RDTSC time measurements
Tries to evade debugger and weak emulator (self modifying code)
Uses known network protocols on non-standard ports
Writes to foreign memory regions
Abnormal high CPU Usage
Allocates memory with a write watch (potentially for evading sandboxes)
Allocates memory within range which is reserved for system DLLs (kernel32.dll, advapi32.dll, etc)
Contains functionality for execution timing, often used to detect debuggers
Contains functionality to call native functions
Contains functionality to check if a debugger is running (IsDebuggerPresent)
Contains functionality to check if a debugger is running (OutputDebugString,GetLastError)
Contains functionality to check if a window is minimized (may be used to check if an application is visible)
Contains functionality to communicate with device drivers
Contains functionality to dynamically determine API calls
Contains functionality to open a port and listen for incoming connection (possibly a backdoor)
Contains functionality to query locales information (e.g. system language)
Contains functionality to record screenshots
Contains functionality to retrieve information about pressed keystrokes
Contains functionality which may be used to detect a debugger (GetProcessHeap)
Creates a process in suspended mode (likely to inject code)
Creates driver files
Creates files inside the system directory
Creates or modifies windows services
Deletes Internet Explorer cookies via registry
Deletes files inside the Windows folder
Detected TCP or UDP traffic on non-standard ports
Detected potential crypto function
Dropped file seen in connection with other malware
Drops PE files
Drops PE files to the windows directory (C:\Windows)
Entry point lies outside standard sections
Found a high number of Window / User specific system calls (may be a loop to detect user behavior)
Found decision node followed by non-executed suspicious APIs
Found dropped PE file which has not been started or loaded
Found evasive API chain (date check)
Found evasive API chain (may stop execution after checking a module file name)
Found potential string decryption / allocating functions
IP address seen in connection with other malware
May check if the current machine is a sandbox (GetTickCount - Sleep)
May sleep (evasive loops) to hinder dynamic analysis
Modifies existing windows services
PE file contains executable resources (Code or Archives)
PE file contains more sections than normal
PE file contains sections with non-standard names
Potential key logger detected (key state polling based)
Queries disk information (often used to detect virtual machines)
Queries the volume information (name, serial number etc) of a device
Suricata IDS alerts with low severity for network traffic
Uses 32bit PE files
Uses Microsoft's Enhanced Cryptographic Provider
Uses a known web browser user agent for HTTP communication
Uses code obfuscation techniques (call, push, ret)
Yara signature match
Classification
- System is w10x64
- VIP-#U4f1a#U5458#U7248.exe (PID: 3788 cmdline:
"C:\Users\ user\Deskt op\VIP-#U4 f1a#U5458# U7248.exe" MD5: 79E8C7FC08846104C300079E8F9CFFF2) - D74384FB8D2C9.exe (PID: 5448 cmdline:
"C:\Progra m Files (x 86)\google \D74384FB8 D2C9.exe" WfCSiyl7KC mSL4J0fXwp klp7KYEqfR 6ShFd+QzmL 6nTfLzmL6+ rr5jmL5ejq 5jx7JntO MD5: 0D79B45E55C20F14D9614596247B7DF2)
- svchost.exe (PID: 744 cmdline:
C:\Windows \System32\ svchost.ex e -k netsv cs -p -s B ITS MD5: B7F884C1B74A263F746EE12A5F7C9F6A)
- cleanup
Name | Description | Attribution | Blogpost URLs | Link |
---|---|---|---|---|
KrBanker, BlackMoon | ThreatPost describes KRBanker (Blackmoon) as a banking Trojan designed to steal user credentials from various South Korean banking institutions. It was discovered in early 2014 and since then has adopted a variety of infection and credential stealing techniques. | No Attribution |
⊘No configs have been found
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_blackmoon | Yara detected BlackMoon Ransomware | Joe Security | ||
MALWARE_Win_BlackMoon | Detects executables using BlackMoon RunTime | ditekSHen |
| |
JoeSecurity_blackmoon | Yara detected BlackMoon Ransomware | Joe Security | ||
MALWARE_Win_BlackMoon | Detects executables using BlackMoon RunTime | ditekSHen |
|
System Summary |
---|
Source: | Author: frack113: |
Source: | Author: vburov: |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-12-05T14:25:19.638998+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49723 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:25:20.255035+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49721 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:25:31.983543+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49759 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:25:31.984552+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49761 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:25:32.084642+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49760 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:25:32.089093+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49758 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:25:40.148938+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49722 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:25:43.383580+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49730 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:25:46.334829+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49797 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:25:46.336136+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49796 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:25:46.960635+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49798 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:25:46.960886+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49799 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:02.165299+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49784 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:26:05.431002+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49792 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:26:22.302707+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49892 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:22.489188+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49846 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:26:22.489234+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49854 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:26:22.489252+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49893 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:32.332586+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49920 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:32.876493+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49921 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:39.492886+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49944 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:39.844409+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49943 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:46.521255+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49961 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:46.864753+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49962 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:53.027833+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49922 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:26:54.369878+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49985 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:55.637475+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49986 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:26:59.513848+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50002 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:26:59.906551+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50001 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:00.150774+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49942 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:01.395278+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 49987 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:01.395384+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50009 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:05.633759+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50014 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:07.295551+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50027 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:27:07.649580+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50026 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:09.941646+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50028 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:14.318476+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50047 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:27:14.664651+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50046 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:16.961981+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50048 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:21.254480+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50069 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:27:21.595844+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50068 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:23.910418+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50067 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:26.246010+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50083 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:27:26.661897+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50084 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:34.363435+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50090 | 119.29.29.29 | 80 | TCP |
2024-12-05T14:27:35.259924+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50089 | 182.254.116.116 | 80 | TCP |
2024-12-05T14:27:46.901575+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50082 | 114.114.114.114 | 80 | TCP |
2024-12-05T14:27:55.026580+0100 | 2803274 | 2 | Potentially Bad Traffic | 192.168.2.5 | 50088 | 114.114.114.114 | 80 | TCP |
Click to jump to signature section
Show All Signature Results
AV Detection |
---|
Source: | Avira: |
Source: | Avira: | ||
Source: | Avira: | ||
Source: | Avira: | ||
Source: | Avira: | ||
Source: | Avira: |
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: |
Source: | ReversingLabs: |
Source: | Integrated Neural Analysis Model: |
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: |
Source: | Joe Sandbox ML: |
Source: | Code function: | 2_2_6A6DB2B0 | |
Source: | Code function: | 2_2_6A6DB450 | |
Source: | Code function: | 2_2_6A6DB5E0 | |
Source: | Code function: | 2_2_6A6DB5C4 |
Source: | Static PE information: |
Source: | Static PE information: |
Source: | Binary string: |