Hey, I recently noticed the activity of the stealer to load the configuration.
0x20 bytes xor key
AC B7 67 69 C8 D3 1A 3A E9 C4 FB 55 87 6D 49 D9 B7 73 94 69 ED E1 DE A0 0A 51 0E 4F FF CA C5 A9
The analysis was carried out by an analyst from any.run in the sandbox at the following link:
For better coverage, I would like to share the following rule:
The decrypted traffic for the sample you shared and some others we found still hit on existing Lumma sigs, one was a ET PRO sig that we moved to the Open set today.
2049836 - ET MALWARE Lumma Stealer Related Activity (previously 2855505)
The following are the new sigs that went out based on the sample you shared and others that were found poking arounnd.
2049838 - ET MALWARE Observed Lumma Stealer Related Domain (agedelayglacierwe .pw in TLS SNI)
2049839 - ET MALWARE Lumma Stealer Related Domain in DNS Lookup (agedelayglacierwe .pw)
2049842 - ET MALWARE Lumma Stealer Related Domain in DNS Lookup (chincenterblandwka .pw)
2049843 - ET MALWARE Observed Lumma Stealer Related Domain (chincenterblandwka .pw in TLS SNI)
2049844 - ET MALWARE Lumma Stealer Related Domain in DNS Lookup (neighborhoodfeelsa .fun)
2049845 - ET MALWARE Observed Lumma Stealer Related Domain (neighborhoodfeelsa .fun in TLS SNI)
We also added INFO sigs for the URI shortening service from the run you shared.
2049840 - ET INFO URI Shortening Service Domain in DNS Lookup (cli .re)
2049841 - ET INFO Observed URI Shortening Service Domain (cli .re in TLS SNI)