File scan report
Verdict Suspicious
Is Prime X- 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.
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 59 flagged
- Flagged 2
- No detection 57
- No result 16
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
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.
What We Detected
APEX and Bkav flagged the executable, producing 2 detections among 75 engines. Both detections are generic and less reliable; no major antivirus engines identified malware or agreed on a family. The file is unsigned and has no established publisher history.
Threat Behavior
One completed sandbox recorded activity mapped to T1055 (Process Injection), T1485 (Data Destruction), and T1486 (Data Encrypted for Impact). The sample contacted 172.67.153.93 and 162.159.36.2 directly; their reputation was not completely cross-checked. Ten dropped files were inspected without a malicious child finding, but all ten remained unclassified.
What To Do Now
Do not run the file on a production system until its origin and expected behavior are confirmed with the developer or distribution channel. Keep security software enabled, and if testing is necessary, use an isolated virtual machine without sensitive credentials or valuable data.
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.
- Only 2/59 engines detected the file, both less reliable
- No major antivirus engines flagged it and no family consensus
- No sandbox returned a malicious verdict
- No dropped file is known to be malicious across 10 inspected children
- YARAify, CIRCL, and MalwareBazaar returned no hits
- Unsigned Win32 executable with no verified publisher history
- Sandbox mapping to process injection
- Sandbox mappings to and T1486
- Direct contacts to two IP addresses without a complete reputation check
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.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
PrimeX-GUI.exe
cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
PrimeX-GUI.exe
"C:\Users\<USER>\Desktop\PrimeX-GUI.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
cmd.exe
C:\Windows\system32\cmd.exe /c "ver"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- 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 - 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 - +1 more recorded observation
- 1
Network
Hosts contacted
- 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.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
12MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1202
- T1485
- T1486· File encryption
- T1574· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
PrimeX-GUI.exe"C:\Users\<USER>\Desktop\PrimeX-GUI.exe"cmd.exeC:\Windows\system32\cmd.exe /c "ver"PrimeX-GUI.exe"C:\Users\user\Desktop\PrimeX-GUI.exe"
Network contacts
11 host, listed as 1 address. Links show the host and path only.
- IP address
172.67.153.93
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_avif.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imaging.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingcms.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingft.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingmath.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingtk.cp314-win_amd64.pyd
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_webp.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\VCRUNTIME140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\VCRUNTIME140_1.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_asyncio.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_bz2.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_cffi_backend.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_ctypes.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_decimal.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\_elementtree.pyd - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\ada92cb5d92a588d1b93__mypyc.cp314-win_amd64.pyd - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\base.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\os.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\ospath.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\tempfile\temptypes.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\tempfile\__init__.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\tempfile - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\threadpool\binary.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\threadpool\text.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\threadpool\utils.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\threadpool\__init__.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\threadpool - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\__init__.py - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles-25.1.0.dist-info\INSTALLER
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
Global\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost - VM process
lsass.exeC:\Windows\system32\lsass.exe
Show all 9 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache. 9 have no saved verdict and were not checked; that is missing coverage, not a finding.
- d8bd3032b72992a81661…1e912aNot checkedno saved verdict
- d823c0e3b54035d08703…5f1105Not checkedno saved verdict
- dff90929dbeb9d51eebf…5a96fdNot checkedno saved verdict
- 93c3ca5a3e7119897be9…c79bceNot checkedno saved verdict
- a7b3d6e462d338744694…1d0d9eNot checkedno saved verdict
- 79208042672ff0b9e366…036593Not checkedno saved verdict
- f4d851381d1bd937753b…d45198Not checkedno saved verdict
- 052ad6a20d375957e82a…5027f4Not checkedno saved verdict
- dc6db118862ab3298e55…aa098aNot checkedno saved verdict
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.
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
Antivirus consensus
2 of 59 engines flagged this file
16 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-19 engines0flagged
- Tier-235 engines0flagged
- Low-trust15 engines2flagged
View all 75 engine results
- APEXMalicious: Malicious
- BkavMalicious: W32.Malware.5CE28D74
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetNo result
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32No result
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingNo result
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosNo result
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroNo result
- TrendMicro-HouseCallNo result
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
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?
What is PrimeX-GUI.exe?
How many antivirus engines detected PrimeX-GUI.exe?
I already downloaded and ran PrimeX-GUI.exe — what should I do?
What is the SHA-256 hash of PrimeX-GUI.exe?
How up to date is this analysis of PrimeX-GUI.exe?
Community
Member reviews and reports for this exact file hash.