Is OpenPrestige.exe safe?
Twenty-one of 75 engines flagged this unsigned, packed executable, while runtime injection indicators and 12 researcher YARA matches strongly corroborate harmful activity.
The file drew 21 detections among 75 engines, including five high-trust detections, and it is unsigned and packed. Runtime evidence includes process-injection techniques and root-certificate installation, while 12 researcher YARA rules add substantial independent corroboration; avoid running it.
94d15295e9aff51602…ad488d73f0a561Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
The file drew 21 detections among 75 engines, including five high-trust detections, and it is unsigned and packed. Runtime evidence includes process-injection techniques and root-certificate installation, while 12 researcher YARA rules add substantial independent corroboration; avoid running it.
Five high-trust engines are among the 21 of 75 engines that detected the sample, although their labels do not establish a single specific family. The executable is unsigned and has high-entropy packed code, increasing concern when combined with the detection volume. Runtime evidence maps to process injection, archive collection, defense impairment, and reflective code loading techniques. It also invoked certutil to install a mitmproxy certificate into the machine root store, an unusually sensitive system modification. Twelve researcher YARA rules matched, including rules for script injection and debugger checks, strongly reinforcing the engine and runtime evidence. The observed IP contact lacks a completed host-reputation cross-check and is therefore not treated as confirmed command-and-control.
What We Detected
Twenty-one of 75 antivirus engines flagged OpenPrestige.exe, including five high-trust engines. Microsoft identified Wacatac, Avast and AVG reported FileRepMalware, and Symantec returned a high-confidence machine-learning detection. The executable is unsigned, recently observed, and contains high-entropy code assessed as likely packed.
Threat Behavior
The completed runtime observation mapped activity to T1055 and T1055.003 process injection, T1560 archive collection, T1562.001 defense impairment, and T1620 reflective code loading. The file also launched certutil to add mitmproxy-ca-cert.cer to the Windows root certificate store, which could enable interception of encrypted traffic. Twelve researcher YARA rules matched, including CP_Script_Inject_Detector and DebuggerCheck__API. One external IP was contacted, but no complete host-reputation result is available because the contacted-host check was not saved.
What To Do Now
Do not execute the file. If it has already run, keep endpoint protection enabled, disconnect the affected system from sensitive networks, perform a full security scan, inspect the Windows root certificate store for the added mitmproxy certificate, and review running processes and credentials used on the machine.
Where this verdict could be wrong4 caveats
- engines.tier1FamilyConsensus.strong=false; the five tier-1 detections do not converge on one named malware family.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox did not itself issue a malicious verdict.
- droppedChildren.hasMaliciousChild=false, but all six inspected children have unknown verdicts rather than confirmed clean results.
- 11 of 17 tier-1 engines reported no detection, including BitDefender, ESET-NOD32, and Avira.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- brandMismatch.detected was not reported
- 11 tier-1 engines reported no detection
- 21/75 antivirus detections, including five high-trust engines
- Unsigned Win32 executable
- High-entropy code assessed as likely packed
- Runtime evidence mapped to T1055 and T1055.003 process injection
- Installed mitmproxy-ca-cert.cer into the Windows root certificate store
- 12 researcher YARA rules matched
Quarantine or remove the file and do not run it. If execution occurred, keep security protection enabled and investigate the root certificate store, running processes, persistence, and exposed credentials.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete21 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete10 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
- 33MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 14filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
OpenPrestige.exe
94d15295e9aff5160291a4980fdf4a1b4b32f74d30f979a9a3ad488d73f0a561
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\0bv8wmr.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"certutil.exe" -addstore -f Root "C:\Users\<USER>\AppData\Local\Temp\mitmproxy-ca-cert.cer"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Inter.ttf
C:\Users\<USER>\AppData\Local\OpenPrestige\Inter.ttf
04Isolated runtime analysis - Written fileObserved
Tmp3265.tmp
C:\Users\<USER>\AppData\Local\Temp\Tmp3265.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- HKEY_LOCAL_MACHINE\Software\Microsoft\SystemCertificates\Root\Certificates\936CDBA49963307FC509C72CD04E8D0CE0F7DADC\Blob
- C:\Users\<USER>\AppData\Local\OpenPrestige\Inter.ttf
- C:\Users\<USER>\AppData\Local\Temp\Tmp3265.tmp
- C:\Users\<USER>\AppData\Local\Temp\Tmp337F.tmp
- C:\Users\<USER>\AppData\Local\Temp\mitmproxy-ca-cert.cer
- C:\Users\<USER>\AppData\Local\Temp\Tmp41B9.tmp
- OpenPrestige_SingleInstance_Mutex
- \Sessions\1\BaseNamedObjects\OpenPrestige_SingleInstance_Mutex
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- ae6e4df81e495601fd91…b3748aNever scannednever seen before
- 66958b31ab05b82fecd6…fe0f6aNever scannednever seen before
- ac015e1048b7729cd1e0…1d6a82Never scannednever seen before
- 29160a80ff49ddcab2c9…559031Never scannednever seen before
- 7dce6442311f6a651081…0d319cNever scannednever seen before
- 65327c8bf37f3d064bd1…78837fNever 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.
- 10rule hits recorded
- 21 / 75engines flagged
- 190sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
7 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
21 of 75 antivirus engines flagged the file, including APEX and Avast.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 12 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: OpenPrestige.exe — 94d15295e9aff5160291a4980fdf4a1b4b32f74d30f979a9a3ad488d73f0a561
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\0bv8wmr.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "certutil.exe" -addstore -f Root "C:\Users\<USER>\AppData\Local\Temp\mitmproxy-ca-cert.cer"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Inter.ttf — C:\Users\<USER>\AppData\Local\OpenPrestige\Inter.ttf
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Tmp3265.tmp — C:\Users\<USER>\AppData\Local\Temp\Tmp3265.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- CP_Script_Inject_Detector
- DebuggerCheck__API
- dependsonpythonailib
- DetectEncryptedVariants
- golang_bin_JCorn_CSC846
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.
Evidence"C:\Users\<USER>\Desktop\0bv8wmr.exe"PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencepackers: Microsoft Visual C++ vx.x DLLAt least one AV engine labelled this sample as anti-VM / anti-debug / sandbox-evading. These techniques are specifically designed to bail out when the sample notices it's being analysed.
EvidencePUA.Win64.VMDetectThe 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.
Evidence162.159.36.2Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence162.159.36.2
21 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- OpenPrestige.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 34.8 MB
- Last analyzed
- Oct 1, 2026, 12:21 PM UTC
94d15295e9aff5160291a4980fdf4a1b4b32f74d30f979a9a3ad488d73f0a561Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is OpenPrestige.exe a virus?
What is OpenPrestige.exe?
How many antivirus engines detected OpenPrestige.exe?
What should I do if I already ran OpenPrestige.exe?
How do I remove OpenPrestige.exe?
What kind of malware is OpenPrestige.exe?
What is the SHA-256 hash of OpenPrestige.exe?
How up to date is this analysis of OpenPrestige.exe?
Community
Member reviews and reports for this exact file hash.