Windows
Analysis Report
file.exe
Overview
General Information
Detection
DarkVision Rat
Score: | 100 |
Range: | 0 - 100 |
Confidence: | 100% |
Signatures
Antivirus / Scanner detection for submitted sample
Antivirus detection for URL or domain
Antivirus detection for dropped file
Benign windows process drops PE files
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 DarkVision Rat
Yara detected UAC Bypass using CMSTP
Adds a directory exclusion to Windows Defender
C2 URLs / IPs found in malware configuration
Creates HTML files with .exe extension (expired dropper behavior)
Creates autostart registry keys with suspicious names
Deletes itself after installation
Found direct / indirect Syscall (likely to bypass EDR)
Joe Sandbox ML detected suspicious sample
Loading BitLocker PowerShell Module
Maps a DLL or memory area into another process
Query firmware table information (likely to detect VMs)
Sample is not signed and drops a device driver
Searches for specific processes (likely to inject)
Sigma detected: Files With System Process Name In Unsuspected Locations
Sigma detected: Powershell Base64 Encoded MpPreference Cmdlet
Sigma detected: Windows Binaries Write Suspicious Extensions
Switches to a custom stack to bypass stack traces
Tries to evade analysis by execution special instruction (VM detection)
Contains functionality to call native functions
Contains functionality to check if a debugger is running (IsDebuggerPresent)
Contains functionality to check the parent process ID (often done to detect debuggers and analysis systems)
Contains functionality to dynamically determine API calls
Contains functionality to launch a program with higher privileges
Contains functionality to load drivers
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 retrieve information about pressed keystrokes
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 driver files
Creates files inside the system directory
Creates or modifies windows services
Deletes files inside the Windows folder
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 PE files to the windows directory (C:\Windows)
Enables debug privileges
Enables driver privileges
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 dropped PE file which has not been started or loaded
Found evaded block containing many API calls
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
JA3 SSL client fingerprint seen in connection with other malware
May sleep (evasive loops) to hinder dynamic analysis
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)
Sample file is different than original file name gathered from version info
Sigma detected: CurrentVersion Autorun Keys Modification
Sigma detected: Powershell Defender Exclusion
Sigma detected: Suspicious Execution From GUID Like Folder Names
Sigma detected: Uncommon Svchost Parent Process
Spawns drivers
Stores large binary data to the registry
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
file.exe (PID: 6884 cmdline:
"C:\Users\ user\Deskt op\file.ex e" MD5: EB880B186BE6092A0DC71D001C2A6C73) cmd.exe (PID: 7152 cmdline:
cmd.exe /c powershel l.exe Add- MpPreferen ce -Exclus ionPath 'C :' MD5: 8A2122E8162DBEF04694B9C3E0B6CDEE) conhost.exe (PID: 7160 cmdline:
C:\Windows \system32\ conhost.ex e 0xffffff ff -ForceV 1 MD5: 0D698AF330FD17BEE3BF90011D49251D) powershell.exe (PID: 6416 cmdline:
powershell .exe Add-M pPreferenc e -Exclusi onPath 'C: ' MD5: 04029E121A0CFA5991749937DD22A1D9) svchost.exe (PID: 6440 cmdline:
"C:\Window s\system32 \svchost.e xe" MD5: B7F884C1B74A263F746EE12A5F7C9F6A) tzutil.exe (PID: 6076 cmdline:
"C:\Progra mData\{425 F784E-921A -4CC0-AE87 -06A3B0393 A0E}\tzuti l.exe" "" MD5: ACB40D712D1158CDE87A02CB4F16B4D4) powershell.exe (PID: 3348 cmdline:
powershell Add-MpPre ference -E xclusionPa th C:\ MD5: 04029E121A0CFA5991749937DD22A1D9) conhost.exe (PID: 6332 cmdline:
C:\Windows \system32\ conhost.ex e 0xffffff ff -ForceV 1 MD5: 0D698AF330FD17BEE3BF90011D49251D) powershell.exe (PID: 2876 cmdline:
powershell Remove-Mp Preference -Exclusio nPath C:\ MD5: 04029E121A0CFA5991749937DD22A1D9) conhost.exe (PID: 3984 cmdline:
C:\Windows \system32\ conhost.ex e 0xffffff ff -ForceV 1 MD5: 0D698AF330FD17BEE3BF90011D49251D) cmd.exe (PID: 7008 cmdline:
C:\Windows \system32\ cmd.exe /c ""C:\User s\user\App Data\Local \Temp\{425 F784E-921A -4CC0-AE87 -06A3B0393 A0E}\set.b at" """ MD5: 8A2122E8162DBEF04694B9C3E0B6CDEE) conhost.exe (PID: 6944 cmdline:
C:\Windows \system32\ conhost.ex e 0xffffff ff -ForceV 1 MD5: 0D698AF330FD17BEE3BF90011D49251D) w32tm.exe (PID: 1232 cmdline:
"C:\Users\ user\AppDa ta\Local\T emp\\{425F 784E-921A- 4CC0-AE87- 06A3B0393A 0E}\w32tm. exe" "" MD5: 15BDC4BD67925EF33B926843B3B8154B)
svchost.exe (PID: 7116 cmdline:
C:\Windows \System32\ svchost.ex e -k netsv cs -p -s B ITS MD5: B7F884C1B74A263F746EE12A5F7C9F6A)
- cleanup
{"C2": "82.29.67.160", "Port": 443}
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_DarkVisionRat | Yara detected DarkVision Rat | Joe Security | ||
JoeSecurity_UACBypassusingCMSTP | Yara detected UAC Bypass using CMSTP | Joe Security | ||
JoeSecurity_DarkVisionRat | Yara detected DarkVision Rat | Joe Security | ||
JoeSecurity_UACBypassusingCMSTP | Yara detected UAC Bypass using CMSTP | Joe Security | ||
JoeSecurity_DarkVisionRat | Yara detected DarkVision Rat | Joe Security | ||
Click to see the 5 entries |
Source | Rule | Description | Author | Strings |
---|---|---|---|---|
JoeSecurity_DarkVisionRat | Yara detected DarkVision Rat | Joe Security | ||
JoeSecurity_UACBypassusingCMSTP | Yara detected UAC Bypass using CMSTP | Joe Security | ||
INDICATOR_SUSPICIOUS_EXE_UACBypass_CMSTPCOM | Detects Windows exceutables bypassing UAC using CMSTP COM interfaces. MITRE (T1218.003) | ditekSHen |
| |
JoeSecurity_DarkVisionRat | Yara detected DarkVision Rat | Joe Security | ||
JoeSecurity_UACBypassusingCMSTP | Yara detected UAC Bypass using CMSTP | Joe Security | ||
Click to see the 6 entries |
System Summary |
---|
Source: | Author: Sander Wiebing, Tim Shelton, Nasreddine Bencherchali (Nextron Systems): |
Source: | Author: Florian Roth (Nextron Systems): |
Source: | Author: Nasreddine Bencherchali (Nextron Systems): |
Source: | Author: Victor Sergeev, Daniil Yugoslavskiy, Gleb Sukhodolskiy, Timur Zinniatullin, oscd.community, Tim Shelton, frack113 (split): |
Source: | Author: Florian Roth (Nextron Systems): |
Source: | Author: Nasreddine Bencherchali (Nextron Systems): |
Source: | Author: Florian Roth (Nextron Systems): |
Source: | Author: Roberto Rodriguez @Cyb3rWard0g (rule), oscd.community (improvements): |
Source: | Author: vburov: |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2025-03-26T14:17:51.942125+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.8 | 49685 | 104.26.8.202 | 443 | TCP |
2025-03-26T14:17:54.670747+0100 | 2028371 | 3 | Unknown Traffic | 192.168.2.8 | 49687 | 104.26.8.202 | 443 | TCP |
Timestamp | SID | Severity | Classtype | Source IP | Source Port | Destination IP | Destination Port | Protocol |
---|---|---|---|---|---|---|---|---|
2025-03-26T14:17:49.692671+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49684 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:17:53.695849+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49686 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:17:57.726000+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49693 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:01.752574+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49721 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:05.768042+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49742 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:09.788436+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49773 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:13.823709+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49777 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:17.862626+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49780 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:21.866625+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49781 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:25.905975+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49782 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:29.929133+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49783 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:33.961100+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49784 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:37.679416+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49786 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:41.117301+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49787 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:44.321750+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49788 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:47.319923+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49789 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:50.116689+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49790 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:52.731584+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49791 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:55.164607+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49792 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:57.476250+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49793 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:18:59.663449+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49794 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:01.710495+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49795 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:03.679744+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49796 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:05.554239+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49797 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:07.319963+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49798 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:09.022951+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49799 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:10.663661+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49800 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:12.242498+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49801 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:13.758661+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49802 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:15.226182+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49803 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:16.633324+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49804 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:18.007274+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49805 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:19.351559+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49806 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:20.663886+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49807 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:21.945870+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49808 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:23.195083+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49809 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:24.462194+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49810 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:25.663423+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49811 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:26.851732+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49812 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:28.038641+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49813 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:29.210522+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49814 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:30.474126+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49815 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:31.585981+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49816 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:32.710687+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49817 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:33.835620+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49818 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:34.945191+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49819 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:36.036777+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49820 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:37.101406+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49821 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:38.163688+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49822 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:39.278678+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49823 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:40.351191+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49824 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:41.414012+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49825 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:42.476082+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49826 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:43.538705+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49827 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:44.585717+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49828 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:45.616930+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49829 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:46.648894+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49830 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:47.679076+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49831 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:48.726979+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49832 | 82.29.67.160 | 443 | TCP |
2025-03-26T14:19:49.773059+0100 | 2045618 | 1 | A Network Trojan was detected | 192.168.2.8 | 49833 | 82.29.67.160 | 443 | TCP |
Click to jump to signature section
Show All Signature Results
AV Detection |
---|
Source: | Avira: |
Source: | Avira URL Cloud: |
Source: | Avira: |
Source: | Malware Configuration Extractor: |
Source: | ReversingLabs: | ||
Source: | ReversingLabs: | ||
Source: | ReversingLabs: |
Source: | Virustotal: | Perma Link | ||
Source: | ReversingLabs: |
Source: | Neural Call Log Analysis: |
Source: | Code function: | 0_2_0040516A | |
Source: | Code function: | 0_2_0041CFE0 | |
Source: | Code function: | 5_2_0000024DE6F8DD8F | |
Source: | Code function: | 5_2_0000024DE6F8DD5A | |
Source: | Code function: | 5_2_0000024DE6F8DD1E | |
Source: | Code function: | 5_2_0000024DE6F8DCF7 | |
Source: | Code function: | 5_2_0000024DE6F8DC00 | |
Source: | Code function: | 5_2_0000024DE6F753B0 | |
Source: | Code function: | 9_2_008582FC | |
Source: | Code function: | 9_2_0089F018 | |
Source: | Code function: | 9_2_0089F028 | |
Source: | Code function: | 9_2_0089F078 | |
Source: | Code function: | 9_2_008471E8 | |
Source: | Code function: | 9_2_008471EA | |
Source: | Code function: | 9_2_00847244 | |
Source: | Code function: | 9_2_0084E4C4 | |
Source: | Code function: | 9_2_00858478 | |
Source: | Code function: | 9_2_0084E510 |
Source: | Code function: | 9_2_0085F214 | |
Source: | Code function: | 9_2_00833268 | |
Source: | Binary or memory string: |
Exploits |
---|
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: | ||
Source: | File source: |
Source: | Static PE information: |
Source: | HTTPS traffic detected: |
Source: | Binary string: | ||
Source: | Binary string: | ||
Source: | Binary string: |
Source: | Code function: | 0_2_00410AA0 | |
Source: | Code function: | 5_2_0000024DE6F797F0 | |
Source: | Code function: | 9_2_008735CC | |
Source: | Code function: | 9_2_00891C54 |
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: | IPs: |
Source: | File created: |
Source: | HTTP traffic detected: |