General
- Target 2026-07-28_7b15ba68f516810801af38d285b9382a_elex_floxif_glassworm_stop
- Size 3.9MB
- Sample260729-a92htadp2w
- SHA256 fdcccd826bd293dc511778ff59ae2e608dd3f76631d2f8afa7fa8d30750f567e
- MD5 7b15ba68f516810801af38d285b9382a
- SHA1 717943f066a1afa4b8c03723a435ef662b4d7a14
- SHA512 c732b479cb8f1de6e9d1785f1283b95a1e820344fa3331b1b9b053a13c3737b9e064ce63af2d3fb488560b0b72611350ef1eb86057544955befb91edbf611f8b
- SSDEEP 49152:5yXKP7X3uQ3YlZfbM3DacNHHO0DZyL8x+2wmyrS5uDOzQazA7kfHWRHiaHSiBeh8:wUKNZf8mGHVD5x+2wTRv4fHgCK
- TLSH T15116AF213FC1C43ED2630272D84DA35893F2D1B06E768557AAA9135D2F35EA3DE21E72
- MD5 SHA1 SHA512 SSDEEP TLSH
Static task
static1
Behavioral task
behavioral1
Sample
2026-07-28_7b15ba68f516810801af38d285b9382a_elex_floxif_glassworm_stop.exe
Resource
win10v2004-20260513-en
Behavioral task
behavioral2
Sample
2026-07-28_7b15ba68f516810801af38d285b9382a_elex_floxif_glassworm_stop.exe
Resource
win11ltsc2024-20260709-en
Malware Config
Targets
-
- Target 2026-07-28_7b15ba68f516810801af38d285b9382a_elex_floxif_glassworm_stop
- Size 3.9MB
- SHA256 fdcccd826bd293dc511778ff59ae2e608dd3f76631d2f8afa7fa8d30750f567e
- MD5 7b15ba68f516810801af38d285b9382a
- SHA1 717943f066a1afa4b8c03723a435ef662b4d7a14
- SHA512 c732b479cb8f1de6e9d1785f1283b95a1e820344fa3331b1b9b053a13c3737b9e064ce63af2d3fb488560b0b72611350ef1eb86057544955befb91edbf611f8b
- SSDEEP 49152:5yXKP7X3uQ3YlZfbM3DacNHHO0DZyL8x+2wmyrS5uDOzQazA7kfHWRHiaHSiBeh8:wUKNZf8mGHVD5x+2wTRv4fHgCK
- TLSH T15116AF213FC1C43ED2630272D84DA35893F2D1B06E768557AAA9135D2F35EA3DE21E72
- MD5 SHA1 SHA512 SSDEEP TLSH
-
Detects Floxif payload
-
UPX dump on OEP (original entry point)
-
Event Triggered Execution: AppInit DLLs
Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppInit DLLs loaded into processes.
-
ACProtect 1.3x - 1.4x DLL software
Detects file using ACProtect software.
-
Loads dropped DLL
-
Enumerates connected drives
Attempts to read the root path of hard drives other than the default C: drive.
-
Maps connected drives based on registry
Disk information is often read in order to detect sandboxing environments.
-
Writes to the Master Boot Record (MBR)
Bootkits write to the MBR to gain persistence at a level below the operating system.