General
- Target Items_Pricerate20201345.xls
- Size 79KB
- Sample200707-vsv9h1kd2n
- SHA256 eba7c4994a5cde3da749b4ebdb5e01ba0e675262198217b36f8cfd61daabae43
- MD5 0533369850fbb2fe2460d2e3ec5507d2
- SHA1 93d57c8f193e0132ec0baf9c4d0a9f8018791413
- SHA512 a8d181cf3779ada1703d8dc1cd6ddb724b0e1f8b4707cb37eab4d1bdc203400d757a53d52c58b375597999da0be0e7937031bfa2dcc516fe3f064fa64982eb42
- MD5 SHA1 SHA512
Static task
static1
Behavioral task
behavioral1
Sample
Items_Pricerate20201345.xls
Resource
win7
Malware Config
Extracted
-
trickbot
-
1000512
-
chil60
-
95.171.16.42:443
-
185.90.61.9:443
-
5.1.81.68:443
-
185.99.2.65:443
-
134.119.191.11:443
-
85.204.116.100:443
-
78.108.216.47:443
-
51.81.112.144:443
-
194.5.250.121:443
-
185.14.31.104:443
-
185.99.2.66:443
-
107.175.72.141:443
-
192.3.247.123:443
-
134.119.191.21:443
-
85.204.116.216:443
-
91.235.129.20:443
-
181.129.104.139:449
-
181.112.157.42:449
-
181.129.134.18:449
-
131.161.253.190:449
-
121.100.19.18:449
-
190.136.178.52:449
-
45.6.16.68:449
-
110.232.76.39:449
-
122.50.6.122:449
-
103.12.161.194:449
-
36.91.45.10:449
-
110.93.15.98:449
-
80.210.32.67:449
-
103.111.83.246:449
-
200.107.35.154:449
-
36.89.182.225:449
-
36.89.243.241:449
-
36.92.19.205:449
-
110.50.84.5:449
-
182.253.113.67:449
-
36.66.218.117:449
-
autorunName:pwgrab
Targets
-
- Target Items_Pricerate20201345.xls
- Size 79KB
- SHA256 eba7c4994a5cde3da749b4ebdb5e01ba0e675262198217b36f8cfd61daabae43
- MD5 0533369850fbb2fe2460d2e3ec5507d2
- SHA1 93d57c8f193e0132ec0baf9c4d0a9f8018791413
- SHA512 a8d181cf3779ada1703d8dc1cd6ddb724b0e1f8b4707cb37eab4d1bdc203400d757a53d52c58b375597999da0be0e7937031bfa2dcc516fe3f064fa64982eb42
- MD5 SHA1 SHA512
-
Process spawned unexpected child process
This typically indicates the parent process was compromised via an exploit or macro.
-
Templ.dll packer
Detects Templ.dll packer which usually loads Trickbot.
-
Loads dropped DLL
-
Reads user/profile data of web browsers
Infostealers often target stored browser data, which can include saved credentials etc.
-
Process spawned suspicious child process
This child process is typically not spawned unless (for example) the parent process crashes. This typically indicates the parent process was unsuccessfully compromised.