Analysis
-
max time kernel
92s -
max time network
96s -
platform
windows10-2004_x64 -
resource
win10v2004-20240709-en -
resource tags
arch:x64arch:x86image:win10v2004-20240709-enlocale:en-usos:windows10-2004-x64system -
submitted
13-07-2024 11:43
Behavioral task
behavioral1
Sample
f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe
Resource
win10v2004-20240709-en
Behavioral task
behavioral2
Sample
f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe
Resource
win11-20240709-en
General
-
Target
f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe
-
Size
3.0MB
-
MD5
f91db36135a994d00b92ec2b1be0fca9
-
SHA1
4219943320a7f291a4da37aed89bce5a4a09e250
-
SHA256
f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff
-
SHA512
48ffd9c8af8019e9e3ae2a5bd479d5eb7ff815e7b9b8bf3887d8528a6e796af7d0ab17f300afadaf24cc24a2fdffd2dff73ba2062903a7f8df40c5e5521f0db9
-
SSDEEP
49152:mwOiIXJQSGd77+om1nVr6AZxPbxlhqhMKucCuTOgVrp7vRo6JE3CGiiFlENhh4xM:mT5af+tF6UxPFlQ+KdnESGNFe4xLafv
Malware Config
Signatures
-
PureLog Stealer
PureLog Stealer is an infostealer written in C#.
-
PureLog Stealer payload 1 IoCs
resource yara_rule behavioral1/memory/4124-1-0x0000000000B90000-0x0000000000E9E000-memory.dmp family_purelog_stealer -
Checks computer location settings 2 TTPs 1 IoCs
Looks up country code configured in the registry, likely geofence.
description ioc Process Key value queried \REGISTRY\USER\S-1-5-21-384068567-2943195810-3631207890-1000\Control Panel\International\Geo\Nation f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe -
Adds Run key to start application 2 TTPs 1 IoCs
description ioc Process Set value (str) \REGISTRY\USER\S-1-5-21-384068567-2943195810-3631207890-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\DataServicesWindows = "C:\\Users\\Admin\\AppData\\Roaming\\DataServicesWindows.exe" f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Suspicious behavior: EnumeratesProcesses 23 IoCs
pid Process 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 1372 powershell.exe 1372 powershell.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeDebugPrivilege 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe Token: SeDebugPrivilege 1372 powershell.exe -
Suspicious use of WriteProcessMemory 46 IoCs
description pid Process procid_target PID 4124 wrote to memory of 4820 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 86 PID 4124 wrote to memory of 4820 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 86 PID 4124 wrote to memory of 4820 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 86 PID 4820 wrote to memory of 1372 4820 cmd.exe 88 PID 4820 wrote to memory of 1372 4820 cmd.exe 88 PID 4820 wrote to memory of 1372 4820 cmd.exe 88 PID 4124 wrote to memory of 1096 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 89 PID 4124 wrote to memory of 1096 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 89 PID 4124 wrote to memory of 1096 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 89 PID 4124 wrote to memory of 1096 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 89 PID 4124 wrote to memory of 3720 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 90 PID 4124 wrote to memory of 3720 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 90 PID 4124 wrote to memory of 3720 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 90 PID 4124 wrote to memory of 3720 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 90 PID 4124 wrote to memory of 2184 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 91 PID 4124 wrote to memory of 2184 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 91 PID 4124 wrote to memory of 2184 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 91 PID 4124 wrote to memory of 2184 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 91 PID 4124 wrote to memory of 2148 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 92 PID 4124 wrote to memory of 2148 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 92 PID 4124 wrote to memory of 2148 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 92 PID 4124 wrote to memory of 2148 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 92 PID 4124 wrote to memory of 844 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 93 PID 4124 wrote to memory of 844 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 93 PID 4124 wrote to memory of 844 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 93 PID 4124 wrote to memory of 844 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 93 PID 4124 wrote to memory of 880 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 94 PID 4124 wrote to memory of 880 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 94 PID 4124 wrote to memory of 880 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 94 PID 4124 wrote to memory of 880 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 94 PID 4124 wrote to memory of 3008 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 95 PID 4124 wrote to memory of 3008 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 95 PID 4124 wrote to memory of 3008 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 95 PID 4124 wrote to memory of 3008 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 95 PID 4124 wrote to memory of 4956 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 96 PID 4124 wrote to memory of 4956 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 96 PID 4124 wrote to memory of 4956 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 96 PID 4124 wrote to memory of 4956 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 96 PID 4124 wrote to memory of 2260 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 97 PID 4124 wrote to memory of 2260 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 97 PID 4124 wrote to memory of 2260 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 97 PID 4124 wrote to memory of 2260 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 97 PID 4124 wrote to memory of 3084 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 98 PID 4124 wrote to memory of 3084 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 98 PID 4124 wrote to memory of 3084 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 98 PID 4124 wrote to memory of 3084 4124 f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe 98
Processes
-
C:\Users\Admin\AppData\Local\Temp\f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe"C:\Users\Admin\AppData\Local\Temp\f3aba98cd53c71d4d5e917e9e1fd43e3db61b46c59610eefba45b8c81f3e68ff.exe"1⤵
- Checks computer location settings
- Adds Run key to start application
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:4124 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c powershell set-mppreference -exclusionpath C:\2⤵
- Suspicious use of WriteProcessMemory
PID:4820 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell set-mppreference -exclusionpath C:\3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:1372
-
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:1096
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:3720
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:2184
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:2148
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:844
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:880
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:3008
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:4956
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:2260
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exeC:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe2⤵PID:3084
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
60B
MD5d17fe0a3f47be24a6453e9ef58c94641
SHA16ab83620379fc69f80c0242105ddffd7d98d5d9d
SHA25696ad1146eb96877eab5942ae0736b82d8b5e2039a80d3d6932665c1a4c87dcf7
SHA5125b592e58f26c264604f98f6aa12860758ce606d1c63220736cf0c779e4e18e3cec8706930a16c38b20161754d1017d1657d35258e58ca22b18f5b232880dec82