Trojan.Amadey.L
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.
| Threat Level: | 80 % (High) |
| First Seen: | August 7, 2026 |
| Last Seen: | November 16, 2026 |
| OS(es) Affected: | Windows |
Trojan.Amadey.L is a Windows Trojan with a danger level of 8 out of 10. Trojans pose as something harmless or useful while carrying out harmful actions in the background. According to the data we hold, this threat was first seen on 2026-08-07 and most recently on 2026-11-16. Only one detection has been recorded so far, but a low count does not make the threat harmless.
Table of Contents
What the threat does
Amadey.L installs itself stealthily and runs silently in the background, so you may not notice anything while it works. Once it is on a system, it may give attackers complete control over the computer. It may also covertly delete files and install additional malware. Trojans of this kind typically also collect personal information, although the available data for this threat does not list every function.
Technical analysis of the sample shows the following:
- It is a 64-bit native Windows program, not a .NET application, with a graphical (GUI) subsystem.
- It is not packed and carries no digital signature.
- It has no debug information and no exports table.
- It makes low-level system calls through the Windows core library. These include writing to files, querying process and token information, opening registry keys, and managing memory. Such calls are typical of programs that want to work close to the operating system.
- Of 165 analyzed code blocks, 135 were flagged as potentially malicious and 30 were whitelisted. None were unknown.
The sample also carries version information that describes it as a document converter utility. Attackers often disguise malware as ordinary software this way, and this information can be copied or forged. A professional-looking description is not proof that a file is safe.
How it usually gets onto computers
Amadey.L usually installs itself without the user's knowledge. The main routes are:
- Exploiting vulnerabilities: it takes advantage of security flaws in the system or in installed software.
- Malicious downloads: software downloaded from untrustworthy websites may carry it.
- Email attachments: messages from untrusted senders may include files with .exe, .pif, .avi or even .jpg extensions. Media or image extensions can be used to make a dangerous file look harmless.
Risks for the user
- Loss of control over your computer to a remote attacker.
- Deletion or damage of personal files.
- Installation of further malware, which can multiply the damage.
- Possible theft of personal data such as saved logins and financial details. This is typical Trojan behavior, so treat your accounts as exposed if you are infected.
Signs of infection
Because the threat runs silently, signs may be subtle or absent. Trojans of this type typically cause some of the following:
- Unexplained slowdowns or high resource use.
- Unfamiliar programs or processes you did not install.
- Files that go missing or change without explanation.
- Unusual network activity.
- Security settings that have been changed or switched off.
- Account activity you do not recognize, such as password reset notices or unexpected logins.
How to stay protected
- Keep Windows and all your software up to date, since exploiting flaws is a main infection route.
- Download programs only from official, trusted sources, and be wary of "free converter" or utility tools from unknown sites.
- Do not open attachments from unknown or unexpected senders. Be especially careful with executable files, or with images and videos that behave like programs.
- Check file extensions. Enable the display of full file names in Windows so a disguised file stands out.
- Use a reputable, up-to-date security solution and run full system scans regularly.
- Back up important files to a location that is not permanently connected to your computer.
- If you suspect an infection, disconnect from the internet, run a full scan with a trusted anti-malware tool, and change your passwords from a clean device afterward.
Acting quickly matters with a threat that can hand control of your system to someone else. If you are unsure whether a file is safe, do not run it.
Analysis Report
General information
| Family Name: | Trojan.Amadey.L |
|---|---|
| Signature status: | No Signature |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
03cf12e59fbfc1184024d0e43a33fcf8
SHA1:
781a916d85dff5758b99ec0019c2d9a8c2781001
SHA256:
0DF5989FF7B32617CEB0A8D771770406732653452FC64C77A3FBC951C4A94837
File Size:
2.93 MB, 2931374 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 security information
- File is 64-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
- IMAGE_FILE_DLL is not set inside PE header (Executable)
Show 1 more
- 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 |
|---|---|
| Company Name | Quilltree Solutions Ltd |
| File Description | NoteLedge Companion - document converter |
| Anion | OriginalFilename |
| I | l |
| L Copyright | (c) 2026 Quilltree Solutions Ltd |
| Uct Name | NoteLedge Companion |
File Traits
- GetConsoleWindow
- ntdll
- x64
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: | 165 |
|---|---|
| Potentially Malicious Blocks: | 135 |
| Whitelisted Blocks: | 30 |
| Unknown Blocks: | 0 |
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.- Amadey.L
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 |
|---|---|
| Syscall Use |
Show 32 more
|