General
- Target OVERDUE PAYMENT.js
- Size 1.2MB
- Sample260821-kjs4vsbk3t
- SHA256 7fd0a79d6396aafc3855da89d19cf38c924a8816db6ba7c45d0f54f453bc1b9b
- MD5 9b1389ca1a80d5721556bc106c634403
- SHA1 3fd7a846049bf8850179cc2b25a5c54b26e76396
- SHA512 a9025b686f32ebdae3a6a8977d1f07923256e28e3018f22aceeb37a76eb3a40a312268e563f7c83466518164915f8a36628e1b71c18e9fe531d81d40216369a4
- SSDEEP 192:nHi0qsp74vtei+eT9iSYiIc7nddLFinHYiIiinitixO2UvYi0Ofkini0H7UArOs5:9lU5gNfJZeTygWgsM1f9/Wz/C18
- TLSH T12145433BC71A0266D37B9544C5B387843BEC65341F5A730428C3EA5726CAA49D7F3BA8
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
OVERDUE PAYMENT.js
Resource
win10v2004-20260513-en
8 signatures
150 seconds
Behavioral task
behavioral2
Sample
OVERDUE PAYMENT.js
Resource
win11ltsc2024-20260709-en
15 signatures
150 seconds
Malware Config
Extracted
Language
-
ps1
Deobfuscated
Source
URLs
-
exe.dropper
http://193.104.58.65/rumpyu18.png
Extracted
Family
-
xworm
Version
-
5.0
C2
-
194.116.236.49:2222
Mutex
-
L9J7bax6V38Cuxgd
Attributes
-
install_file
USB.exe
aes.plain
Targets
-
- Target OVERDUE PAYMENT.js
- Size 1.2MB
- SHA256 7fd0a79d6396aafc3855da89d19cf38c924a8816db6ba7c45d0f54f453bc1b9b
- MD5 9b1389ca1a80d5721556bc106c634403
- SHA1 3fd7a846049bf8850179cc2b25a5c54b26e76396
- SHA512 a9025b686f32ebdae3a6a8977d1f07923256e28e3018f22aceeb37a76eb3a40a312268e563f7c83466518164915f8a36628e1b71c18e9fe531d81d40216369a4
- SSDEEP 192:nHi0qsp74vtei+eT9iSYiIc7nddLFinHYiIiinitixO2UvYi0Ofkini0H7UArOs5:9lU5gNfJZeTygWgsM1f9/Wz/C18
- TLSH T12145433BC71A0266D37B9544C5B387843BEC65341F5A730428C3EA5726CAA49D7F3BA8
- 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.
-
Command and Scripting Interpreter: PowerShell
Run Powershell to modify Windows Defender settings to add exclusions for file extensions, paths, and processes.
-
Creates a file in the Startup directory
A file was written to a Windows startup folder. Files in these directories are executed automatically when a user logs on or an application initializes.
-
Suspicious use of SetThreadContext