Summary

1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e

File 1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e

Summary
Download Resubmit sample

Size 2.0MB
Type PE32 executable (GUI) Intel 80386, for MS Windows
MD5 d8227401eb022ad2b622fd37427b9425
SHA1 0e205b4ac0e163bffcb4a0fde6776dbaffd3a982
SHA256 1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e
SHA512
65ce2bf21a34eed6288aa7f80bdb26436c99c84a38eea5de0dcf0f96751217318370664c88a306b7fac31fe2ee1323a1daab9a801dcb68f443e0da3aeee1a35d
CRC32 7195A8FF
ssdeep None
Yara
  • vmdetect - Possibly employs anti-virtualization techniques
  • anti_dbgtools - Checks for the presence of known debug tools

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.

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 April 12, 2025, 6:49 p.m. April 12, 2025, 6:56 p.m. 448 seconds internet Show Analyzer Log
Show Cuckoo Log

Analyzer Log

2025-04-11 01:31:04,015 [analyzer] DEBUG: Starting analyzer from: C:\tmpdyrg_l
2025-04-11 01:31:04,015 [analyzer] DEBUG: Pipe server name: \??\PIPE\wOSawCiPXMMXHWwGlSkOyNLyblxbtjhC
2025-04-11 01:31:04,015 [analyzer] DEBUG: Log pipe server name: \??\PIPE\hJYCoGQeDltcTraciluxkEeX
2025-04-11 01:31:04,312 [analyzer] DEBUG: Started auxiliary module Curtain
2025-04-11 01:31:04,312 [analyzer] DEBUG: Started auxiliary module DbgView
2025-04-11 01:31:04,875 [analyzer] DEBUG: Started auxiliary module Disguise
2025-04-11 01:31:05,092 [analyzer] DEBUG: Loaded monitor into process with pid 500
2025-04-11 01:31:05,092 [analyzer] DEBUG: Started auxiliary module DumpTLSMasterSecrets
2025-04-11 01:31:05,092 [analyzer] DEBUG: Started auxiliary module Human
2025-04-11 01:31:05,092 [analyzer] DEBUG: Started auxiliary module InstallCertificate
2025-04-11 01:31:05,108 [analyzer] DEBUG: Started auxiliary module Reboot
2025-04-11 01:31:05,187 [analyzer] DEBUG: Started auxiliary module RecentFiles
2025-04-11 01:31:05,187 [analyzer] DEBUG: Started auxiliary module Screenshots
2025-04-11 01:31:05,187 [analyzer] DEBUG: Started auxiliary module Sysmon
2025-04-11 01:31:05,187 [analyzer] DEBUG: Started auxiliary module LoadZer0m0n
2025-04-11 01:31:05,312 [lib.api.process] ERROR: Failed to execute process from path u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e.exe' with arguments ['bin\\inject-x86.exe', '--app', u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e.exe', '--only-start', '--curdir', 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp'] (Error: Command '['bin\\inject-x86.exe', '--app', u'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\1e4ae6ed6747c22be2867dde1a0f06b70cd1539ec5c1c50717028343042d539e.exe', '--only-start', '--curdir', 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp']' returned non-zero exit status 1)

Cuckoo Log

2025-04-12 18:49:31,606 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:32,632 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:33,652 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:34,679 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:35,851 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:36,901 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:37,937 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:38,998 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:40,044 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:41,082 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:42,119 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:43,165 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:44,216 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:45,257 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:46,404 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:47,536 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:48,570 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:49,603 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:50,642 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:51,798 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:52,833 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:53,955 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:54,991 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:56,029 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:57,071 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:58,110 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:49:59,136 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:00,188 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:01,232 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:02,273 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:03,308 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:04,343 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:05,383 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:06,414 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:07,456 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:08,494 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:09,609 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:10,641 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:11,677 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:12,710 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:13,745 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:14,778 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:15,816 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:16,848 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:17,878 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:18,913 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:19,945 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:20,987 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:22,019 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:23,048 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:24,078 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:25,158 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:26,229 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:27,301 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:28,352 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:29,396 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:31,232 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:32,629 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:33,812 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:35,060 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:36,464 [cuckoo.core.scheduler] DEBUG: Task #6268164: no machine available yet
2025-04-12 18:50:37,956 [cuckoo.core.scheduler] INFO: Task #6268164: acquired machine win7x6430 (label=win7x6430)
2025-04-12 18:50:37,975 [cuckoo.core.resultserver] DEBUG: Now tracking machine 192.168.168.230 for task #6268164
2025-04-12 18:50:38,380 [cuckoo.auxiliary.sniffer] INFO: Started sniffer with PID 1643414 (interface=vboxnet0, host=192.168.168.230)
2025-04-12 18:50:48,757 [cuckoo.machinery.virtualbox] DEBUG: Starting vm win7x6430
2025-04-12 18:50:49,356 [cuckoo.machinery.virtualbox] DEBUG: Restoring virtual machine win7x6430 to vmcloak
2025-04-12 18:53:25,490 [cuckoo.core.guest] INFO: Starting analysis #6268164 on guest (id=win7x6430, ip=192.168.168.230)
2025-04-12 18:53:26,497 [cuckoo.core.guest] DEBUG: win7x6430: not ready yet
2025-04-12 18:53:31,531 [cuckoo.core.guest] INFO: Guest is running Cuckoo Agent 0.10 (id=win7x6430, ip=192.168.168.230)
2025-04-12 18:53:31,969 [cuckoo.core.guest] DEBUG: Uploading analyzer to guest (id=win7x6430, ip=192.168.168.230, monitor=latest, size=6660546)
2025-04-12 18:53:33,651 [cuckoo.core.resultserver] DEBUG: Task #6268164: live log analysis.log initialized.
2025-04-12 18:53:34,688 [cuckoo.core.resultserver] DEBUG: Task #6268164 is sending a BSON stream
2025-04-12 18:53:35,977 [cuckoo.core.resultserver] DEBUG: Task #6268164: File upload for 'shots/0001.jpg'
2025-04-12 18:53:36,002 [cuckoo.core.resultserver] DEBUG: Task #6268164 uploaded file length: 133455
2025-04-12 18:53:36,173 [cuckoo.core.guest] WARNING: win7x6430: analysis #6268164 caught an exception
Traceback (most recent call last):
  File "C:/tmpdyrg_l/analyzer.py", line 824, in <module>
    success = analyzer.run()
  File "C:/tmpdyrg_l/analyzer.py", line 673, in run
    pids = self.package.start(self.target)
  File "C:\tmpdyrg_l\modules\packages\exe.py", line 34, in start
    return self.execute(path, args=shlex.split(args))
  File "C:\tmpdyrg_l\lib\common\abstracts.py", line 205, in execute
    "Unable to execute the initial process, analysis aborted."
