Trojan.Agent.OCJ
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: | October 29, 2026 |
| Last Seen: | November 20, 2026 |
| OS(es) Affected: | Windows |
Trojan.Agent.OCJ is a Windows Trojan with a danger level of 8 out of 10. Trojans pose as legitimate or harmless programs, or arrive hidden inside them, and then carry out malicious actions without the user's knowledge. This detection was first seen on 2026-10-29 and most recently on 2026-11-20. Only one detection is recorded in the feed data, so the available information is limited.
Table of Contents
What the threat does
According to the feed description, Agent.OCJ installs itself stealthily and runs silently in the background while performing malicious functions. After installation it may give attackers complete control over the infected system. It may also covertly delete files and install additional malware. The description is truncated, so further capabilities are not listed here.
The analyzed sample is a 64-bit native Windows executable with a graphical subsystem. It is not packed and has no digital signature. Its version information presents it as "Modern Manager" from "Proximal Collective," with the original filename setup.exe. Details like these can be chosen freely by an attacker, so a professional-looking name does not make a file trustworthy. The sample also has an exports table and is flagged as high entropy. All 61 analyzed code blocks were classed as potentially malicious, and none were whitelisted.
The sample uses low-level system calls from ntdll.dll, including ones for writing files, querying and freeing memory, and querying process information. Programs that call these functions directly can be hard for some security tools to observe. By themselves, though, these calls do not prove malicious intent, since normal software also uses them.
How it usually gets onto computers
The feed says Agent.OCJ most often spreads in these ways:
- Exploiting system vulnerabilities and security flaws.
- Software downloads from malicious websites.
- Email attachments from untrusted sources, typically .exe, .pif, .avi, and even .jpg files.
The sample's original filename, setup.exe, suggests it may be disguised as an installer. That is typical of Trojans, but the feed does not confirm how this specific file was distributed.
Risks for the user
- Loss of control: attackers may gain full access to the system.
- Data loss: files may be deleted without your knowledge.
- More infections: additional malware may be installed.
- Privacy and security exposure: typical of Trojans with remote access, though the feed does not specify exactly what data is targeted.
Signs of infection
The threat is designed to run silently, so obvious symptoms may be absent. Typical warning signs for Trojans of this kind include:
- Unexpected programs, especially something named "Modern Manager" that you did not install.
- Files that go missing without explanation.
- Sluggish performance or unusual disk and network activity.
- Security settings that change on their own.
- Unfamiliar software appearing after running a downloaded setup.exe.
The absence of symptoms does not mean a system is clean.
How to stay protected
- Keep Windows and all installed software updated, since the threat can exploit known vulnerabilities.
- Download software only from the vendor's official website, and avoid unfamiliar download sites.
- Do not open attachments from unknown senders. Be suspicious of image or video files that are actually executables, and enable the display of full file extensions in Windows.
- Be cautious with unsigned installers. This sample had no digital signature.
- Use a reputable, up-to-date security solution and run regular full system scans.
- Back up important files to a location that is not permanently connected to your computer.
If you suspect infection, disconnect the computer from the internet, run a full scan with an up-to-date anti-malware tool, and remove anything detected. Afterward, change important passwords from a clean device. If the system was possibly under remote control, consider restoring it from a known clean backup or reinstalling Windows.
Analysis Report
General information
| Family Name: | Trojan.Agent.OCJ |
|---|---|
| Signature status: | No Signature |
Known Samples
Known Samples
This section lists other file samples believed to be associated with this family.|
MD5:
061f264efaa6489cd929be28ecf8760a
SHA1:
7166f27566e8b7d7457b80b5235b61cc963cd2a7
SHA256:
2DB0B3D12A74AC3EAC5A8D20C68840F4393A1BF0256E62EB94728FEC0F57314C
File Size:
757.76 KB, 757760 bytes
|
Windows Portable Executable Attributes
- File doesn't have "Rich" header
- File doesn't have security information
- File has exports table
- 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)
- 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 |
|---|---|
| Company Name | Proximal Collective |
| File Description | Modern Manager |
| File Version | 2.5.2984.10 |
| Legal Copyright | 2026 Proximal Collective |
| Original Filename | setup.exe |
| Product Name | Modern Manager |
| Product Version | 2.5.2984.10 |
File Traits
- dll
- HighEntropy
- Installer Version
- 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: | 61 |
|---|---|
| Potentially Malicious Blocks: | 61 |
| Whitelisted Blocks: | 0 |
| 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.- Trojan.Agent.Gen.HCU
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 36 more
|