Is Update.exe safe?
The verified Discord-signed updater drew 0 detections from 75 engines and is widely prevalent, while imphash-based YARA and behavioral signals merit limited caution.
This appears consistent with a legitimate Discord updater: its Discord Inc. signature verifies, 0 of 75 engines detected malware, and the sample has broad multi-year prevalence. The process-injection mapping and two imphash-based YARA matches are notable, but they are not corroborated by engine detections, a malicious sandbox result, or a malicious dropped child.
739681d4867feb7080…4fcf739c0f7e1aRecommended 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.
This appears consistent with a legitimate Discord updater: its Discord Inc. signature verifies, 0 of 75 engines detected malware, and the sample has broad multi-year prevalence. The process-injection mapping and two imphash-based YARA matches are notable, but they are not corroborated by engine detections, a malicious sandbox result, or a malicious dropped child.
The strongest evidence is the verified Discord Inc. signature and trusted-publisher match, supported by 0 detections among 75 engines. The file has also circulated since 2022 across 1,132 sources, which is consistent with established commercial software rather than a newly introduced impersonator. One completed sandbox recorded techniques including process injection and defense impairment, but it did not issue a malicious verdict and no malicious dropped child was identified. Two YARA rules matched, although both rely on an imphash shared by unrelated executables and do not identify a concrete malware family. The prior similar-file decisions are mixed and lack signer co-matches, making them weak evidence for this specific Discord-signed sample. Host-reputation coverage was incomplete, so the network activity cannot be described as comprehensively cleared.
What We Detected
The executable carries a verified signature from Discord Inc., and the trusted-publisher check matched Discord. None of 75 antivirus engines flagged it, including no tier-1 detections, while the sample has been submitted 1,491 times by 1,132 sources since February 2022.
Threat Behavior
One completed sandbox mapped activity to T1055, T1560, T1562.001, and T1620, including possible process injection and defense impairment. That sandbox did not return a malicious verdict, and none of eight inspected dropped children was identified as malicious, although their individual outcomes remain unknown. Two community YARA rules matched the PE imphash, but imphashes can be shared by unrelated programs built with the same framework. Host-reputation inspection did not cover every domain and IP observed, so no complete network-reputation conclusion is available.
What To Do Now
Confirm that the file came through Discord's normal installation or update channel and that Windows still reports a valid Discord Inc. signature. Keep endpoint protection enabled; if the signature fails locally or the file arrived from an unrelated download source, discard it and obtain a fresh installer from Discord.
Where this verdict could be wrong4 caveats
- Runtime evidence maps activity to T1055, T1560, T1562.001, and T1620, although the single completed sandbox did not issue a malicious verdict.
- YARAify matched two rules, including 'Skystars_Malware_Imphash'; both are based on the broadly shared imphash rather than a named malware family.
- Contacted-host inspection covered only 7 hosts while runtime evidence contains additional IP addresses, so no complete host-reputation result is available.
- All eight dropped children have unknown individual verdicts, although none is currently recorded as a malicious child.
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 detected malware.
- Verified signature from Discord Inc.
- signing.trustedPublisher.matched=true for Discord.
- Established prevalence: 1,132 sources and 1,491 submissions.
- No malicious sandbox verdict or malicious dropped child.
- Runtime mapping includes T1055 process injection.
- Runtime mapping includes T1562.001 defense impairment.
- YARAify matched 2 imphash-based rules.
- The .NET executable is marked likely packed.
- Host-reputation coverage was incomplete.
- Eight dropped children lack individual verdicts.
Use it only if it came through Discord's official installation or update path and the Discord Inc. signature verifies locally. Keep endpoint protection enabled and replace the file if its origin or signature is uncertain.
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
Partial7 of 27 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
- 24MITRE ATT&CK techniques
- 7spawned processes
- 27network contacts
- 24filesystem & 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.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- telemetry-incoming.r53-2.services.mozilla.com
- fp2e7a.wpc.phicdn.net
- prod.ingestion-edge.prod.dataops.mozgcp.net
- www.msftconnecttest.com
- fp2E7A.wpc.2BE4.phicdn.net
- 204.79.197.203
- a83f:8110:0:0:1400:1400:2800:3800
- a83f:8110:182e:d801:beac:bf78:cce1:d301
- 13.107.4.50
- 23.216.147.76
- 192.168.0.54
- 23.216.147.64
- a83f:8110:0:0:100:0:1800:0
- 192.168.0.1
- a83f:8110:b0ad:b8ad:c0ad:d0ad:e0ad:e8ad
- C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\Update.exe.log
- C:\Users\user\Desktop\SquirrelSetup.log
- \Device\ConDrv\Connect
- C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\program.exe.log
- C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1652.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER177A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER179B.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER2E10.tmp.WERInternalMetadata.xml
- Local\SM0:2496:168:WilStaging_02
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- 906b348568cf71aa17e3…7dde34Never scannednever seen before
- 9f1c7a70a062ceecb83f…c4dfa3Never scannednever seen before
- e63fdf79562f0518f364…2eb7fdNever scannednever seen before
- cac995bc6ee3e6e57809…7c0941Never scannednever seen before
- cb6628e27f4af63cf525…0efb5eNever scannednever seen before
- fe5f7b759edc8b86eb12…14b005Never scannednever seen before
- 031fbd00b5f2b5447823…8c93b9Never scannednever seen before
- 47ed777c463bb45f28fd…68013fNever 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.
- 3rule hits recorded
- 0 / 75engines flagged
- 1,132sources 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 a long, established submission history across 1,132 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Discord Inc..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Update.exe — 739681d4867feb70805401a25347ac39dbef57f2cb7f15ef764fcf739c0f7e1a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\Update.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Update.exe.log — C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\Update.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: SquirrelSetup.log — C:\Users\user\Desktop\SquirrelSetup.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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.
- pe_imphash
- Skystars_Malware_Imphash
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>\AppData\Local\Temp\executable.exe"
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Update.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Discord Inc.
- Size
- 1.4 MB
- Last analyzed
- Oct 7, 2026, 6:38 PM UTC
739681d4867feb70805401a25347ac39dbef57f2cb7f15ef764fcf739c0f7e1aSafety & 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 Update.exe safe?
What is Update.exe?
How many antivirus engines detected Update.exe?
Is Update.exe digitally signed?
What is the SHA-256 hash of Update.exe?
Is it safe to run Update.exe?
How up to date is this analysis of Update.exe?
Community
Member reviews and reports for this exact file hash.