Trojan.Lumma.DA
Threat Scorecard
EnigmaSoft Threat Scorecard
EnigmaSoft Threat Scorecards are assessment reports for different malware threats which have been collected and analyzed by our research team. EnigmaSoft Threat Scorecards evaluate and rank threats using several metrics including real-world and potential risk factors, trends, frequency, prevalence, and persistence. EnigmaSoft Threat Scorecards are updated regularly based on our research data and metrics and are useful for a wide range of computer users, from end users seeking solutions to remove malware from their systems to security experts analyzing threats.
EnigmaSoft Threat Scorecards display a variety of useful information, including:
Popularity Rank: The ranking of a particular threat in EnigmaSoft’s Threat Database.
Severity Level: The determined severity level of an object, represented numerically, based on our risk modeling process and research, as explained in our Threat Assessment Criteria.
Infected Computers: The number of confirmed and suspected cases of a particular threat detected on infected computers as reported by SpyHunter.
See also Threat Assessment Criteria.
| Popularity Rank: | 14,948 |
| Threat Level: | 80 % (High) |
| Infected Computers: | 26 |
| First Seen: | December 14, 2024 |
| Last Seen: | July 12, 2026 |
| OS(es) Affected: | Windows |
The detection of Trojan.Lumma.DA indicates that your system has been compromised by a potentially malicious threat. This type of threat is generally categorized as a Trojan, which is a broad term for malicious software that disguises itself as legitimate. Trojans can have various effects on a system, ranging from data theft to disruption of service, and understanding the nature of the threat is crucial for effective removal and prevention of future infections.
Table of Contents
What Is Trojan.Lumma.DA?
Trojan.Lumma.DA, as detected by security software, suggests a specific identification of a malicious entity. However, without more detailed information, it's challenging to pinpoint the exact characteristics or the intentions behind this particular threat. Generally, Trojans are designed to allow unauthorized access to a computer, and they can be used to steal sensitive information, install additional malware, or disrupt system operation. The name itself does not directly indicate a known malware family but rather serves as an identifier for the detected threat.
How Trojan.Lumma.DA Operates
Trojans typically operate by deceiving users into installing them, often by masquerading as useful software or attachments in emails. Once installed, they can execute a wide range of malicious activities, from keystroke logging to exploiting system vulnerabilities. The specific operations of Trojan.Lumma.DA would depend on its design and the goals of its creators, which could range from financial gain through data theft to using the infected machine as part of a larger network for malicious activities.
Symptoms of Infection
Symptoms of a Trojan infection can vary widely but may include noticeable slowdowns of the system, frequent crashes, or unusual network activity. Some Trojans may also trigger additional malware downloads, which can lead to more severe system compromise. Users might also notice unfamiliar programs or toolbars in their browsers, changes in system settings, or an increase in pop-up advertisements. However, some Trojans are designed to operate stealthily, making them difficult to detect without proper security software.
How to Remove Trojan.Lumma.DA
- Boot your computer in Safe Mode with Networking to limit the malware's ability to interfere with the removal process.
- Perform a full scan of your system using a reputable anti-malware tool, such as SpyHunter, to detect and remove all traces of the Trojan.
- Uninstall any recently installed or suspicious programs that could be related to the infection.
- Reset your web browsers (Chrome, Firefox, Edge) to their default settings to remove any malicious extensions or settings changes.
- Reboot your computer and run another full scan with your anti-malware tool to ensure that all components of the Trojan have been removed.
It's also a good practice to change passwords for all accounts, especially if you've used the same passwords on the infected computer, to prevent further unauthorized access.
Conclusion
The removal of Trojan.Lumma.DA requires careful and systematic steps to ensure that all components of the malware are eliminated from the system. Preventing future infections involves a combination of using reputable security software, practicing safe browsing habits, avoiding suspicious downloads, and keeping your operating system and software up to date. By understanding the nature of Trojans and taking proactive measures, users can significantly reduce the risk of infection and protect their digital assets.
Analysis Report
General information
| Family Name: | Trojan.Lumma.DA |
|---|---|
| Signature status: | Hash Mismatch |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
abed5d2a9e1961b34d246520c5162534
SHA1:
f5b383a6da49d85511337372d55bc4d5a90aa4d5
SHA256:
98387D1AB6A06DDA6ECBF23C9325ACA0E0171C0D05827DA5EE7A988A33034573
File Size:
7.75 MB, 7754040 bytes
|
|
MD5:
06bdff0249101851fd564b8504282ec5
SHA1:
35a338b3e92a2a6caf8cd88a71852673825218fd
SHA256:
28EC022369B6B61B7C0F88D752601FE846F9BCC39096CFD6BDA1C41A911C92E5
File Size:
4.80 MB, 4803706 bytes
|
|
MD5:
0a8ee85166a63e2889cf035b4611eb0d
SHA1:
1ff36c5e2534bfc0fa922befbb6d1c5dd73db6f4
SHA256:
3DA8C8CEED2F51AAF8C8791E100E9CCD484F0163FCD10FBF08C733B55AE5F97F
File Size:
8.20 MB, 8195392 bytes
|
|
MD5:
78a1416725e14fa76df7b8ec057d12ae
SHA1:
daaf784c07afd2b687929063095d373f37d8aeb0
SHA256:
135BE22DFF3118A67CA6BC5981F43A7256107CFA1AC5478449A4636197E38B1C
File Size:
5.14 MB, 5143981 bytes
|
|
MD5:
beacb2d8d4568aaec9592ad3847caa41
SHA1:
5851a8f976509a0a3cd9bc0a0cc02f0e94ca90db
SHA256:
1C4A7E56CEF67A2C2252B6761F2876DF803D8BA52F9340CFA3D6455F0CA0E980
File Size:
5.97 MB, 5970128 bytes
|
Windows Portable Executable Attributes
- File doesn't have "Rich" header
- File doesn't have debug information
- File doesn't have exports table
- File doesn't have relocations information
- File doesn't have security information
- File has TLS information
- File is 32-bit executable
- File is console application (IMAGE_SUBSYSTEM_WINDOWS_CUI)
- File is either console or GUI application
- File is GUI application (IMAGE_SUBSYSTEM_WINDOWS_GUI)
Show More
- File is Native application (NOT .NET application)
- File is not packed
- IMAGE_FILE_DLL is not set inside PE header (Executable)
- IMAGE_FILE_EXECUTABLE_IMAGE is set inside PE header (Executable Image)
File Icons
File Icons
This section displays icon resources found within family samples. Malware often replicates icons commonly associated with legitimate software to mislead users into believing the malware is safe.
Windows PE Version Information
Windows PE Version Information
This section displays values and attributes that have been set in the Windows file version information data structure for samples within this family. To mislead users, malware actors often add fake version information mimicking legitimate software.| Name | Value |
|---|---|
| Comments | This installation was built with Inno Setup. |
| Company Name |
|
| File Description |
|
| File Version |
|
| Internal Name | stnlc |
| Legal Copyright |
|
| Legal Trademarks | Acronis International GmbH. All rights reserved. |
| Original Filename |
|
| Product Name |
|
| Product Version |
|
Digital Signatures
Digital Signatures
This section lists digital signatures that are attached to samples within this family. When analyzing and verifying digital signatures, it is important to confirm that the signature’s root authority is a well-known and trustworthy entity and that the status of the signature is good. Malware is often signed with non-trustworthy “Self Signed” digital signatures (which can be easily created by a malware author with no verification). Malware may also be signed by legitimate signatures that have an invalid status, and by signatures from questionable root authorities with fake or misleading “Signer” names.| Signer | Root | Status |
|---|---|---|
| Acronis International GmbH | DigiCert EV Code Signing CA (SHA2) | Hash Mismatch |
| Acronis International GmbH | GlobalSign CodeSigning CA - G3 | Hash Mismatch |
| Icons8 LLC | Sectigo Public Code Signing CA EV R36 | Hash Mismatch |
| Sugar Sweet Apps | Sectigo Public Code Signing Root R46 | Hash Mismatch |
File Traits
- CryptUnprotectData
- golang
- HighEntropy
- InnoSetup Installer
- Installer Manifest
- Installer Version
- x86
Block Information
Block Information
During analysis, EnigmaSoft breaks file samples into logical blocks for classification and comparison with other samples. Blocks can be used to generate malware detection rules and to group file samples into families based on shared source code, functionality and other distinguishing attributes and characteristics. This section lists a summary of this block data, as well as its classification by EnigmaSoft. A visual representation of the block data is also displayed, where available.| Total Blocks: | 15,775 |
|---|---|
| Potentially Malicious Blocks: | 72 |
| Whitelisted Blocks: | 14,357 |
| Unknown Blocks: | 1,346 |
Visual Map
? - Unknown Block
x - Potentially Malicious Block
Similar Families
Similar Families
This section lists other families that share similarities with this family, based on EnigmaSoft’s analysis. Many malware families are created from the same malware toolkits and use the same packing and encryption techniques but uniquely extend functionality. Similar families may also share source code, attributes, icons, subcomponents, compromised and/or invalid digital signatures, and network characteristics. Researchers leverage these similarities to rapidly and effectively triage file samples and extend malware detection rules.- Banker.TH
- Brute.PVE
- Delf.XB
- Estemani.A
- Filecoder.XG
Show More
- IPStorm.A
- Injector.FHBH
- Injector.GSD
- Injector.KFAD
- Injector.KZP
- Injector.XN
- Lokibot.G
- Lumma.DA
- Lumma.ME
- Trojan.Agent.Gen.ZW
Windows API Usage
Windows API Usage
This section lists Windows API calls that are used by the samples in this family. Windows API usage analysis is a valuable tool that can help identify malicious activity, such as keylogging, security privilege escalation, data encryption, data exfiltration, interference with antivirus software, and network request manipulation.| Category | API |
|---|---|
| Network Winsock2 |
|
