Is MdOdrMcpFilter.exe safe?
No engine flagged this verified Microsoft-signed executable, and its static structure shows neither packing nor suspicious code entropy.
All 75 antivirus engines avoided flagging the file, including the reporting high-trust products. Its Microsoft Windows signature verifies successfully, the publisher matches Microsoft, and static PE analysis found no packing or suspicious code entropy; however, no completed sandbox run is available.
d65ee81d84ecdaea73…164394417c52dbRecommended 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.
All 75 antivirus engines avoided flagging the file, including the reporting high-trust products. Its Microsoft Windows signature verifies successfully, the publisher matches Microsoft, and static PE analysis found no packing or suspicious code entropy; however, no completed sandbox run is available.
The strongest evidence is complete detection silence: 0 of 75 engines marked the executable malicious or suspicious. The signature verifies as Microsoft Windows and matches the curated Microsoft publisher identity, with no brand conflict detected. Static PE inspection found no identified packer, no high-entropy code, and no suspicious section. No external threat-intelligence source supplied a matching malware family or research rule. Runtime behavior cannot be characterized because behaviour.sandboxCount is zero, and no complete contacted-host reputation result is available.
What We Detected
None of the 75 antivirus engines flagged the executable, and 16 high-trust engines explicitly reported no detection. The file carries a verified Microsoft Windows signature, signing.trustedPublisher.matched is true for Microsoft, and no brand mismatch was detected.
Threat Behavior
Static PE analysis found no identified packer, no high-entropy code, and no suspicious section. Four benign-common MITRE indicators were extracted, but behaviour.sandboxCount=0 means there was no completed runtime observation; contactedHosts was also unavailable, so no complete host-reputation conclusion can be made.
What To Do Now
Use the file only if it came through Microsoft or another trusted Windows distribution channel. Keep endpoint protection enabled and recheck the digital signature if the file was obtained from an unexpected source.
Where this verdict could be wrong3 caveats
- behaviour.sandboxCount=0, so no completed runtime execution supports the static and reputation evidence.
- contactedHosts=null, meaning no completed host-reputation cross-check is available.
- signing.signerStats.found=false, so this exact signer identity has no saved sample-history record despite the verified Microsoft certificate.
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 malicious or suspicious result.
- Verified signature from 'Microsoft Windows'.
- signing.trustedPublisher.matched=true for Microsoft.
- No packing, high-entropy code, or suspicious PE sections.
- No YARAify, MalwareBazaar, or CIRCL match.
- No completed sandbox execution was available.
- No complete contacted-host reputation check was available.
- The file has only three recorded submissions across three sources.
The evidence supports normal use when the executable came from Microsoft or a trusted Windows update channel. Keep security protection enabled and avoid copies obtained from unrelated download sites.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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 behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 3sources 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
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The file has a valid code signature from Microsoft Windows.
ProvenanceObservedSourceCode-signing metadataObserved 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
- MdOdrMcpFilter.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Microsoft Windows
- Size
- 214.1 KB
- Last analyzed
- Sep 8, 2026, 8:00 PM UTC
d65ee81d84ecdaea73f7b2a7f11d09156d7151c3fb412bde43164394417c52dbSafety & 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 MdOdrMcpFilter.exe safe?
What is MdOdrMcpFilter.exe?
How many antivirus engines detected MdOdrMcpFilter.exe?
Is MdOdrMcpFilter.exe digitally signed?
What is the SHA-256 hash of MdOdrMcpFilter.exe?
Is it safe to run MdOdrMcpFilter.exe?
How up to date is this analysis of MdOdrMcpFilter.exe?
Community
Member reviews and reports for this exact file hash.