Windows
Analysis Report
XO4ioEY3nq.exe
Overview
General Information
Sample name: | XO4ioEY3nq.exerenamed because original name is a hash value |
Original sample name: | 73636685f823d103c54b30bc457c7f0d.exe |
Analysis ID: | 1627459 |
MD5: | 73636685f823d103c54b30bc457c7f0d |
SHA1: | 597dba03dce00cf6d30b082c80c8f9108ae90ccf |
SHA256: | 1edc123e5a8ea5ce814e2759ee38453404d4af72a3577b0af55e8d99fa38ef1c |
Tags: | exeuser-abuse_ch |
Infos: | |
Detection
Amadey, SystemBC
Score: | 100 |
Range: | 0 - 100 |
Confidence: | 100% |
Signatures
Antivirus detection for URL or domain
Detected unpacking (changes PE section rights)
Found malware configuration
Multi AV Scanner detection for dropped file
Multi AV Scanner detection for submitted file
Suricata IDS alerts for network traffic
Yara detected Amadey
Yara detected Amadeys Clipper DLL
Yara detected SystemBC
C2 URLs / IPs found in malware configuration
Contains functionality to inject code into remote processes
Contains functionality to start a terminal service
Hides threads from debuggers
Joe Sandbox ML detected suspicious sample
PE file contains section with special chars
Potentially malicious time measurement code found
Sample uses string decryption to hide its real strings
Tries to detect process monitoring tools (Task Manager, Process Explorer etc.)
Tries to detect sandboxes / dynamic malware analysis system (registry check)
Tries to detect sandboxes and other dynamic analysis tools (window names)
Tries to detect virtualization through RDTSC time measurements
Tries to evade debugger and weak emulator (self modifying code)
Abnormal high CPU Usage
Checks for debuggers (devices)
Checks if the current process is being debugged
Contains capabilities to detect virtual machines
Contains functionality for execution timing, often used to detect debuggers
Contains functionality to check if a debugger is running (IsDebuggerPresent)
Contains functionality to query CPU information (cpuid)
Contains functionality to query locales information (e.g. system language)
Contains functionality to read the PEB
Contains functionality to record screenshots
Contains functionality which may be used to detect a debugger (GetProcessHeap)
Contains long sleeps (>= 3 min)
Creates a process in suspended mode (likely to inject code)
Creates files inside the system directory
Creates job files (autostart)
Detected TCP or UDP traffic on non-standard ports
Detected non-DNS traffic on DNS port
Detected potential crypto function
Downloads executable code via HTTP
Drops PE files
Drops PE files to the application program directory (C:\ProgramData)
Entry point lies outside standard sections
Extensive use of GetProcAddress (often used to hide API calls)
Found a high number of Window / User specific system calls (may be a loop to detect user behavior)
Found large amount of non-executed APIs
Found potential string decryption / allocating functions
HTTP GET or POST without a user agent
IP address seen in connection with other malware
May sleep (evasive loops) to hinder dynamic analysis
PE / OLE file has an invalid certificate
PE file contains an invalid checksum
PE file contains sections with non-standard names
Queries the volume information (name, serial number etc) of a device
Sample execution stops while process was sleeping (likely an evasion)
Suricata IDS alerts with low severity for network traffic
Uses 32bit PE files
Uses code obfuscation techniques (call, push, ret)
Classification
- System is w10x64
XO4ioEY3nq.exe (PID: 6076 cmdline:
"C:\Users\ user\Deskt op\XO4ioEY 3nq.exe" MD5: 73636685F823D103C54B30BC457C7F0D) Gxtuum.exe (PID: 5552 cmdline:
"C:\Users\ user\AppDa ta\Local\T emp\a58456 755d\Gxtuu m.exe" MD5: 73636685F823D103C54B30BC457C7F0D) rundrive.exe (PID: 6176 cmdline:
"C:\Users\ user\AppDa ta\Roaming \100005501 00\rundriv e.exe" MD5: 9218E5CAD03C752F237ED87A9E52DEF4)
Gxtuum.exe (PID: 5560 cmdline:
C:\Users\u ser\AppDat a\Local\Te mp\a584567 55d\Gxtuum .exe MD5: 73636685F823D103C54B30BC457C7F0D)
eafkou.exe (PID: 6520 cmdline:
C:\Program Data\rcjuo \eafkou.ex e MD5: 9218E5CAD03C752F237ED87A9E52DEF4)
Gxtuum.exe (PID: 6500 cmdline:
C:\Users\u ser\AppDat a\Local\Te mp\a584567 55d\Gxtuum .exe MD5: 73636685F823D103C54B30BC457C7F0D)
Gxtuum.exe (PID: 2584 cmdline:
C:\Users\u ser\AppDat a\Local\Te mp\a584567 55d\Gxtuum .exe MD5: 73636685F823D103C54B30BC457C7F0D)
Gxtuum.exe (PID: 3688 cmdline:
C:\Users\u ser\AppDat a\Local\Te mp\a584567 55d\Gxtuum .exe MD5: 73636685F823D103C54B30BC457C7F0D)
Gxtuum.exe (PID: 3716 cmdline:
C:\Users\u ser\AppDat a\Local\Te mp\a584567 55d\Gxtuum .exe MD5: 73636685F823D103C54B30BC457C7F0D)
- cleanup
Name | Description | Attribution | Blogpost URLs | Link |
---|---|---|---|---|
Amadey | Amadey is a botnet that appeared around October 2018 and is being sold for about $500 on Russian-speaking hacking forums. It periodically sends information about the system and installed AV software to its C2 server and polls to receive orders from it. Its main functionality is that it can load other payloads (called "tasks") for all or specifically targeted computers compromised by the malware. | No Attribution |
Name | Description | Attribution | Blogpost URLs | Link |
---|---|---|---|---|
SystemBC | SystemBC is a proxy malware leveraging SOCKS5. Based on screenshots used in ads on a underground marketplace, Proofpoint decided to call it SystemBC.SystemBC has been observed occasionally, but more pronounced since June 2019. First samples goes back to October 2018. | No Attribution |
{"C2 url": "cobolrationumelawrtewarms.com/3ofn3jf3e2ljk/index.php", "Version": "5.21", "Install Folder": "a58456755d", "Install File": "Gxtuum.exe"}
{"HOST1": "towerbingobongoboom.com", "HOST2": "213.209.150.137"}
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_SystemBC | Yara detected SystemBC | Joe Security | ||
JoeSecurity_SystemBC | Yara detected SystemBC | Joe Security | ||
JoeSecurity_SystemBC | Yara detected SystemBC | Joe Security | ||
JoeSecurity_SystemBC | Yara detected SystemBC | Joe Security | ||
JoeSecurity_Amadey_4 | Yara detected Amadey | Joe Security |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security | ||
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security | ||
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security | ||
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security | ||
JoeSecurity_Amadey_3 | Yara detected Amadey\'s Clipper DLL | Joe Security | ||
Click to see the 9 entries |
⊘No Sigma rule has matched
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2025-03-02T13:15:16.934308+0100 | 2856147 | 1 | A Network Trojan was detected | 192.168.2.5 | 49704 | 107.189.27.66 | 80 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2025-03-02T13:15:19.077288+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 49705 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:15:38.193887+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 49758 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:15:42.592965+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 49790 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:15:46.951710+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61684 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:15:51.286074+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61716 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:15:55.810462+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61740 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:00.168902+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61772 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:04.690691+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61804 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:09.048275+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61834 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:13.379738+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61862 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:17.751981+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61864 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:22.141775+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61866 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:26.613810+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61868 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:30.967145+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61870 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:35.332293+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61872 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:39.700458+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61874 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:44.080935+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61876 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:48.456566+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61878 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:52.819517+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61880 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:16:57.271130+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61882 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:01.652078+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61884 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:06.065993+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61886 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:10.578393+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61888 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:15.002537+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61890 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:19.369440+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61892 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:23.752294+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61894 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:28.090740+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61896 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:32.486039+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61898 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:36.892451+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61900 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:41.275660+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61902 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:45.666257+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61904 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:50.019126+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61906 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:54.392231+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61908 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:17:58.791128+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61910 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:03.166543+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61912 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:07.616960+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61914 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:11.973686+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61916 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:16.382226+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61918 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:20.769244+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61920 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:25.135343+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61922 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:29.472363+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61924 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:34.165326+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61926 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:38.570650+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61928 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:42.948676+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61930 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:47.321810+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61932 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:51.750178+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61934 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:18:56.178261+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61936 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:19:00.654904+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61938 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:19:05.058313+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61940 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:19:09.457697+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61942 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:19:13.842864+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61944 | 107.189.27.66 | 80 | TCP |
2025-03-02T13:19:18.380076+0100 | 2856148 | 1 | A Network Trojan was detected | 192.168.2.5 | 61946 | 107.189.27.66 | 80 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2025-03-02T13:15:21.359962+0100 | 2803305 | 3 | Unknown Traffic | 192.168.2.5 | 49706 | 45.59.120.8 | 80 | TCP |
Click to jump to signature section
Show All Signature Results
AV Detection |
---|
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: |
Source: | Malware Configuration Extractor: | ||
Source: | Malware Configuration Extractor: |
Source: | ReversingLabs: |
Source: | Virustotal: | Perma Link | ||
Source: | ReversingLabs: |
Source: | Integrated Neural Analysis Model: |
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: | ||
Source: | String decryptor: |
Source: | Static PE information: |
Source: | Static PE information: |
Source: | Code function: | 0_2_000AF011 | |
Source: | Code function: | 1_2_0090F011 | |
Source: | Code function: | 2_2_0090F011 |
Networking |
---|
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: |
Source: | URLs: | ||
Source: | URLs: | ||
Source: | URLs: |
Source: | TCP traffic: |
Source: | TCP traffic: |
Source: | HTTP traffic detected: |