General
- Target Revised Invoice.js
- Size 29KB
- Sample260924-qrybfaee38
- SHA256 418c63bee3b1ffdc417a31ec87c3b1158128976ba189f45fd9a45864f86e6826
- MD5 6c2780b60fa96cda7ed3e117bbf40d54
- SHA1 be61f57420899d9020a729f68bda1df474ab8a9b
- SHA512 b9e8d9062b0d865a222df32bda24fb7aa861b86df20790fa29a1ac2e82ac8fabf97c650fe71c8bc9fd59f65a53d4a1e4991c00be539a48e8a04b3d25490d74ff
- SSDEEP 768:3LDQ0Jur2Lv0nREyhjtUYlcQVHSOOf72k05lB9ynmnvU6/3U1mZqnZcdW:bxguA0tLH
- TLSH T138D20D415982749093336B7AA726A8E8F77B067B01944943B83CB494EFF1D18DFE4DB1
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
Revised Invoice.js
Resource
win10v2004-20260911-en
16 signatures
150 seconds
Behavioral task
behavioral2
Sample
Revised Invoice.js
Resource
win11ltsc2024-20260911-en
15 signatures
150 seconds
Malware Config
Extracted
Family
-
vipkeylogger
Credentials
-
Protocol
smtp
-
Host
hosting2.ro.hostsailor.com
-
Port
587
-
Username
-
Password
7213575aceACE@@
-
Email to
Targets
-
- Target Revised Invoice.js
- Size 29KB
- SHA256 418c63bee3b1ffdc417a31ec87c3b1158128976ba189f45fd9a45864f86e6826
- MD5 6c2780b60fa96cda7ed3e117bbf40d54
- SHA1 be61f57420899d9020a729f68bda1df474ab8a9b
- SHA512 b9e8d9062b0d865a222df32bda24fb7aa861b86df20790fa29a1ac2e82ac8fabf97c650fe71c8bc9fd59f65a53d4a1e4991c00be539a48e8a04b3d25490d74ff
- SSDEEP 768:3LDQ0Jur2Lv0nREyhjtUYlcQVHSOOf72k05lB9ynmnvU6/3U1mZqnZcdW:bxguA0tLH
- TLSH T138D20D415982749093336B7AA726A8E8F77B067B01944943B83CB494EFF1D18DFE4DB1
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Family: VIPKeylogger
VIPKeylogger is a keylogger and infostealer written in C# and it resembles SnakeKeylogger that was found in 2020.
-
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.
-
Accesses Microsoft Outlook profiles
-
Looks up external IP address via web service
Uses a legitimate IP lookup service to find the infected system's external IP.
-
Suspicious use of SetThreadContext