Analysis
-
max time kernel
142s -
max time network
146s -
platform
windows10-2004_x64 -
resource
win10v2004-20230703-en -
resource tags
arch:x64arch:x86image:win10v2004-20230703-enlocale:en-usos:windows10-2004-x64system -
submitted
04-08-2023 00:49
Static task
static1
1 signatures
General
-
Target
b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe
-
Size
1.1MB
-
MD5
a490f1848b792df4dc37c9e1b200578d
-
SHA1
f862b1f3460aafd54b1159b2a180f70e6b3d8d21
-
SHA256
b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e
-
SHA512
1e9a492976d2c80acd7cebfa8ca8fba55c3a9cb71ecf12a5c29e648f6fcc0d9d41930a33964c6b85ecbc96150a25dcc08578da5d2e0dd509d370256d4d20f268
-
SSDEEP
24576:mDXdMCbh0lhSMXlPFN3RFEuHhra2oQfKhBdY7O8gz/7:mBMPt/G29fKhBdYy8ij
Malware Config
Signatures
-
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 2 IoCs
Uses a legitimate IP lookup service to find the infected system's external IP.
flow ioc 30 api.ipify.org 31 api.ipify.org -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5068 set thread context of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Runs ping.exe 1 TTPs 1 IoCs
pid Process 2904 PING.EXE -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 5068 wrote to memory of 1696 5068 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 90 PID 1696 wrote to memory of 3768 1696 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 93 PID 1696 wrote to memory of 3768 1696 b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe 93 PID 3768 wrote to memory of 2904 3768 cmd.exe 95 PID 3768 wrote to memory of 2904 3768 cmd.exe 95
Processes
-
C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe"C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5068 -
C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe"C:\Users\Admin\AppData\Local\Temp\b61325a676000c0afb169f63048c583bc81cb52e1690a6ccf5642decb7831b5e.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:1696 -
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.exe"3⤵
- Suspicious use of WriteProcessMemory
PID:3768 -
C:\Windows\system32\PING.EXEping 1.1.1.1 -n 1 -w 30004⤵
- Runs ping.exe
PID:2904
-
-
-