Analysis
-
max time kernel
120s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20230712-en -
resource tags
arch:x64arch:x86image:win7-20230712-enlocale:en-usos:windows7-x64system -
submitted
10-08-2023 16:44
Static task
static1
Behavioral task
behavioral1
Sample
b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe
Resource
win7-20230712-en
General
-
Target
b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe
-
Size
1.1MB
-
MD5
a490f1848b792df4dc37c9e1b200578d
-
SHA1
f862b1f3460aafd54b1159b2a180f70e6b3d8d21
-
SHA256
b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e
-
SHA512
1e9a492976d2c80acd7cebfa8ca8fba55c3a9cb71ecf12a5c29e648f6fcc0d9d41930a33964c6b85ecbc96150a25dcc08578da5d2e0dd509d370256d4d20f268
-
SSDEEP
24576:mDXdMCbh0lhSMXlPFN3RFEuHhra2oQfKhBdY7O8gz/7:mBMPt/G29fKhBdYy8ij
Malware Config
Signatures
-
Deletes itself 1 IoCs
pid Process 2664 cmd.exe -
Reads user/profile data of web browsers 2 TTPs
Infostealers often target stored browser data, which can include saved credentials etc.
-
Looks up external IP address via web service 3 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
flow ioc 7 api.ipify.org 3 api.ipify.org 5 api.ipify.org -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2304 set thread context of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 -
Runs ping.exe 1 TTPs 1 IoCs
pid Process 2744 PING.EXE -
Suspicious use of WriteProcessMemory 24 IoCs
description pid Process procid_target PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 2304 wrote to memory of 292 2304 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 28 PID 292 wrote to memory of 2664 292 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 30 PID 292 wrote to memory of 2664 292 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 30 PID 292 wrote to memory of 2664 292 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe 30 PID 2664 wrote to memory of 2744 2664 cmd.exe 32 PID 2664 wrote to memory of 2744 2664 cmd.exe 32 PID 2664 wrote to memory of 2744 2664 cmd.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe"C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2304 -
C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe"C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:292 -
C:\Windows\System32\cmd.exe"C:\Windows\System32\cmd.exe" /C ping 1.1.1.1 -n 1 -w 3000 > Nul & Del /f /q "C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e_JC.exe"3⤵
- Deletes itself
- Suspicious use of WriteProcessMemory
PID:2664 -
C:\Windows\system32\PING.EXEping 1.1.1.1 -n 1 -w 30004⤵
- Runs ping.exe
PID:2744
-
-
-