Is ValorantTrueStretch_GUI_2.5.exe safe?
Eight of 75 engines raised mostly generic machine-learning detections, but one sandbox found no offensive activity and no confirmed malware family emerged.
Eight of 75 engines flagged this unsigned executable, although only Symantec represented a tier-1 detection and no strong family consensus formed. One sandbox run found no offensive techniques, persistence, malicious child, or malicious runtime verdict, so the generic detections remain inconclusive rather than definitive.
13a9cb77fb1e0d9680…00853e19fc66e0Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Eight of 75 engines flagged this unsigned executable, although only Symantec represented a tier-1 detection and no strong family consensus formed. One sandbox run found no offensive techniques, persistence, malicious child, or malicious runtime verdict, so the generic detections remain inconclusive rather than definitive.
The detection pattern is mixed: 8 of 75 engines flagged the sample, but five detections came from low-trust engines and only Symantec supplied a tier-1 vote. The labels are generic machine-learning assessments rather than agreement on a recognizable malware family. A completed sandbox run recorded nine broadly common techniques but zero offensive techniques, no persistence, and no malicious sandbox verdict. Ten extracted children were inspected without a confirmed malicious result, although all ten remain unclassified rather than established as benign. Because the executable is unsigned and lacks signer history, provenance cannot offset the detections. No complete host-reputation cross-check or external-intelligence coverage is available, leaving enough uncertainty to warrant caution.
What We Detected
Eight of 75 antivirus engines flagged the executable. Symantec was the only tier-1 detector, reporting a generic machine-learning attribute result; Elastic and SentinelOne also supplied generic assessments, while five detections came from low-trust engines. The engines did not converge on a named malware family.
Threat Behavior
One completed sandbox run observed nine broadly common techniques, including system-information and file discovery, but behaviour.offensiveCount was zero and no malicious sandbox verdict or persistence indicator was recorded. Ten extracted files were inspected and none was confirmed malicious, though all ten remain unclassified. No domains, IP addresses, or URLs were observed during that run, while a separate complete host-reputation cross-check is unavailable.
What To Do Now
Do not run the file on a primary or sensitive system until its origin and hash can be confirmed through the developer's official release channel. Keep endpoint protection enabled, and use an isolated test environment if further examination is necessary.
Where this verdict could be wrong3 caveats
- Symantec, a tier-1 engine, reported ML.Attribute.HighConfidence, and Elastic described its generic detection as high confidence.
- The file is unsigned despite signing.applicable=true, with no signer history available to establish provenance.
- contactedHosts=null, so no complete contacted-host reputation result is available; externalIntel availability is also unknown.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No strong tier-1 family consensus
- Zero offensive techniques in one completed sandbox run
- No malicious sandbox verdict
- No confirmed malicious dropped child
- No high-entropy code or likely packing
- 8/75 antivirus detections
- One tier-1 generic machine-learning detection from Symantec
- Unsigned executable with no signer history
- Ten extracted children remain unclassified
- No complete contacted-host reputation result
- No available external-intelligence coverage
Verify SHA-256 13a9cb77fb1e0d96804617e6aee2026af76f184afa144a528d00853e19fc66e0 against the developer's official release source before use. Keep endpoint protection enabled and avoid execution on a primary system while provenance remains unverified.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete8 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
- 9MITRE ATT&CK techniques
- 4spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Loads extra code modules while running.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
ValorantTrueStretch_GUI_2.5.exe
13a9cb77fb1e0d96804617e6aee2026af76f184afa144a528d00853e19fc66e0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Users\<USER>\Desktop\executable.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ValorantTrueStretch_GUI_2.5.dll
C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\ValorantTrueStretch_GUI_2.5.dll
04Isolated runtime analysis - Written fileObserved
_bz2.pyd
C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_bz2.pyd
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\onefile_6668_134054430821315761\ValorantTrueStretch_GUI_2.5.dll
- C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_cffi_backend.pyd
- C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_ctypes.pyd
- C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_decimal.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
- 76f6bc85fc9cb89bc3f9…5415eaNever scannednever seen before
- 741859cf238c3a63bbb2…561c2eNever 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
- 8 / 75engines flagged
- 16sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
8 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 17 times from 16 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: ValorantTrueStretch_GUI_2.5.exe — 13a9cb77fb1e0d96804617e6aee2026af76f184afa144a528d00853e19fc66e0
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Users\<USER>\Desktop\executable.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: ValorantTrueStretch_GUI_2.5.dll — C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\ValorantTrueStretch_GUI_2.5.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _bz2.pyd — C:\Users\<USER>\AppData\Local\Temp\onefile_6668_134054430821315761\_bz2.pyd
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.
8 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
- ValorantTrueStretch_GUI_2.5.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 12.1 MB
- Last analyzed
- Sep 15, 2026, 3:01 AM UTC
13a9cb77fb1e0d96804617e6aee2026af76f184afa144a528d00853e19fc66e0Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is ValorantTrueStretch_GUI_2.5.exe safe, or is it malware?
What is ValorantTrueStretch_GUI_2.5.exe?
How many antivirus engines detected ValorantTrueStretch_GUI_2.5.exe?
I already downloaded and ran ValorantTrueStretch_GUI_2.5.exe — what should I do?
How do I remove ValorantTrueStretch_GUI_2.5.exe?
What is the SHA-256 hash of ValorantTrueStretch_GUI_2.5.exe?
How up to date is this analysis of ValorantTrueStretch_GUI_2.5.exe?
Community
Member reviews and reports for this exact file hash.