File scan report
Verdict Suspicious
Is Uni Tracker_ Latest. exe safe? Treat it as suspicious.
Only two less reliable engines raised generic alerts, but the unsigned, rarely seen executable also produced unresolved and runtime mappings.
Read the whole reasonShow less
Why Suspicious? 2 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
2 of 66 flagged
- Flagged 2
- No detection 64
- No result 9
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
APEX and Trapmine were the only 2 of the 66 antivirus engines that checked it to flag the executable, and no major antivirus engines detected it. That strongly suggests false positives, but the lack of a signature, very limited distribution, and unresolved process-injection and token-manipulation mappings warrant caution until its source is verified.
Only 2 of the 66 antivirus engines that checked it flagged the sample, both with generic less reliable labels, while no major antivirus engines detected it. One completed sandbox run returned clean, and the recorded network contacts were analysis-environment background traffic rather than sample activity. The executable is unsigned and has appeared from only one source, leaving weak provenance. Similar-file history is mixed, but every match relies solely on a shared import-table fingerprint without a matching signer, so it cannot reliably identify this program.
What We Detected
APEX and Trapmine flagged the file, accounting for 2 of the 66 antivirus engines that checked it. MalwareBazaar and YARAify supplied no corroborating hit.
Threat Behavior
One completed sandbox run returned clean. It mapped activity to T1055 process injection and T1134 access-token manipulation, but the evidence names no injected process and shows no persistence indicator. The domain and IP recorded during analysis are both marked as sandbox background contacts, not sample-generated traffic; the host-reputation check covered the sole distinct host and found no known malicious or suspicious entry.
Context and Limitations
The executable has no digital signature and has been submitted only twice from one source, so its publisher and origin lack strong assurance. Two dropped files have no saved decisions, which is missing coverage rather than evidence against the parent. Similar files have mixed outcomes, but all share only an import-table fingerprint without a signer match, a weak comparison that can reflect a common installer framework.
What To Do Now
Verify the download against a checksum or release supplied through the developer's official channel before running it. If its origin cannot be confirmed, quarantine it and test it only in an isolated environment while keeping security software enabled.
Where this verdict could be wrong2 caveats
- The completed sandbox run returned clean and identified no injected process or persistence indicator.
- The file is unsigned and scarcely distributed, so its publisher and origin cannot be independently established.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 2 of the 66 antivirus engines that checked it raised alerts, and both were generic less reliable detections.
- No major antivirus engines detected the file.
- The completed sandbox run returned clean and identified no injected target process or persistence.
- The observed network contacts were attributed to the analysis environment, and the covered host had no known malicious or suspicious reputation.
- No malware-specific external research rule or known malware-repository match was found.
- The executable is unsigned, so no authenticated publisher can be established.
- It has been observed from only one source and has very limited submission history.
- The test run mapped possible process injection and access-token manipulation.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 17sandbox rule tags
- 5spawned processes
- 0network contacts
- 14filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
UniTracker_Latest.exe
5c4c73c959fd8df79324eacda726b5c1c6fee54f76570ec6f010f2ec1f273399
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
UniTracker_Latest.exe
"C:\Users\<USER>\Desktop\UniTracker_Latest.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
UniTracker_Latest.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-3ORL4.tmp\UniTracker_Latest.tmp" /SL5="$F014A,16282726,780288,C:\Users\<USER>\Desktop\UniTracker_Latest.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
UniTracker_Latest.tmp
C:\Users\<USER>\AppData\Local\Temp\is-3ORL4.tmp\UniTracker_Latest.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 17 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
2 of the 66 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
- APEXMalicious
- Trapminesuspicious.low.ml.score
File fingerprint
- Last analyzed
- Oct 9, 2026, 2:10 PM UTC
- SHA-256
5c4c73c959fd8df79324eacda726b5c1c6fee54f76570ec6f010f2ec1f273399- SHA-1
0fcc45bde56e79f4e967a4308824963a3ac25980- MD5
21afa6e706f9c0e19a86ee8dd683c4d6
About this file
UniTracker_Latest.exe is a Win32 EXE file of 17.1 MB.
- Type and size
- Win32 EXE · 17.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 24, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.28 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is UniTracker_Latest.exe safe, or is it malware?
What is UniTracker_Latest.exe?
How many antivirus engines detected UniTracker_Latest.exe?
What should I do if I already ran UniTracker_Latest.exe?
What is the SHA-256 hash of UniTracker_Latest.exe?
How up to date is this analysis of UniTracker_Latest.exe?
Community
Member reviews and reports for this exact file hash.