Is PrimeX-GUI.exe safe?
Only two low-trust engines detected this unsigned executable, but process-injection, LSASS-targeting, destructive-technique, and unchecked direct-IP activity warrant caution.
APEX and Bkav flagged the file, while all participating high-trust engines remained silent, making a false positive plausible. However, one sandbox recorded process-injection and destructive-technique mappings, apparent LSASS targeting, and two direct-IP contacts whose reputation was not checked, so execution should be deferred pending source verification.
cd14b36286a5e62ebe…c482526a56c536Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
APEX and Bkav flagged the file, while all participating high-trust engines remained silent, making a false positive plausible. However, one sandbox recorded process-injection and destructive-technique mappings, apparent LSASS targeting, and two direct-IP contacts whose reputation was not checked, so execution should be deferred pending source verification.
Only 2 of 75 engines detected the sample, both from the low-trust tier, and there is no high-trust family consensus. That detection pattern ordinarily favors a false positive. However, the completed sandbox mapped activity to T1055, T1485, and T1486 and surfaced apparent interaction with LSASS, which is more concerning than the generic engine labels alone. 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 low-trust; no high-trust engine 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). A heuristic also associated observed LSASS-related process activity with credential-dumping behavior, although the saved evidence does not prove that LSASS memory was actually read. 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 endpoint protection enabled, and if testing is necessary, use an isolated virtual machine without sensitive credentials or valuable data.
Where this verdict could be wrong4 caveats
- engines.onlyLowTrustFlagging=true and engines.tier1Malicious=0 make the two generic detections likely false positives.
- behaviour.hasMaliciousSandboxVerdict=false, 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/75 engines detected the file, both low-trust
- engines.tier1Malicious=0 and no family consensus
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- YARAify, CIRCL, and MalwareBazaar returned no hits
- Unsigned Win32 executable with no verified publisher history
- Sandbox mapping to T1055 process injection
- Apparent LSASS-targeting activity
- Sandbox mappings to T1485 and T1486
- Direct contacts to two IP addresses without a complete reputation check
Avoid execution until the file is verified against an official source or developer-provided hash. Keep endpoint protection enabled and use an isolated environment if further testing is essential.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 12MITRE ATT&CK techniques
- 11spawned processes
- 2network contacts
- 31filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
PrimeX-GUI.exe
cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\PrimeX-GUI.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_avif.cp314-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imaging.cp314-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.67.153.93
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 172.67.153.93
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_avif.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imaging.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingcms.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingft.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imagingmath.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\ada92cb5d92a588d1b93__mypyc.cp314-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\base.py
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\os.py
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\ospath.py
- C:\Users\<USER>\AppData\Local\Temp\_MEI52682\aiofiles\tempfile\temptypes.py
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- d8bd3032b72992a81661…1e912aNever scannednever seen before
- d823c0e3b54035d08703…5f1105Never scannednever seen before
- dff90929dbeb9d51eebf…5a96fdNever scannednever seen before
- 93c3ca5a3e7119897be9…c79bceNever scannednever seen before
- a7b3d6e462d338744694…1d0d9eNever scannednever seen before
- 79208042672ff0b9e366…036593Never scannednever seen before
- f4d851381d1bd937753b…d45198Never scannednever seen before
- 052ad6a20d375957e82a…5027f4Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- dc6db118862ab3298e55…aa098aNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 2 / 75engines flagged
- 22sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
2 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 22 times from 22 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: PrimeX-GUI.exe — cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\PrimeX-GUI.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _avif.cp314-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_avif.cp314-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp314-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI52682\PIL\_imaging.cp314-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 172.67.153.93 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence172.67.153.93 · 162.159.36.2
2 of 75 engines flagged this file
View all 75 engine results
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.
Fingerprint and provenance
- File name
- PrimeX-GUI.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 35.2 MB
- Last analyzed
- Sep 12, 2026, 12:16 PM UTC
cd14b36286a5e62ebe53809dbebebd86fddc806205efaf7e96c482526a56c536Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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?
How do I remove PrimeX-GUI.exe?
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.