File scan report

Verdict Suspicious

Analyzed , 1 month ago

Is PrimeX-GUI.exe safe? Treat it as suspicious.

APEX and Bkav flagged the file, while all participating major antivirus engines remained silent, making a false positive plausible.

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 59 flagged

  • Flagged 2
  • No detection 57
  • No result 16
FilePrimeX-GUI.exe37.0 MBSHA-256 cd14b36286a5…56c536
  • Code signing Unsigned
  • Test run Completed
  • First seen 2mo ago
2 of the 59 antivirus engines that checked it flag it, including APEX and Bkav.

Chapter 02

Why we think so

4 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

Only 2 of the 59 antivirus engines that checked it detected the sample, both from the less reliable tier, and there is no major family consensus. That detection pattern ordinarily favors a false positive. The executable is unsigned, so no verified publisher identity helps explain or contextualize that activity. It also contacted two IP addresses directly, but no complete host-reputation result is available. With no malicious child, external-intelligence match, or sandbox verdict corroborating malware, the evidence remains materially mixed rather than conclusive.

Where this verdict could be wrong4 caveats
  • The fact that only less reliable engines flagged it and the absence of major detections make the two generic detections likely false positives.
  • No sandbox returned a malicious verdict, so the completed sandbox did not independently assign a malicious result.
  • droppedChildren inspected 10 files and found hasMaliciousChild=false, although all ten child verdicts remained unknown.
  • YARAify returned zero rules and CIRCL returned no hit, but absence of external matches does not exclude previously uncatalogued threats.

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 · 5 complete · 1 partial. 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
  • 12sandbox rule tags
  • 3spawned processes
  • 1network contact
  • 31filesystem & 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).

  • 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: Talked to servers over the internet during the test run.

  • 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: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

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 6: FileSeen in the test run

      PrimeX-GUI.exe

      cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536

      Uploaded file
  2. Processes

    What ran

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

      PrimeX-GUI.exe

      "C:\Users\<USER>\Desktop\PrimeX-GUI.exe"

      Test run
    2. Evidence 3 of 6: ProcessSeen in the test run

      cmd.exe

      C:\Windows\system32\cmd.exe /c "ver"

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 6: Written fileSeen in the test run

      _avif.cp314-win_amd64.pyd

      C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_avif.cp314-win_amd64.pyd

      Test run
    2. Evidence 5 of 6: Written fileSeen in the test run

      _imaging.cp314-win_amd64.pyd

      C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imaging.cp314-win_amd64.pyd

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    1
    1. Evidence 6 of 6: Contacted hostSeen in the test run

      172.67.153.93

      Contacted during the test run.

      Test run

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

Chapter 04

Technical details

2 of the 59 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 2 of 59 engines flagged it · 16 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 host contacted in the test run had no completed reputation check Details for contacted hosts
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
  • BkavW32.Malware.5CE28D74

File fingerprint

Last analyzed
Sep 12, 2026, 12:16 PM UTC
SHA-256
cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536
SHA-1
e4f5824a4ddd19d680546c8c4c9b152c0d1e35bf
MD5
1d71db36460af6e0adebb554b5030b5b

About this file

PrimeX-GUI.exe is a Win32 EXE file of 37.0 MB.

Type and size
Win32 EXE · 37.0 MB
Signer
UnsignedNo code signature.
First seen
Jul 31, 2026On VirusTotal.
Submitted by
22 distinct sources
Packer
None detected
Entropy
8.00 of 8

First scanned

Chapter 05

Questions & answers

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

Is PrimeX-GUI.exe safe, or is it malware?
PrimeX-GUI.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 2 of the 59 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 PrimeX-GUI.exe?
PrimeX-GUI.exe is a Windows program, about 37.0 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Jul 31, 2026.
How many antivirus engines detected PrimeX-GUI.exe?
2 of the 59 antivirus engines that checked it flag PrimeX-GUI.exe, including APEX and Bkav. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and ran PrimeX-GUI.exe — what should I do?
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 PrimeX-GUI.exe?
The SHA-256 fingerprint of PrimeX-GUI.exe is cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536, and its MD5 is 1d71db36460af6e0adebb554b5030b5b. 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 PrimeX-GUI.exe?
This report reflects the scan on Sep 12, 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.