Is officedeploymenttool_20228-20124.exe safe?
Microsoft-signed Office Deployment Tool with zero detections and strong signer history.
All 75 engines returned clean. The file is signed by Microsoft Corporation, a trusted publisher, and matches four prior safe verdicts under the same signer. Prevalence is common_new with hundreds of submissions.
92a3cbd56191533e36…c870893681e0d4Recommended 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 engines returned clean. The file is signed by Microsoft Corporation, a trusted publisher, and matches four prior safe verdicts under the same signer. Prevalence is common_new with hundreds of submissions.
Zero malicious detections across 75 reporting engines, including 16 tier-1 engines, eliminates any engine-based threat signal. The verified Microsoft signature and 10/11 historical safe samples for this signer provide strong authenticity evidence. Four of five similar-hash records under the same signer also returned safe verdicts with the benign-signed-installer reason code. The single dissenting similar-hash entry is a different file type flagged by external CIRCL data, not relevant to this binary. The file is widely distributed (common_new) and shows no sandbox malice or malicious children.
What We Detected
75 antivirus engines scanned the 3.5 MB executable; none flagged it malicious or suspicious. The binary carries a valid, verified code-signing certificate issued to Microsoft Corporation. Sandbox execution produced only ambient system queries and two MITRE techniques (T1134, T1547.001) commonly seen in legitimate installers.
Threat Behavior
no complete contacted-host reputation result was available, IPs, or URLs were contacted. One child file was dropped and inspected; it received no malicious verdict. No persistence mechanisms or offensive tooling were observed.
What To Do Now
The file can be executed if obtained from an official Microsoft source. Keep Windows Defender and other endpoint protection enabled; no disabling is required or recommended.
Where this verdict could be wrong1 caveat
- One similar-hash entry (44422e6936dc…) returned malicious with reason ai_unavailable:circl_known_malicious, but that file is d3dcompiler_47.dll, not the same binary.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Microsoft Corporation trusted-publisher match
- 4 prior safe verdicts under identical signer
- Zero engine detections across 75 scanners
- Widely distributed (common_new)
Safe to use when downloaded directly from Microsoft; retain endpoint protection.
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
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 flight recorder
Capture complete- 1isolated sandbox run
- 14MITRE ATT&CK techniques
- 2spawned processes
- 0network contacts
- 3filesystem & mutex artifacts
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
officedeploymenttool_20228-20124.exe
92a3cbd56191533e36bde1c6e4640883c900c00d1b5d43a974c870893681e0d4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\program.exe" /RELAUNCHED
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
OWP2258.tmp
C:\Users\user\AppData\Local\Temp\OWP2258.tmp
04Isolated runtime analysis - Written fileObserved
eula.txt
C:\Users\user\AppData\Local\Temp\OWP2258.tmp\eula.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\user\AppData\Local\Temp\OWP2258.tmp
- C:\Users\user\AppData\Local\Temp\OWP2258.tmp\eula.txt
- C:\Users\user\AppData\Local\Temp\OWP2258.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 97caa43e6e6644a38828…541966Never 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
- 327sources 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 file has a valid code signature from Microsoft Corporation.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 357 times from 327 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: officedeploymenttool_20228-20124.exe — 92a3cbd56191533e36bde1c6e4640883c900c00d1b5d43a974c870893681e0d4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\program.exe" /RELAUNCHED
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: OWP2258.tmp — C:\Users\user\AppData\Local\Temp\OWP2258.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: eula.txt — C:\Users\user\AppData\Local\Temp\OWP2258.tmp\eula.txt
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
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
- officedeploymenttool_20228-20124.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Microsoft Corporation
- Size
- 3.4 MB
- Last analyzed
- Aug 31, 2026, 1:02 PM UTC
92a3cbd56191533e36bde1c6e4640883c900c00d1b5d43a974c870893681e0d4Safety & 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 officedeploymenttool_20228-20124.exe safe?
What is officedeploymenttool_20228-20124.exe?
How many antivirus engines detected officedeploymenttool_20228-20124.exe?
Is officedeploymenttool_20228-20124.exe digitally signed?
What is the SHA-256 hash of officedeploymenttool_20228-20124.exe?
Is it safe to run officedeploymenttool_20228-20124.exe?
How up to date is this analysis of officedeploymenttool_20228-20124.exe?
Community
Member reviews and reports for this exact file hash.