Analysis
-
max time kernel
43s -
max time network
46s -
platform
windows7_x64 -
resource
win7-20220812-en -
resource tags
arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system -
submitted
02/12/2022, 23:51
Behavioral task
behavioral1
Sample
92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe
Resource
win10v2004-20221111-en
General
-
Target
92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe
-
Size
608KB
-
MD5
c07c35d459dbe4fd2e6e230e9a9b8e83
-
SHA1
37a658665f9b9cc3712a7f91317682273a218376
-
SHA256
92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4
-
SHA512
79391946787802fdb6e0abe708748b57f391c06343a44c4e8300b8a6a5a1daaf61d5bf7fa9ee74caa1f549bb20310dabfc8ec7cd177f7d1f02b56a6768724d2f
-
SSDEEP
12288:FBG8Z5eJocFYE1nm2q/u45KX0bgcq0em/SQoz/m:7G8Kq1
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1196-55-0x0000000000400000-0x000000000049A000-memory.dmp upx behavioral1/memory/1196-71-0x0000000000400000-0x000000000049A000-memory.dmp upx behavioral1/files/0x000a000000012677-74.dat upx -
Deletes itself 1 IoCs
pid Process 1048 cmd.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1196 set thread context of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 -
Modifies registry key 1 TTPs 1 IoCs
pid Process 1924 reg.exe -
Suspicious use of WriteProcessMemory 27 IoCs
description pid Process procid_target PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1196 wrote to memory of 1652 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 27 PID 1652 wrote to memory of 936 1652 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 28 PID 1652 wrote to memory of 936 1652 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 28 PID 1652 wrote to memory of 936 1652 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 28 PID 1652 wrote to memory of 936 1652 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 28 PID 1196 wrote to memory of 1048 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 30 PID 1196 wrote to memory of 1048 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 30 PID 1196 wrote to memory of 1048 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 30 PID 1196 wrote to memory of 1048 1196 92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe 30 PID 936 wrote to memory of 1924 936 cmd.exe 32 PID 936 wrote to memory of 1924 936 cmd.exe 32 PID 936 wrote to memory of 1924 936 cmd.exe 32 PID 936 wrote to memory of 1924 936 cmd.exe 32 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33 PID 936 wrote to memory of 1656 936 cmd.exe 33
Processes
-
C:\Users\Admin\AppData\Local\Temp\92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe"C:\Users\Admin\AppData\Local\Temp\92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1196 -
C:\Users\Admin\AppData\Local\Temp\92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe"C:\Users\Admin\AppData\Local\Temp\92cc618ee337f887284d4c08c9b4bca3330269b9ce93ac4f8cbc493c46da48f4.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1652 -
C:\Windows\SysWOW64\cmd.execmd /c C:\Users\Admin\AppData\Local\Temp\Start.bat3⤵
- Suspicious use of WriteProcessMemory
PID:936 -
C:\Windows\SysWOW64\reg.exereg add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Associations /v ModRiskFileTypes /t REG_SZ /d .exe /f4⤵
- Modifies registry key
PID:1924
-
-
C:\Windows\SysWOW64\gpupdate.exegpupdate /force4⤵PID:1656
-
-
-
-
C:\Windows\SysWOW64\cmd.execmd /c C:\Users\Admin\AppData\Local\Temp\jnduf.bat2⤵
- Deletes itself
PID:1048
-
Network
MITRE ATT&CK Enterprise v6
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
200B
MD59cedeb0b293d2b5491225ef3d9eb2a8b
SHA1b607ef9bd319b6ec696c8dab8a314998d133298b
SHA2563fc59706783a0778da9121da52a63e34e47c82f436d5b14943e14fb418fd4f08
SHA512ec7d4544e32b1ea460895b1037a9eca2529eed45d6ee1644f83dfc4d4ad8f7c32a811ee4627bc6b243fb5d5c9e3e2b22060d6a2903692830ff1f114d2b9f3cfc
-
Filesize
341B
MD5fdca3b2b1a4816aae18bb6e8a04a2508
SHA16feb05c959f3332ada1b507da72c00763ebebab5
SHA256dfa9ddf59ff1f217c6e7fe104bf43a3e8a3aaa2b4957916f74f20ade925530b0
SHA512ffde80051fb1281adf3e78ed04d429004f6d7681d50b147103ab338bb1b951c0a2d8ed187a640fa6837066f33a4bd0863561e5b7d4951f4637129608921b8c74
-
Filesize
608KB
MD57fba722cfba0224abaf6bd896b857cd4
SHA104fde645a163effc56c9b26e0b6a4628101bf2c9
SHA2561202329cdbae9d55bb7d7b4cbbadbecf20cdf5de1403927bb72fe3af5b4543ef
SHA512dc0704f83967a6451ca0614180264ebd670a0d23652f2512d6c3eb0381a5e7399f0ed5a4ca356e2dbe6721f97f0ced56edd86109c31eecf09a2878a616a3d774