abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f

Analysis

max time kernel
141s
max time network
152s
platform
windows10-2004_x64
resource
win10v2004-20220812-en
resource tags

arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system
submitted
28/11/2022, 06:48

Target

abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
Size

1.3MB
MD5

f8977929dc84388e2f4b2bc850141b6a
SHA1

827c79bdf1c5a51c91cad1958f8fc5f01e83f3ac
SHA256

abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f
SHA512

0f1a61159fdd44497c4a01478342f541d7f1b2ed8c84128c6210479af114cd18a4419f08ef289a42e0e6ecb74b4c04b19c19f847b7c37d2275ff029fb9f8308c
SSDEEP

24576:brKqlGCPcJKwybUDwEZZODYmR9G+gnbkk6XRJfe3DqYO/KpLwFfngWX4VmJPakr:brKo4ZwCOnYjVmJPaY

Score

5^/10

Suspicious use of SetThreadContext 1 IoCs

description	pid	Process	procid_target
PID 4112 set thread context of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79

Suspicious use of SetWindowsHookEx 5 IoCs

pid	Process
4768	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
4768	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
4768	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
4768	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
4768	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe

Suspicious use of WriteProcessMemory 10 IoCs

description	pid	Process	procid_target
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79
PID 4112 wrote to memory of 4768	4112	abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe	79

C:\Users\Admin\AppData\Local\Temp\abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
"C:\Users\Admin\AppData\Local\Temp\abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe"
1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4112
- C:\Users\Admin\AppData\Local\Temp\abdb256cb387f96cd03e9cbca7e20ab859aef7c711d786fa2f50ad03d623b31f.exe
  2⤵
  - Suspicious use of SetWindowsHookEx
  PID:4768

memory/4768-133-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/4768-134-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/4768-135-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/4768-136-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download
memory/4768-137-0x0000000000400000-0x00000000004D9000-memory.dmp

Filesize
868KB

Download