Analysis
-
max time kernel
135s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
21-05-2024 02:42
Behavioral task
behavioral1
Sample
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
Resource
win7-20240221-en
General
-
Target
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe
-
Size
1.6MB
-
MD5
309db6cee33cc2b6f29d73366f485524
-
SHA1
7af3deb5792f1ebefc663672b269655eec723ad6
-
SHA256
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
-
SHA512
0f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgHa:E5aIwC+Agr6SqCPGC6HZkIT/S
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule \Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral1/memory/2172-15-0x0000000000320000-0x0000000000349000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exepid process 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 412 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Loads dropped DLL 2 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exepid process 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe -
Drops file in System32 directory 1 IoCs
Processes:
powershell.exedescription ioc process File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe -
Launches sc.exe 2 IoCs
Sc.exe is a Windows utlilty to control services on the system.
Processes:
sc.exesc.exepid process 2592 sc.exe 2652 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exepowershell.exepid process 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 2500 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
Processes:
powershell.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exedescription pid process Token: SeDebugPrivilege 2500 powershell.exe Token: SeTcbPrivilege 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe Token: SeTcbPrivilege 412 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exepid process 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe 412 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.execmd.execmd.execmd.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exetaskeng.exead99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exedescription pid process target process PID 2172 wrote to memory of 2596 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2596 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2596 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2596 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2632 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2632 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2632 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2632 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2676 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2676 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2676 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2676 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe cmd.exe PID 2172 wrote to memory of 2204 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 2172 wrote to memory of 2204 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 2172 wrote to memory of 2204 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 2172 wrote to memory of 2204 2172 ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 2596 wrote to memory of 2652 2596 cmd.exe sc.exe PID 2596 wrote to memory of 2652 2596 cmd.exe sc.exe PID 2596 wrote to memory of 2652 2596 cmd.exe sc.exe PID 2596 wrote to memory of 2652 2596 cmd.exe sc.exe PID 2632 wrote to memory of 2592 2632 cmd.exe sc.exe PID 2632 wrote to memory of 2592 2632 cmd.exe sc.exe PID 2632 wrote to memory of 2592 2632 cmd.exe sc.exe PID 2632 wrote to memory of 2592 2632 cmd.exe sc.exe PID 2676 wrote to memory of 2500 2676 cmd.exe powershell.exe PID 2676 wrote to memory of 2500 2676 cmd.exe powershell.exe PID 2676 wrote to memory of 2500 2676 cmd.exe powershell.exe PID 2676 wrote to memory of 2500 2676 cmd.exe powershell.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 2204 wrote to memory of 2472 2204 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 1952 wrote to memory of 840 1952 taskeng.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 1952 wrote to memory of 840 1952 taskeng.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 1952 wrote to memory of 840 1952 taskeng.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 1952 wrote to memory of 840 1952 taskeng.exe ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe PID 840 wrote to memory of 1660 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 840 wrote to memory of 1660 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 840 wrote to memory of 1660 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe PID 840 wrote to memory of 1660 840 ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe svchost.exe -
Uses Task Scheduler COM API 1 TTPs
The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.
Processes
-
C:\Users\Admin\AppData\Local\Temp\ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe"C:\Users\Admin\AppData\Local\Temp\ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
-
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵
-
C:\Windows\system32\taskeng.exetaskeng.exe {871C217F-DC11-46E6-9417-4784CE793BEF} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵
-
C:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeC:\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵
Network
MITRE ATT&CK Matrix ATT&CK v13
Replay Monitor
Loading Replay Monitor...
Downloads
-
\Users\Admin\AppData\Roaming\WinSocket\ad99ebcd263e9a00c1db8ffcad1670e146443602b79d068ae22696f798d2d883.exeFilesize
1.6MB
MD5309db6cee33cc2b6f29d73366f485524
SHA17af3deb5792f1ebefc663672b269655eec723ad6
SHA256ad98ebcd253e8a00c1db7ffcad1560e145443502b69d057ae22585f697d2d773
SHA5120f81a3a3418da2a3807026e22d5968465f2db9cc6ac898a6282ec66cd611b68e5d1967fae2c2f6a5e0c63d9a0942fd7925e7384266fa157d608cd0a790d9dcaa
-
memory/840-71-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-70-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-69-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-68-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-67-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-66-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-72-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-65-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-64-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-63-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-62-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/840-61-0x0000000000260000-0x0000000000261000-memory.dmpFilesize
4KB
-
memory/2172-12-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-13-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-18-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/2172-15-0x0000000000320000-0x0000000000349000-memory.dmpFilesize
164KB
-
memory/2172-9-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-10-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-11-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-17-0x0000000000421000-0x0000000000422000-memory.dmpFilesize
4KB
-
memory/2172-14-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-4-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-7-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-8-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-2-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-3-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-5-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2172-6-0x00000000002F0000-0x00000000002F1000-memory.dmpFilesize
4KB
-
memory/2204-37-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-34-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-45-0x0000000010000000-0x0000000010007000-memory.dmpFilesize
28KB
-
memory/2204-41-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-44-0x0000000000400000-0x0000000000472000-memory.dmpFilesize
456KB
-
memory/2204-30-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-31-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-32-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-33-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-46-0x0000000010000000-0x0000000010007000-memory.dmpFilesize
28KB
-
memory/2204-35-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-36-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-38-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-39-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2204-40-0x00000000003F0000-0x00000000003F1000-memory.dmpFilesize
4KB
-
memory/2472-49-0x0000000010000000-0x000000001001E000-memory.dmpFilesize
120KB
-
memory/2472-50-0x0000000010000000-0x000000001001E000-memory.dmpFilesize
120KB