Is VencordInstaller.exe safe?
Unsigned installer with zero AV detections, high prevalence, and community confirmation as the legitimate Vencord client installer.
No engine flagged the sample. Widespread submissions and researcher comments identify it as the genuine Vencord installer. Observed MITRE techniques and YARA matches reflect common installer or anti-analysis behaviour rather than confirmed malice.
dc0826657a005009f4…a2db6e9913e871Recommended 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.
No engine flagged the sample. Widespread submissions and researcher comments identify it as the genuine Vencord installer. Observed MITRE techniques and YARA matches reflect common installer or anti-analysis behaviour rather than confirmed malice.
Zero detections across 75 engines, including all 17 tier-1 engines, outweighs the static and behavioural heuristics. The file is unsigned, yet its 954-day history, 108k submissions, and explicit community endorsement as the correct Vencord installer indicate legitimate distribution. Sandbox execution produced no malicious verdict and no malicious child or host artefacts were recorded. The YARA hits and MITRE mappings are consistent with anti-debugging and installer behaviour rather than a confirmed threat family.
What We Detected
75 engines scanned the file; none returned a malicious or suspicious result. The binary is unsigned and contains no code-signing certificate. Runtime telemetry recorded process-injection (T1055) and token-manipulation (T1134) calls plus direct-IP connections, but the sandbox returned no malicious verdict and no malicious dropped children or contacted hosts.
Threat Behavior
Community researchers explicitly label the sample as the authentic Vencord installer. The 28 YARA rules that fired focus on debugger checks and generic C2 strings, patterns also seen in many legitimate applications that implement anti-analysis or updater routines. No named malware family appears in any engine label or external intelligence source.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If you obtained the file from the official Vencord GitHub release channel, the evidence supports continued safe use. Verify future downloads against the project’s published checksums.
Where this verdict could be wrong1 caveat
- YARAify returned 28 rules including 'command_and_control', but no tier-1 engine or MalwareBazaar family match corroborates malicious intent.
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 flagged malicious
- 108771 prior submissions with clean reputation
- Explicit community confirmation as legitimate Vencord installer
- Unsigned executable
- Process-injection and debugger-detection behaviour observed
The file can be executed if downloaded from the official Vencord project; retain active antivirus protection for any future downloads.
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
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete7 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
- 23MITRE ATT&CK techniques
- 15spawned processes
- 22network contacts
- 18filesystem & 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
VencordInstaller.exe
dc0826657a005009f43bdc3a0933d08352f8b22b2b9b961697a2db6e9913e871
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\dc0826657a005009f43bdc3a0933d08352f8b22b2b9b961697a2db6e9913e871.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
KsecDD
\Device\KsecDD
04Isolated runtime analysis - Written fileObserved
Vencord
C:\Users\user\AppData\Roaming\Vencord
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
140.82.113.6
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.168.0.2
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 140.82.113.6
- 192.168.0.2
- 140.82.116.5
- 23.216.81.152
- 20.99.133.109
- a83f:8110:0:0:1b00:100:2800:0
- 192.168.0.41
- 20.99.185.48
- 23.62.210.8
- 192.168.0.55
- http://crt.sectigo.com/SectigoPublicCodeSigningCAR36.crt
- http://crt.sectigo.com/SectigoPublicCodeSigningRootR46.p7c
- \Device\KsecDD
- C:\Users\user\AppData\Roaming\Vencord
- C:\Users\user\AppData\Roaming\Vencord\dist
- C:\Users\<USER>\Desktop\software.exe.old
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
- MeBjAaAa__shmem3_winpthreads_tdm_
- DirectInput.{89521361-AA8A-11CF-BFC7-444553540000}
- DirectInput.{5944E682-C92E-11CF-BFC7-444553540000}
- HeAlAaAa__shmem3_winpthreads_tdm_
- PiAjAaAa__shmem3_winpthreads_tdm_
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- b33efcb95235b98b4850…29307fNever 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.
- 7rule hits recorded
- 0 / 75engines flagged
- 3,687sources 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 3,687 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: VencordInstaller.exe — dc0826657a005009f43bdc3a0933d08352f8b22b2b9b961697a2db6e9913e871
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\dc0826657a005009f43bdc3a0933d08352f8b22b2b9b961697a2db6e9913e871.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: KsecDD — \Device\KsecDD
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Vencord — C:\Users\user\AppData\Roaming\Vencord
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 140.82.113.6 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.168.0.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
- Check_OutputDebugStringA_iat
- command_and_control
- DebuggerCheck__API
- DebuggerCheck__QueryInfo
- DebuggerException__ConsoleCtrl
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>\Desktop\software.exe"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence140.82.113.6 · 140.82.116.5 · 23.216.81.152
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
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
- VencordInstaller.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 9.9 MB
- Last analyzed
- Sep 2, 2026, 6:53 PM UTC
dc0826657a005009f43bdc3a0933d08352f8b22b2b9b961697a2db6e9913e871Safety & 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 VencordInstaller.exe safe?
What is VencordInstaller.exe?
How many antivirus engines detected VencordInstaller.exe?
What is the SHA-256 hash of VencordInstaller.exe?
Is it safe to run VencordInstaller.exe?
How up to date is this analysis of VencordInstaller.exe?
Community
Member reviews and reports for this exact file hash.