Edit tour
Windows
Analysis Report
file.exe
Overview
General Information
Detection
Nymaim, Socks5Systemz
Score: | 100 |
Range: | 0 - 100 |
Whitelisted: | false |
Confidence: | 100% |
Signatures
Antivirus / Scanner detection for submitted sample
Antivirus detection for URL or domain
Antivirus detection for dropped file
Detected unpacking (changes PE section rights)
Detected unpacking (overwrites its own PE header)
Found malware configuration
Malicious sample detected (through community Yara rule)
Multi AV Scanner detection for dropped file
Multi AV Scanner detection for submitted file
Suricata IDS alerts for network traffic
Yara detected Nymaim
Yara detected Socks5Systemz
AI detected suspicious sample
C2 URLs / IPs found in malware configuration
Contains functionality to infect the boot sector
Contains functionality to inject code into remote processes
Found API chain indicative of debugger detection
Injects a PE file into a foreign processes
Machine Learning detection for dropped file
Machine Learning detection for sample
Allocates memory with a write watch (potentially for evading sandboxes)
Binary contains a suspicious time stamp
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 launch a program with higher privileges
Contains functionality to open a port and listen for incoming connection (possibly a backdoor)
Contains functionality to query CPU information (cpuid)
Contains functionality to query locales information (e.g. system language)
Contains functionality to query network adapater information
Contains functionality to read the PEB
Contains functionality to shutdown / reboot the system
Contains functionality which may be used to detect a debugger (GetProcessHeap)
Contains long sleeps (>= 3 min)
Creates a DirectInput object (often for capturing keystrokes)
Creates a process in suspended mode (likely to inject code)
Detected TCP or UDP traffic on non-standard ports
Detected potential crypto function
Downloads executable code via HTTP
Dropped file seen in connection with other malware
Drops PE files
Drops PE files to the application program directory (C:\ProgramData)
Drops files with a non-matching file extension (content does not match file extension)
Entry point lies outside standard sections
Extensive use of GetProcAddress (often used to hide API calls)
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 large amount of non-executed APIs
Found potential string decryption / allocating functions
IP address seen in connection with other malware
Internet Provider seen in connection with other malware
May sleep (evasive loops) to hinder dynamic analysis
PE file contains executable resources (Code or Archives)
PE file contains more sections than normal
PE file contains sections with non-standard names
Queries disk information (often used to detect virtual machines)
Queries the volume information (name, serial number etc) of a device
Sample execution stops while process was sleeping (likely an evasion)
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
- file.exe (PID: 6508 cmdline:
"C:\Users\ user\Deskt op\file.ex e" MD5: 5237853DBEBAEFB1DFA86130DD1D39FA) - file.exe (PID: 6556 cmdline:
"C:\Users\ user\Deskt op\file.ex e" MD5: 5237853DBEBAEFB1DFA86130DD1D39FA) - NqISs1vOr.exe (PID: 6872 cmdline:
"C:\Users\ user\AppDa ta\Roaming \0L1IPDf6p \NqISs1vOr .exe" MD5: 98C5D582966DD7E46FF73E7D6D62B87D) - NqISs1vOr.tmp (PID: 6916 cmdline:
"C:\Users\ user\AppDa ta\Local\T emp\is-JSG 7N.tmp\NqI Ss1vOr.tmp " /SL5="$4 03E6,38174 17,54272,C :\Users\us er\AppData \Roaming\0 L1IPDf6p\N qISs1vOr.e xe" MD5: 62FDBBA6364B54BBE42B437284A2963C) - net.exe (PID: 7036 cmdline:
"C:\Window s\system32 \net.exe" pause alte r_game_111 96 MD5: 31890A7DE89936F922D44D677F681A7F) - conhost.exe (PID: 7076 cmdline:
C:\Windows \system32\ conhost.ex e 0xffffff ff -ForceV 1 MD5: 0D698AF330FD17BEE3BF90011D49251D) - net1.exe (PID: 980 cmdline:
C:\Windows \system32\ net1 pause alter_gam e_11196 MD5: 2EFE6ED4C294AB8A39EB59C80813FEC1) - altergame32.exe (PID: 2488 cmdline:
"C:\Users\ user\AppDa ta\Local\A lterGame 1 .13\alterg ame32.exe" -i MD5: C1DEEF6663EFF952E8990193B3452A2F) - ebAAb6KfuCx7.exe (PID: 3236 cmdline:
"C:\Users\ user\AppDa ta\Roaming \xMs8rtQRv 7K\ebAAb6K fuCx7.exe" MD5: F328A95046E3A2514C36347EAEC911C0)
- cleanup
Name | Description | Attribution | Blogpost URLs | Link |
---|---|---|---|---|
Nymaim | Nymaim is a trojan downloader. It downloads (and runs) other malware on affected systems and was one of the primary malware families hosted on Avalanche. Nymaim is different in that it displays a localized lockscreen while it downloads additional malware. Nymaim is usually delivered by exploit kits and malvertising. | No Attribution |
{"C2 list": ["boietuj.com"]}
{"C2 addresses": ["185.156.72.65", "185.156.72.65", "185.156.72.65", "185.156.72.65"]}
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_Socks5Systemz | Yara detected Socks5Systemz | Joe Security | ||
JoeSecurity_Nymaim | Yara detected Nymaim | Joe Security | ||
Windows_Trojan_RedLineStealer_ed346e4c | unknown | unknown |
| |
JoeSecurity_Socks5Systemz | Yara detected Socks5Systemz | Joe Security | ||
JoeSecurity_Socks5Systemz | Yara detected Socks5Systemz | Joe Security |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_Nymaim | Yara detected Nymaim | Joe Security |
⊘No Sigma rule has matched
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-20T05:03:19.330150+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:19.707958+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:22.679741+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:23.511115+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49885 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:24.349525+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49892 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:25.182992+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49898 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:26.013459+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49904 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:26.986222+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49910 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:27.814581+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49917 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:28.175922+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49917 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:29.003148+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49927 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:29.864671+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49933 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:30.897323+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49939 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:31.290583+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49939 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:32.129208+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49945 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:32.485151+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49945 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:33.323396+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49956 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:34.155422+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49962 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:35.150207+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49968 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:36.033281+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49974 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:36.989737+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:37.360947+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:37.716797+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:38.564118+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49991 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:38.925442+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49991 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:39.993516+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 49999 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:40.837006+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50004 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:41.685590+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50011 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:42.515663+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50017 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:43.344138+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50023 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:44.181802+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50028 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:45.014578+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50029 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:45.841220+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50030 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:46.665553+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50031 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:47.498201+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50032 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:48.354773+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50033 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:49.183437+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50034 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:50.006850+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50035 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:50.849542+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50036 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:51.338903+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50036 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.189569+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.550809+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.911402+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:53.274782+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.114938+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.469937+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.962762+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:55.796532+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50039 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:56.638762+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50040 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:57.469980+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50041 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:58.720031+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50042 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:59.578052+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50043 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:00.430705+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50044 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:01.290859+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50045 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:02.423851+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50046 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:02.792646+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50046 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:03.640276+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50047 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:04.467375+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50048 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:05.296380+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50049 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:06.232401+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50050 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:07.075224+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50051 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:07.930877+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50052 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:08.770839+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50053 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:09.241906+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50053 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:10.097218+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50054 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:10.465007+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50054 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:11.292434+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50055 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:13.148623+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50056 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:13.978186+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50057 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:14.830874+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50058 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:15.203927+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50058 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:16.029802+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50059 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:16.852260+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50060 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:17.704692+0100 | 2049467 | 1 | A Network Trojan was detected | 192.168.2.4 | 50061 | 185.208.158.202 | 80 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2024-11-20T05:03:19.330150+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:19.707958+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:22.679741+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49858 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:23.511115+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49885 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:24.349525+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49892 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:25.182992+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49898 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:26.013459+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49904 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:26.986222+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49910 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:27.814581+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49917 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:28.175922+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49917 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:29.003148+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49927 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:29.864671+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49933 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:30.897323+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49939 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:31.290583+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49939 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:32.129208+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49945 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:32.485151+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49945 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:33.323396+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49956 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:34.155422+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49962 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:35.150207+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49968 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:36.033281+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49974 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:36.989737+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:37.360947+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:37.716797+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49980 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:38.564118+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49991 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:38.925442+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49991 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:39.993516+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 49999 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:40.837006+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50004 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:41.685590+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50011 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:42.515663+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50017 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:43.344138+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50023 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:44.181802+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50028 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:45.014578+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50029 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:45.841220+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50030 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:46.665553+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50031 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:47.498201+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50032 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:48.354773+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50033 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:49.183437+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50034 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:50.006850+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50035 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:50.849542+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50036 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:51.338903+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50036 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.189569+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.550809+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:52.911402+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:53.274782+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50037 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.114938+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.469937+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:54.962762+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50038 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:55.796532+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50039 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:56.638762+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50040 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:57.469980+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50041 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:58.720031+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50042 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:03:59.578052+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50043 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:00.430705+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50044 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:01.290859+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50045 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:02.423851+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50046 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:02.792646+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50046 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:03.640276+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50047 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:04.467375+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50048 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:05.296380+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50049 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:06.232401+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50050 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:07.075224+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50051 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:07.930877+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50052 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:08.770839+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50053 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:09.241906+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50053 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:10.097218+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50054 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:10.465007+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50054 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:11.292434+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50055 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:13.148623+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50056 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:13.978186+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50057 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:14.830874+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50058 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:15.203927+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50058 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:16.029802+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50059 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:16.852260+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50060 | 185.208.158.202 | 80 | TCP |
2024-11-20T05:04:17.704692+0100 | 2050112 | 1 | A Network Trojan was detected | 192.168.2.4 | 50061 | 185.208.158.202 | 80 | TCP |
Click to jump to signature section
Show All Signature Results
AV Detection |
---|
Source: | Avira: |
Source: | Avira URL Cloud: | ||
Source: | Avira URL Cloud: |
Source: | Avira: |
Source: | Malware Configuration Extractor: | ||
Source: | Malware Configuration Extractor: |
Source: | ReversingLabs: | ||
Source: | ReversingLabs: |
Source: | ReversingLabs: | |||
Source: | Virustotal: | Perma Link |
Source: | Integrated Neural Analysis Model: |
Source: | Joe Sandbox ML: | ||
Source: | Joe Sandbox ML: |
Source: | Joe Sandbox ML: |
Source: | Code function: | 3_2_0045CFA8 | |
Source: | Code function: | 3_2_0045D05C | |
Source: | Code function: | 3_2_0045D074 | |
Source: | Code function: | 3_2_10001000 | |
Source: | Code function: | 3_2_10001130 |
Compliance |
---|
Source: | Unpacked PE file: |
Source: | Static PE information: |
Source: | Registry value created: | Jump to behavior |
Source: | Binary string: | ||
Source: | Binary string: | ||
Source: | Binary string: | ||
Source: | Binary string: | ||
Source: | Binary string: | ||
Source: | Binary string: |
Source: | Code function: | 3_2_00452A34 | |
Source: | Code function: | 3_2_00474D70 | |
Source: | Code function: | 3_2_00462578 | |
Source: | Code function: | 3_2_004975B0 | |
Source: | Code function: | 3_2_00463B04 | |
Source: | Code function: | 3_2_00463F80 |
Source: | Code function: | 0_2_00404250 |
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: | 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: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: | ||
Source: | Suricata IDS: |
Source: | URLs: | ||
Source: | IPs: | ||
Source: | IPs: | ||
Source: | IPs: | ||
Source: | IPs: |
Source: | TCP traffic: |
Source: | HTTP traffic detected: |