2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d

Analysis

max time kernel
143s
max time network
155s
platform
windows10-2004_x64
resource
win10v2004-20220812-en
resource tags

arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
submitted
24-11-2022 07:25

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
Size

470KB
MD5

1325ea7384a4653a3a337381cfe180fa
SHA1

eb2eae4cc2a5c7356b4e00c0f3d44788c4ae27e0
SHA256

2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d
SHA512

dcaae00a97123d7d97773bdb52f99ea79c20f8a39a5366195c8fa916c7111f69117a91f259fef0ec7d6f67b7e69f734cfe7058c14696aef94ef4fcd1a0378b3d
SSDEEP

6144:eicL4qwxpzEuqcQM8sKndGxkL/Pu4tmB+K/mcm8aST97BX2Lc9i:enUlbzbuxW4uKmEK/mc+m97BWcw

Score

5^/10

Malware Config

Signatures

Suspicious use of NtCreateThreadExHideFromDebugger 1 IoCs

Processes:

2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

pid process

1872 2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

pid	process
1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

Suspicious use of SetThreadContext 1 IoCs

Processes:

2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

description	pid	process	target process
PID 1872 set thread context of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

Program crash 1 IoCs

Processes:

WerFault.exe

pid pid_target process target process

5044 3392 WerFault.exe 2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

pid	pid_target	process	target process
5044	3392	WerFault.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

Suspicious use of WriteProcessMemory 10 IoCs

Processes:

2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

description	pid	process	target process
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
PID 1872 wrote to memory of 3392	1872	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe	2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe

C:\Users\Admin\AppData\Local\Temp\2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
"C:\Users\Admin\AppData\Local\Temp\2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe"
1⤵
- Suspicious use of NtCreateThreadExHideFromDebugger
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1872

C:\Users\Admin\AppData\Local\Temp\2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe
"C:\Users\Admin\AppData\Local\Temp\2c6e410c276a53ad9c2f0560604a42bcd487e0d853b6f524b6db278ca112b81d.exe"
2⤵
PID:3392

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -u -p 3392 -s 8
3⤵
- Program crash
PID:5044

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -pss -s 440 -p 3392 -ip 3392
1⤵
PID:4308

Analysis

Sharing

General

Malware Config

Signatures

Processes

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads