Backdoor.Ruledor.A
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: | 19,961 |
| Threat Level: | 60 % (Medium) |
| Infected Computers: | 20 |
| First Seen: | January 24, 2013 |
| Last Seen: | November 16, 2026 |
| OS(es) Affected: | Windows |
Backdoor.Ruledor.A is a backdoor threat that targets Windows computers. It is rated 6 out of 10 for danger. Backdoors are designed to give an attacker a hidden way into a computer, so the person using the machine may not realize that someone else has access to it.
Table of Contents
What Backdoor.Ruledor.A does
According to the available information, Backdoor.Ruledor.A exploits vulnerabilities in installed programs and bypasses the normal authentication process. This allows attackers to gain remote access to a compromised system while trying to remain undetected. It may also pose as installed software to obtain unauthorized remote access.
Analysis of a sample shows a 32-bit native Windows GUI executable that is not packed and carries no digital signature. It has version information listed as 1, 13, 0, 5. The sample uses Windows networking functions (WinHTTP and WinINet) to open internet connections and URLs, which fits the typical behavior of a backdoor that communicates with a remote server. The sample was also observed modifying files in a folder under Program Files (x86), including an executable inside a newly created folder and a text file named test.txt.
Behavior analysis recorded 312 network-related blocks, of which 93 were flagged as potentially malicious and 219 were whitelisted.
How it usually gets onto computers
The feed says Backdoor.Ruledor.A may disguise itself as installed software, or it may arrive through rootkits, viruses or worms. Beyond that, the feed does not describe a specific delivery method. Backdoors in general typically spread through:
- Fake or bundled software downloads from untrusted sources
- Malicious email attachments or links
- Outdated programs with known security flaws
- Other malware that has already infected the computer
Risks for the user
Once a backdoor is in place, the attacker may be able to control the computer remotely. The feed does not list what Backdoor.Ruledor.A was used for, but backdoors typically allow:
- Theft of personal files, passwords and other sensitive data
- Installation of additional malware
- Use of the computer for other attacks
- Monitoring of user activity
Backdoors work quietly, which makes them hard to notice. The longer one stays on a system, the more time an attacker has to misuse it.
Signs of infection
Because this threat tries to stay hidden, there may be no obvious symptoms. Possible warning signs include:
- An unfamiliar folder or program in the Program Files (x86) directory that you did not install
- Unexpected files, such as stray text files, appearing there
- Unexplained network activity when you are not using the internet
- Slower performance or unexpected changes in system settings
- Security settings or protection tools that have been turned off without your action
These signs can also be caused by unrelated problems, so they are not proof of infection on their own.
How to stay protected
- Keep Windows and all installed programs up to date, since this threat exploits vulnerabilities in installed software.
- Download software only from official, trusted sources.
- Do not open attachments or click links in unexpected emails.
- Use a reputable, up-to-date security solution and run regular full system scans.
- Use a standard user account for daily tasks rather than an administrator account.
- Keep a firewall enabled to limit unwanted connections.
- Back up important files regularly to a location that is not permanently connected to your computer.
If you suspect that your computer is infected, disconnect it from the internet, run a full scan with an updated security tool, and remove anything it flags. Afterwards, change your important passwords from a different, clean device. If the problem persists, consider seeking help from a qualified professional.
Analysis Report
General information
| Family Name: | Backdoor.Ruledor.A |
|---|---|
| Signature status: | No Signature |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
db4cb9ee496b63f5b9380ab80336bae7
SHA1:
8c9d1a44cf17e536af5395dd1022ef679a3e1635
SHA256:
0560CF69A01946F8F5C5925DC8AA8CD09CF4FF044862B96A2BCFEDC838BE1159
File Size:
108.03 KB, 108032 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 is 32-bit executable
- File is either console or GUI application
- File is GUI application (IMAGE_SUBSYSTEM_WINDOWS_GUI)
- File is Native application (NOT .NET application)
- File is not packed
Show 2 more
- IMAGE_FILE_DLL is not set inside PE header (Executable)
- IMAGE_FILE_EXECUTABLE_IMAGE is set inside PE header (Executable Image)
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 |
|---|---|
| File Version | 1, 13, 0, 5 |
| Product Version | 1, 13, 0, 5 |
File Traits
- HighEntropy
- 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: | 312 |
|---|---|
| Potentially Malicious Blocks: | 93 |
| Whitelisted Blocks: | 219 |
| Unknown Blocks: | 0 |
Visual Map
? - Unknown Block
x - Potentially Malicious Block
Files Modified
Files Modified
This section lists files that were created, modified, moved and/or deleted by samples in this family. File system activity can provide valuable insight into how malware functions on the operating system.| File | Attributes |
|---|---|
| c:\program files (x86)\7a0zmhv5\7a0zmhv5.exe | Generic Read,Write Data,Write Attributes,Write extended,Append data,Delete,LEFT 262144 |
| c:\program files (x86)\7a0zmhv5\7a0zmhv5.exe | Generic Write,Read Attributes |
| c:\program files (x86)\test.txt | Generic Write,Read Attributes |
Registry Modifications
Registry Modifications
This section lists registry keys and values that were created, modified and/or deleted by samples in this family. Windows Registry activity can provide valuable insight into malware functionality. Additionally, malware often creates registry values to allow itself to automatically start and indefinitely persist after an initial infection has compromised the system.| Key::Value | Data | API Name |
|---|---|---|
| HKLM\software\wow6432node\7a0zmhv5::676 | RegNtPreCreateKey | |
| HKLM\software\wow6432node\7a0zmhv5::938 | C:\Program Files (x86)\7a0zmhv5 | RegNtPreCreateKey |
| HKLM\software\wow6432node\microsoft\windows\currentversion\run::7a0zmhv5 | C:\Program Files (x86)\7a0zmhv5\7a0zmhv5.exe | RegNtPreCreateKey |
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 Winhttp |
|
| Network Wininet |
|