CuckooPackageError: Unable to execute the initial process, analysis aborted.

2025-04-12 18:53:36,184 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Redsocks
2025-04-12 18:53:36,215 [cuckoo.core.plugins] DEBUG: Stopped auxiliary module: Sniffer
2025-04-12 18:53:37,101 [cuckoo.machinery.virtualbox] INFO: Successfully generated memory dump for virtual machine with label win7x6430 to path /srv/cuckoo/cwd/storage/analyses/6268164/memory.dmp
2025-04-12 18:53:37,102 [cuckoo.machinery.virtualbox] DEBUG: Stopping vm win7x6430
2025-04-12 18:56:41,888 [cuckoo.core.resultserver] DEBUG: Stopped tracking machine 192.168.168.230 for task #6268164
2025-04-12 18:56:41,892 [cuckoo.core.resultserver] DEBUG: Cancel <Context for LOG> for task 6268164
2025-04-12 18:56:46,110 [cuckoo.core.scheduler] DEBUG: Released database task #6268164
2025-04-12 18:56:49,705 [cuckoo.core.scheduler] INFO: Task #6268164: analysis procedure completed

Signatures

Yara rules detected for file (2 events)
description Possibly employs anti-virtualization techniques rule vmdetect
description Checks for the presence of known debug tools rule anti_dbgtools
The executable contains unknown PE section names indicative of a packer (could be a false positive) (6 events)
section \x00
section .idata
section
section mughqkns
section mxuodipd
section .taggant
File has been identified by at least one AntiVirus engine on IRMA as malicious (1 event)
Avast Core Security (Linux) Win32:MalwareX-gen [Misc]
File has been identified by 29 AntiVirus engines on VirusTotal as malicious (29 events)
Lionic Trojan.Win32.LummaStealer.4!c
tehtris Generic.Malware
Skyhigh BehavesLike.Win32.Generic.tm
Cylance Unsafe
CrowdStrike win/malicious_confidence_100% (W)
K7GW Riskware ( 00584baa1 )
K7AntiVirus Riskware ( 00584baa1 )
Elastic malicious (high confidence)
APEX Malicious
Avast FileRepMalware [Misc]
Rising Trojan.LummaStealer!8.17CC6 (TFE:4:zPmeQf0lK3S)
McAfeeD Real Protect-LS!D8227401EB02
Trapmine malicious.high.ml.score
CTX exe.trojan.lummastealer
Sophos Generic ML PUA (PUA)
SentinelOne Static AI - Malicious PE
Google Detected
Antiy-AVL Trojan/Win32.LummaStealer
Kingsoft malware.kb.a.871
Microsoft Trojan:Win32/LummaStealer.DM!MTB
GData Win32.Trojan-Stealer.LummaStealer.YMZFSO
AhnLab-V3 Trojan/Win.LummaStealer.C5750503
McAfee Artemis!D8227401EB02
DeepInstinct MALICIOUS
Malwarebytes Malware.AI.2835294281
Ikarus Trojan-Spy.Win32.LummaStealer
Zoner Probably Heur.ExeHeaderL
TrendMicro-HouseCall TROJ_GEN.R002H01DA25
AVG FileRepMalware [Misc]
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.