General
- Target 08052026_0256_07052026_WhatsApp IMG 07-05-26 Payment advice.zip
- Size 60KB
- Sample260508-dga2yags2n
- SHA256 d9cc58466048e39a5a396abc94124be4a82458f912f6a20ba760062c896ae7ca
- MD5 036fe04607f28a4d84d84389e075ea27
- SHA1 a522e62099076b1d05137b732e09a596007dd509
- SHA512 083815105901b27d03221d97d976882de65c2a1999c4f5133883d83c542ceb643aed05bd40868ad025490aa2693efc89c840aafe5726b6e53c1ed3f9fa0fc9e5
- SSDEEP 1536:AIZmkN8eXh/rDZ60Zc5wD7nPewV5lXJgyQO:Qku6hjDZ9O5I7n3vdJgyF
- TLSH T142533BEBC1CD62588AFD05E5D431660DA7BFDC1068221EF854F2C1BA0867F8A37966C7
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
WhatsApp IMG 07-05-26 Payment advice.vbs
Resource
win10v2004-20260130-en
17 signatures
150 seconds
Behavioral task
behavioral2
Sample
WhatsApp IMG 07-05-26 Payment advice.vbs
Resource
win11-20250610-en
21 signatures
150 seconds
Malware Config
Extracted
Family
-
xworm
Version
-
5.0
C2
-
103.83.86.92:3333
Mutex
-
UDWJhb0nWsfp7CKC
Attributes
-
install_file
USB.exe
aes.plain
Targets
-
- Target WhatsApp IMG 07-05-26 Payment advice.vbs
- Size 2.7MB
- SHA256 51cf4209be2c160f3182f2488e68eec40edd7e9f9f76224fa4b66d4ec74a35bd
- MD5 49cb9069b85abb848febad5884d61a5f
- SHA1 fdd260f303aba9acd08772b397fa05d4820413b8
- SHA512 c39fee62bf4b91e4ebf87c26a8eb2029176055832fddfe60aad3d0c5d318e2ac76d000559c10d11ea29185764f186751ebf6b1300308d641bf9ea76847f40038
- SSDEEP 768:7uuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuT:H
- TLSH T149D5AF315E84BAB0D3DB01E3F514D99DE5EE671B290DEEC9C1EA4D0523808F89CDD4AA
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Detect Xworm Payload
-
Process spawned unexpected child process
This typically indicates the parent process was compromised via an exploit or macro.
-
Badlisted process makes network request
Network request originating from process or tool commonly abused by malware.
-
Checks computer location settings
Looks up country code configured in the registry, likely geofence.
-
Executes dropped EXE
-
Loads dropped DLL
-
Accesses Microsoft Outlook profiles
-
Suspicious use of SetThreadContext