File scan report

Verdict Suspicious

Analyzed , 17 days ago

Is UniTracker_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.

Don't run it until you know where it came from

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

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

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
FileUniTracker_Latest.exe17.1 MBSHA-256 5c4c73c959fd…273399
  • Code signing Unsigned
  • Test run Completed
  • First seen 2mo ago
2 of the 66 antivirus engines that checked it flag it, including APEX and Trapmine.

Chapter 02

Why we think so

3 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

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.

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.

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.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 5: FileSeen in the test run

      UniTracker_Latest.exe

      5c4c73c959fd8df79324eacda726b5c1c6fee54f76570ec6f010f2ec1f273399

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 5: ProcessSeen in the test run

      UniTracker_Latest.exe

      "C:\Users\<USER>\Desktop\UniTracker_Latest.exe"

      Test run
    2. 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
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. 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
    2. 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
    3. +1 more recorded observation

5 facts from the test run. See the full activity list.

Chapter 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 2 of 66 engines flagged it · 9 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteCombined summary: clean verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete1 contacted host checked
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is UniTracker_Latest.exe safe, or is it malware?
UniTracker_Latest.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 2 of the 66 antivirus engines that checked it flag it. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is UniTracker_Latest.exe?
UniTracker_Latest.exe is a Windows program, about 17.1 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Aug 24, 2026.
How many antivirus engines detected UniTracker_Latest.exe?
2 of the 66 antivirus engines that checked it flag UniTracker_Latest.exe, including APEX and Trapmine. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already ran UniTracker_Latest.exe?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of UniTracker_Latest.exe?
The SHA-256 fingerprint of UniTracker_Latest.exe is 5c4c73c959fd8df79324eacda726b5c1c6fee54f76570ec6f010f2ec1f273399, and its MD5 is 21afa6e706f9c0e19a86ee8dd683c4d6. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of UniTracker_Latest.exe?
This report reflects the scan on Oct 9, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.