Is logitray.exe safe?
Unsigned 64-bit executable flagged by two low-tier engines and exhibiting process-injection behaviour.
Two engines label the file Win32.Troj.shellloader.v while 16 tier-1 engines remain silent. Sandbox evidence shows process injection (T1055) and evasion (T1562.001) but no malicious children or confirmed C2 contact.
d0b678797836641d23…519553986f3998Recommended 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.
Two engines label the file Win32.Troj.shellloader.v while 16 tier-1 engines remain silent. Sandbox evidence shows process injection (T1055) and evasion (T1562.001) but no malicious children or confirmed C2 contact.
The file is unsigned and carries only two low-trust detections, yet runtime behaviour includes process injection and anti-analysis techniques. No tier-1 consensus or malicious dropped children exist, and the host-reputation check is incomplete. Medium prevalence and absence of similar-hash history leave the sample in mixed-signal territory.
What We Detected
Two engines (Kingsoft tier2, APEX low_trust) flag the sample as Win32.Troj.shellloader.v. Sixteen tier-1 engines report clean. The binary is unsigned and writes configuration files under %APPDATA%\logitray.
Threat Behavior
Sandbox execution recorded MITRE techniques T1055 (process injection) and T1562.001 (impair defences). No malicious child files or confirmed C2 domains were observed, but the host-reputation cross-check was not completed.
What To Do Now
Keep endpoint protection enabled. Avoid executing the file until further reputation data or a completed host-reputation check is available.
Where this verdict could be wrong1 caveat
- engines.tier1Malicious=0 and 16 tier-1 engines reported clean — majority high-trust silence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Majority tier-1 engines silent
- No malicious dropped children
- No confirmed malicious host contact
- Unsigned executable
- Process-injection capability (T1055)
- Anti-analysis technique (T1562.001)
Treat as suspicious; do not run until additional reputation or sandbox coverage is obtained.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 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
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 flight recorder
Capture complete- 1isolated sandbox run
- 8MITRE ATT&CK techniques
- 2spawned processes
- 0network contacts
- 7filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Collects details about your system.
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
logitray.exe
d0b678797836641d23d2d3006ddac27c536fd1089e0ea316a3519553986f3998
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\logitray.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\logitray.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
.config.toml.3256.tmp
C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp
04Isolated runtime analysis - Written fileObserved
config.toml
C:\Users\<USER>\AppData\Roaming\logitray\config.toml
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\Roaming\logitray\.config.toml.3256.tmp
- C:\Users\<USER>\AppData\Roaming\logitray\config.toml
- C:\Users\<USER>\AppData\Roaming\logitray\logitray.log
- C:\Users\user\AppData\Roaming\logitray
- C:\Users\user\AppData\Roaming\logitray\.config.toml.6912.tmp
- C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- 6e96e612c011a4861d94…b9d09bNever scannednever seen before
- 787def0b49fe1cf51446…1d496dNever scannednever seen before
- 68b935445d08763f9622…96a2f2Never 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.
- 1rule hit recorded
- 2 / 75engines flagged
- 8sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
2 of 75 antivirus engines flagged the file, including APEX and Kingsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 9 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: logitray.exe — d0b678797836641d23d2d3006ddac27c536fd1089e0ea316a3519553986f3998
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\logitray.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\logitray.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: .config.toml.3256.tmp — C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: config.toml — C:\Users\<USER>\AppData\Roaming\logitray\config.toml
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
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.
Evidence"C:\Users\<USER>\Desktop\logitray.exe"
2 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
- logitray.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.1 MB
- Last analyzed
- Sep 2, 2026, 3:14 PM UTC
d0b678797836641d23d2d3006ddac27c536fd1089e0ea316a3519553986f3998Safety & 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 logitray.exe safe, or is it malware?
What is logitray.exe?
How many antivirus engines detected logitray.exe?
I already downloaded and ran logitray.exe — what should I do?
How do I remove logitray.exe?
What kind of malware is logitray.exe?
What is the SHA-256 hash of logitray.exe?
How up to date is this analysis of logitray.exe?
Community
Member reviews and reports for this exact file hash.