Analysis
- max time kernel
144s - max time network
147s - platform
windows10-2004_x64 - resource
win10v2004-20220414-en - submitted
03/05/2022, 20:31
Static task
static1
Behavioral task
behavioral1
Sample
d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe
Resource
win7-20220414-en
0 signatures
0 seconds
Behavioral task
behavioral2
Sample
d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe
Resource
win10v2004-20220414-en
0 signatures
0 seconds
General
- Target d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe
- Size 241KB
- Sample220503-zay13sefcn
- SHA256 d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344
- MD5 917ccb7eb85219db2ff8104945bec3eb
- SHA1 480b275fe4a9533617147086d32e39618b29a9df
- SHA512 6d239a4d544c8b6245e6d18bdd2eafd8b953f0917174f3123780dab64c0d9b5369285740df70bb56b5e0a11e8259861c6d80d77d2bfe8a2cb47d64f39cab99e8
- MD5 SHA1 SHA512
Score
10/10
Malware Config
Signatures
- OnlyLogger
A tiny loader that uses IPLogger to get its payload.
- OnlyLogger Payload 2 IoCs
resource yara_rule behavioral2/memory/1864-131-0x00000000007C0000-0x0000000000806000-memory.dmp family_onlylogger behavioral2/memory/1864-132-0x0000000000400000-0x00000000004F6000-memory.dmp family_onlylogger - 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-3751123196-3323558407-1869646069-1000\Control Panel\International\Geo\Nation d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe - Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
- Program crash 1 IoCs
pid pid_target Process procid_target 3636 1864 WerFault.exe 79 - Kills process with taskkill 1 IoCs
pid Process 2204 taskkill.exe - Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 2204 taskkill.exe - Suspicious use of WriteProcessMemory 6 IoCs
description pid Process procid_target PID 1864 wrote to memory of 2644 1864 d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe 80 PID 1864 wrote to memory of 2644 1864 d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe 80 PID 1864 wrote to memory of 2644 1864 d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe 80 PID 2644 wrote to memory of 2204 2644 cmd.exe 84 PID 2644 wrote to memory of 2204 2644 cmd.exe 84 PID 2644 wrote to memory of 2204 2644 cmd.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe"C:\Users\Admin\AppData\Local\Temp\d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe"1⤵
- Checks computer location settings
- Suspicious use of WriteProcessMemory
PID:1864 -
C:\Windows\SysWOW64\cmd.exe"C:\Windows\System32\cmd.exe" /c taskkill /im "d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe" /f & erase "C:\Users\Admin\AppData\Local\Temp\d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe" & exit2⤵
- Suspicious use of WriteProcessMemory
PID:2644 -
C:\Windows\SysWOW64\taskkill.exetaskkill /im "d73b5c9ba3ddf0b41ea66cf4eea9098d4e810d195cfc37539010d6e49b954344.exe" /f3⤵
- Kills process with taskkill
- Suspicious use of AdjustPrivilegeToken
PID:2204
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1864 -s 12642⤵
- Program crash
PID:3636
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 404 -p 1864 -ip 18641⤵PID:912