Is chrome.exe safe?
No antivirus engine detected malware, and the isolated T1055 mapping lacks completed sandbox corroboration, although the unsigned browser-like executable deserves source verification.
All 75 antivirus engines avoided a malware or suspicious detection, including 16 tier-1 engines that reported no detection. The only notable concern is an uncorroborated T1055 mapping combined with an unsigned executable named chrome.exe; verify that it came from the official software source before running it.
d69623da734b95110f…1eb1296a84d998Recommended 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 a malware or suspicious detection, including 16 tier-1 engines that reported no detection. The only notable concern is an uncorroborated T1055 mapping combined with an unsigned executable named chrome.exe; verify that it came from the official software source before running it.
The strongest evidence is the absence of detections across 75 antivirus engines, with no tier-1 engine identifying a threat family. Static PE analysis also found no likely packing or unusually high-entropy code, and external intelligence produced no matching malware or YARA evidence. A heuristic maps saved evidence to T1055, but there were zero completed sandbox runs, so process injection was not directly observed here. The file is unsigned despite using a browser-like filename, which prevents publisher verification and warrants caution. No complete contacted-host reputation result is available, although the payload records no contacted domains, IPs, or URLs.
What We Detected
None of 75 antivirus engines flagged the executable as malware or suspicious, and 16 tier-1 engines reported no detection. No malware family consensus, confirmed hacktool label, MalwareBazaar match, or YARAify rule match was present. Static PE analysis reports peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false.
Threat Behavior
A saved heuristic maps the file to MITRE T1055, which is associated with process injection. However, behaviour.sandboxCount=0 means no completed runtime observation is available, and the heuristic itself does not establish the injection method or intent. The contacted-host reputation check was not available, so no conclusion about host reputation should be drawn.
What To Do Now
Confirm that the file came directly from the software vendor or another trusted distribution channel. Because signing.signed=false for chrome.exe, avoid replacing an installed browser binary with this copy unless its origin and hash are independently verified, and keep endpoint protection enabled.
Where this verdict could be wrong3 caveats
- T1055 is associated with process injection, an offensive technique, although the saved mapping does not establish the exact method or intent.
- The executable is unsigned despite the chrome.exe filename, so its publisher identity cannot be authenticated.
- contactedHosts=null, meaning no complete host-reputation cross-check is available.
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 antivirus engines reported malware or suspicious content
- 16 tier-1 engines reported no detection
- No tier-1 family consensus or confirmed hacktool label
- No MalwareBazaar or YARAify match
- No packing or high-entropy code indicated
- Unsigned Win32 executable using the browser-like filename chrome.exe
- Uncorroborated MITRE T1055 process-injection mapping
- No completed sandbox runtime observation
- No complete contacted-host reputation cross-check
Verify the download source and hash before execution because the executable is unsigned. Keep endpoint protection enabled and obtain a vendor-signed copy when one is available.
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
Complete1 signature or behavior rule matched.
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.
- 1rule hit recorded
- 0 / 75engines flagged
- 11sources 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
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved 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.
EvidenceT1055 (MITRE)
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
- chrome.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 3.9 MB
- Last analyzed
- Sep 20, 2026, 10:04 PM UTC
d69623da734b95110f8336b9a6e60f6bcad64ec8e8796c738c1eb1296a84d998Safety & 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 chrome.exe safe?
What is chrome.exe?
How many antivirus engines detected chrome.exe?
What is the SHA-256 hash of chrome.exe?
Is it safe to run chrome.exe?
How up to date is this analysis of chrome.exe?
Community
Member reviews and reports for this exact file hash.