Analysis
-
max time kernel
34s -
max time network
41s -
platform
windows7_x64 -
resource
win7 -
submitted
16-09-2020 16:43
Static task
static1
Behavioral task
behavioral1
Sample
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe
Resource
win7
windows7_x64
0 signatures
0 seconds
General
-
Target
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe
-
Size
259KB
-
MD5
ac8348dd8319365d4857b1e20715c6da
-
SHA1
5c5b1008a7a96015f2588fd60ddc0b4739f74fb5
-
SHA256
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0
-
SHA512
eed7640b28d4b023cd4c252ed812820221aca61f969ca2e6d5f59aad5532fae07d17401272dd36a3c49641136fa8a95d1e1d801076deb8eac97222f506f0ac86
Malware Config
Extracted
Family
buer
C2
https://kackdelar.top/
Signatures
-
Buer Loader 3 IoCs
Detects Buer loader in memory or disk.
Processes:
resource yara_rule behavioral1/memory/1764-5-0x0000000040000000-0x000000004000C000-memory.dmp buer behavioral1/memory/1764-6-0x0000000040002E00-mapping.dmp buer behavioral1/memory/1764-7-0x0000000040000000-0x000000004000C000-memory.dmp buer -
Suspicious use of SetThreadContext 1 IoCs
Processes:
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exedescription pid process target process PID 1164 set thread context of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe -
Suspicious behavior: MapViewOfSection 1 IoCs
Processes:
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exepid process 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exedescription pid process target process PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe PID 1164 wrote to memory of 1764 1164 a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe RegAsm.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe"C:\Users\Admin\AppData\Local\Temp\a6cf85f38f11e82be3fbabc2f7ee0d07f608f30ceb92654ec2168c4fcfad56e0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: MapViewOfSection
- Suspicious use of WriteProcessMemory
PID:1164 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:1764
-