Is MediaInfo_GUI_26.10_Windows.exe safe?
No antivirus engine detected this executable, and its sandbox run, child inspection, static structure, and available external intelligence produced no corroborated malware finding.
The strongest evidence is the 0/75 engine result, including no detections from 17 tier-1 engines. One sandbox run produced no malicious verdict, and neither static analysis nor external intelligence supplied corroborating malware evidence; however, the executable is unsigned and newly observed, so it should still come from the official publisher channel.
e84193f2c068c67780…9a5b66cd896d6eRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 strongest evidence is the 0/75 engine result, including no detections from 17 tier-1 engines. One sandbox run produced no malicious verdict, and neither static analysis nor external intelligence supplied corroborating malware evidence; however, the executable is unsigned and newly observed, so it should still come from the official publisher channel.
All 75 antivirus engines returned no malicious or suspicious finding, including 17 tier-1 engines. One completed sandbox run did not issue a malicious verdict, although it recorded T1134 among mostly ambient activity. Three dropped files were inspected without a confirmed malicious child, but their individual status remains unknown. Static analysis found neither high-entropy code nor likely packing, and the external-intelligence checks produced no hits. The main limitations are the absent code signature, the file's short observation history, and incomplete reputation coverage for every distinct network contact.
What We Detected
None of 75 antivirus engines flagged the executable, and all 17 reporting tier-1 engines returned no detection. Static PE analysis found no recognized packer, no high-entropy code, and no indication that the file is likely packed. MalwareBazaar, YARAify, and CIRCL supplied no corroborating hit.
Threat Behavior
One completed sandbox run produced no malicious verdict. It recorded T1134, a technique that can involve access-token manipulation, but this appeared alongside 19 benign-common techniques and lacked supporting detections, malicious persistence, or a confirmed malicious child. Three contacted domains were checked without a cached malicious or suspicious result, but the observed IP was not included in that inspection count, so complete host-reputation coverage is unavailable.
What To Do Now
The executable is unsigned and was first observed only one day ago. Obtain it from MediaArea's official release channel, verify the SHA-256 value if the publisher provides one, and keep endpoint protection enabled while installing or running it.
Where this verdict could be wrong5 caveats
- signing.applicable=true but signing.signed=false, so the claimed publisher identity is not authenticated by a code signature.
- T1134 appeared in the sandbox technique list; this token-manipulation technique can be abused, although no malicious sandbox verdict corroborated it.
- The file was first submitted only 1 day ago, limiting the available history despite 47 submitters and 49 submissions.
- The three dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false does not establish that each child is benign.
- similarHashes contains 3 safe and 2 suspicious verdicts, but every match is imphash-only with signerMatchesSubject=false, making these likely installer-framework collisions rather than strong file similarity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported a detection
- All 17 tier-1 engines reported no detection
- No malicious sandbox verdict across 1 completed run
- No confirmed malicious child among 3 inspected hashes
- No high-entropy code, likely packing, or external-intelligence hit
- Unsigned Windows executable despite code signing being applicable
- First observed only 1 day ago
- Sandbox recorded offensive technique T1134
- Three dropped-child verdicts remain unknown
- Host-reputation inspection did not clearly cover the observed IP address
Download the installer only from MediaArea's official release channel and verify its SHA-256 hash when an official checksum is available. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 4 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 20MITRE ATT&CK techniques
- 1spawned processes
- 4network contacts
- 15filesystem & mutex artifacts
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.
- ocsps.ssl.com
- mediaarea.net
- atm.teams.mira.tm.svc.cloud.microsoft
- 45.56.78.187
- HKEY_CURRENT_USER\Software\MediaArea
- HKEY_CURRENT_USER\Software\MediaArea\MediaInfo
- HKEY_CURRENT_USER\Software\MediaArea\MediaInfo\InstallCount
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Microsoft\Windows\History
- C:\Users\user\AppData\Local\Microsoft\Windows\INetCache
- C:\Users\user\AppData\Local\Microsoft\Windows\INetCookies
- C:\Users\user\AppData\Local\Temp
- C:\Users\user\AppData\Local\Temp\nsl59BD.tmp
- C:\Users\user\AppData\Local\Temp\nsr5BB3.tmp
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- 85e03805f90f72257dd4…1dccb9Never scannednever seen before
- 760df89c2341f9c39c02…dc1d8eNever scannednever seen before
- 996645d7f16a6294babb…dc51a5Never 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.
- 0rule hits recorded
- 0 / 75engines flagged
- 47sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 49 times from 47 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: MediaInfo_GUI_26.10_Windows.exe — e84193f2c068c677804924763e4cf9c7bc3d7138482ab174939a5b66cd896d6e
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\MediaInfo_GUI_26.10_Windows.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
File written: Caches — C:\Users\user\AppData\Local\Microsoft\Windows\Caches
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: History — C:\Users\user\AppData\Local\Microsoft\Windows\History
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: ocsps.ssl.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: mediaarea.net — 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 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
- MediaInfo_GUI_26.10_Windows.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 15.0 MB
- Last analyzed
- Oct 7, 2026, 1:07 AM UTC
e84193f2c068c677804924763e4cf9c7bc3d7138482ab174939a5b66cd896d6eSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is MediaInfo_GUI_26.10_Windows.exe safe?
What is MediaInfo_GUI_26.10_Windows.exe?
How many antivirus engines detected MediaInfo_GUI_26.10_Windows.exe?
What is the SHA-256 hash of MediaInfo_GUI_26.10_Windows.exe?
Is it safe to run MediaInfo_GUI_26.10_Windows.exe?
How up to date is this analysis of MediaInfo_GUI_26.10_Windows.exe?
Community
Member reviews and reports for this exact file hash.