Is WormholeInstaller.exe safe?
Zero engine detections, signed executable with wide distribution and no malicious sandbox verdict.
All 74 engines returned clean. The file is signed and has been submitted by 1423 sources over 681 days. YARA rules fired but are generic and do not name malware.
13ab411e6642c85600…afc938c5ed11b9Recommended 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 74 engines returned clean. The file is signed and has been submitted by 1423 sources over 681 days. YARA rules fired but are generic and do not name malware.
Zero malicious detections across tier-1, tier-2, and low-trust engines removes the primary malware signal. The verified signature and common_old prevalence indicate established distribution rather than a new threat. Two MITRE techniques appear in sandbox output, yet the sandbox itself returned no malicious verdict. YARA hits are present but target generic behaviours such as debugger checks and encryption strings. Contacted-host reputation data is missing, so the 19 no complete contacted-host reputation result was available or malicious.
What We Detected
74 engines scanned the sample; none flagged it malicious or suspicious. The executable is signed by Beijing Guanshanjiyue Technology Co. and shows no brand mismatch. Sandbox execution recorded two MITRE techniques (T1134, T1543.003) but returned no malicious verdict.
Threat Behavior
YARAify matched eight community rules, five of which fired. Rule names focus on debugger detection and encryption strings rather than named malware families. 19 external IPs were contacted; host-reputation coverage is incomplete.
What To Do Now
Keep endpoint protection enabled. The file can be executed in a controlled environment if further behavioural review is required, but current evidence does not indicate malice.
Where this verdict could be wrong2 caveats
- YARAify returned 8 rules and 5 community matches, but rule names are generic (debugger checks, encryption detection) and do not name a malware family.
- contactedHosts=null means the 19 observed no complete contacted-host reputation result was available result cannot be inferred.
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/74 engines flagged malicious
- verified digital signature present
- common_old prevalence across 1423 sources
- no malicious sandbox verdict
- YARAify community rules matched (generic behaviours)
- contactedHosts data unavailable for 19 observed IPs
The sample shows no malicious indicators from engines or sandbox; treat as safe for normal use while retaining standard security controls.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete6 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
- 19MITRE ATT&CK techniques
- 8spawned processes
- 20network contacts
- 7filesystem & 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
WormholeInstaller.exe
13ab411e6642c8560022df383170e7f443e853f98c3a7c2109afc938c5ed11b9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\WormholeInstaller.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\WormholeInstaller.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
setup2024-10-13.txt
C:\Users\<USER>\Desktop\Log\setup2024-10-13.txt
04Isolated runtime analysis - Written fileObserved
Microsoft Compatibility Appraiser
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
142.251.184.94
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.186.246
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.
- 142.251.184.94
- 20.99.186.246
- 20.99.133.109
- 23.216.81.152
- 23.198.171.50
- 20.99.185.48
- 23.192.210.9
- 152.195.19.97
- 151.101.22.172
- 23.213.37.172
- C:\Users\<USER>\Desktop\Log\setup2024-10-13.txt
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- 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
- Wormhole_InstallerMutex
- \Sessions\1\BaseNamedObjects\Wormhole_InstallerMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 6rule hits recorded
- 0 / 74engines flagged
- 1,423sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,423 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Beijing Guanshanjiyue Technology Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: WormholeInstaller.exe — 13ab411e6642c8560022df383170e7f443e853f98c3a7c2109afc938c5ed11b9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\WormholeInstaller.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\WormholeInstaller.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: setup2024-10-13.txt — C:\Users\<USER>\Desktop\Log\setup2024-10-13.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Microsoft Compatibility Appraiser — C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 142.251.184.94 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.186.246 — 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.
- CP_Script_Inject_Detector
- DebuggerCheck__API
- DebuggerException__SetConsoleCtrl
- DetectEncryptedVariants
- golang_bin_JCorn_CSC846
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.
Evidence142.251.184.94 · 20.99.186.246 · 20.99.133.109
0 of 74 engines flagged this file
View all 74 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
- WormholeInstaller.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Beijing Guanshanjiyue Technology Co.
- Size
- 62.9 MB
- Last analyzed
- Aug 25, 2026, 10:00 AM UTC
13ab411e6642c8560022df383170e7f443e853f98c3a7c2109afc938c5ed11b9Safety & 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 WormholeInstaller.exe safe?
What is WormholeInstaller.exe?
How many antivirus engines detected WormholeInstaller.exe?
Is WormholeInstaller.exe digitally signed?
What is the SHA-256 hash of WormholeInstaller.exe?
Is it safe to run WormholeInstaller.exe?
How up to date is this analysis of WormholeInstaller.exe?
Community
Member reviews and reports for this exact file hash.