3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa

Analysis

max time kernel
121s
max time network
124s
platform
windows7_x64
resource
win7-20230831-en
resource tags

arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system
submitted
12-09-2023 12:50

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe
Size

1.4MB
MD5

f6b485ccef600f36706edab8954f0a30
SHA1

601ffe5e0576fedaec6a90a32c0a7944da8e21ca
SHA256

3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa
SHA512

ee1578bb02817b1e152d84f72f1daa29b45114ef708663bffe5d2821e0d630ecc4352fe7f6f57f33b85de0d4ce89f928c07e16e4997f3d93f18caf73beeda4b4
SSDEEP

24576:6RSiHSTDB3oblEne2AAqPg4/ALRrODqAUG3sytSCi52fOPGAuSc/YUny:hiyTDEUe2AJPpX3syt65nFuSiYo

Score

5^/10

Malware Config

Signatures

Suspicious use of SetThreadContext 1 IoCs

Processes:

3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe

description	pid	process	target process
PID 3012 set thread context of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe

Program crash 1 IoCs

Processes:

WerFault.exe

pid pid_target process target process

2308 2948 WerFault.exe AppLaunch.exe

pid	pid_target	process	target process
2308	2948	WerFault.exe	AppLaunch.exe

Suspicious use of WriteProcessMemory 21 IoCs

Processes:

3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exeAppLaunch.exe

description	pid	process	target process
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 3012 wrote to memory of 2948	3012	3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe	AppLaunch.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe
PID 2948 wrote to memory of 2308	2948	AppLaunch.exe	WerFault.exe

C:\Users\Admin\AppData\Local\Temp\3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe
"C:\Users\Admin\AppData\Local\Temp\3fb9ffe6f9613f18c1e9984787d37a5d9ed4cdc37c628be7cba33d5c37e782aa_JC.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3012

C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"
2⤵
- Suspicious use of WriteProcessMemory
PID:2948

C:\Windows\SysWOW64\WerFault.exe
C:\Windows\SysWOW64\WerFault.exe -u -p 2948 -s 200
3⤵
- Program crash
PID:2308

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads

memory/2948-0-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-1-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-2-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-4-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-3-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-6-0x00000000FFFDE000-0x00000000FFFDF000-memory.dmp

Filesize
4KB

Download
memory/2948-5-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-7-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-9-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download
memory/2948-11-0x0000000000400000-0x000000000053A000-memory.dmp

Filesize
1.2MB

Download