8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90

Analysis

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

arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system
submitted
01/10/2023, 20:16

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe
Size

276KB
MD5

daeda710935ca645576818e0b0a6b84b
SHA1

4a4b01ce3e39d5598d0031cda8b1af9d3d329e67
SHA256

8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90
SHA512

28f62ec366052f41651234e24225485bd91e5d0328b87ee67156c98071e429af1cbf132f387f8f5f23d7a18e894a8ca716e8f3aa84f502116d1ba46f4b76a83d
SSDEEP

6144:WhCcKajWpVP06ik3mU29FeiZ7j0VfWpgrj:W1KajWYUM7j0Ipej

Score

5^/10

Malware Config

Signatures

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 2000 set thread context of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29

Program crash 2 IoCs

pid	pid_target	Process	procid_target
2796	2000	WerFault.exe	27
2936	2224	WerFault.exe	29

Suspicious use of WriteProcessMemory 25 IoCs

description	pid	Process	procid_target
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2224	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	29
PID 2000 wrote to memory of 2796	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	30
PID 2000 wrote to memory of 2796	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	30
PID 2000 wrote to memory of 2796	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	30
PID 2000 wrote to memory of 2796	2000	8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe	30
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31
PID 2224 wrote to memory of 2936	2224	AppLaunch.exe	31

C:\Users\Admin\AppData\Local\Temp\8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe
"C:\Users\Admin\AppData\Local\Temp\8085430f270fd6ebcec4d167ee88472e314ef6f7125706f0d8c8a1c3f9796b90_JC.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2000
- 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:2224
- - C:\Windows\SysWOW64\WerFault.exe
    C:\Windows\SysWOW64\WerFault.exe -u -p 2224 -s 196
    3⤵
    - Program crash
    PID:2936
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 2000 -s 68
  2⤵
  - Program crash
  PID:2796

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads

memory/2224-0-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-1-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-2-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-3-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-4-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-5-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

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

Filesize
4KB

Download
memory/2224-7-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-9-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download
memory/2224-11-0x0000000000400000-0x0000000000428000-memory.dmp

Filesize
160KB

Download

Analysis

Sharing

General

Malware Config

Signatures

Processes

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads