File scan report
Verdict Suspicious
Is logitray. exe safe? Treat it as suspicious.
Two engines label the file Win32.Troj.shellloader.v while 16 major antivirus engines remain silent.
Why Suspicious? 2 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious; do not run until additional reputation or sandbox coverage is obtained.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
2 of 69 flagged
- Flagged 2
- No detection 67
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
2 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
No major consensus or malicious files it created 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 smaller, APEX low_trust) flag the sample as Win32.Troj.shellloader.v. Sixteen major antivirus 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 files it created or confirmed control-server domains were observed, but the host-reputation cross-check was not completed.
What To Do Now
Keep security software enabled. Avoid executing the file until further reputation data or a completed host-reputation check is available.
- Majority major antivirus engines silent
- No malicious files it created
- No confirmed malicious host contact
- Unsigned executable
- Anti-analysis technique
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 8sandbox rule tags
- 2spawned processes
- 0network contacts
- 7filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
logitray.exe
d0b678797836641d23d2d3006ddac27c536fd1089e0ea316a3519553986f3998
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
logitray.exe
"C:\Users\<USER>\Desktop\logitray.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
logitray.exe
"C:\Users\user\Desktop\logitray.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
.config.toml.3256.tmp
C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
config.toml
C:\Users\<USER>\AppData\Roaming\logitray\config.toml
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
8MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1036
- T1055· Process injection
- T1056· Keylogging
- T1071· Application protocol
- T1082· System recon
- T1562.001· Disables security
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
logitray.exe"C:\Users\<USER>\Desktop\logitray.exe"logitray.exe"C:\Users\user\Desktop\logitray.exe"
Files
7Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp - Written
C:\Users\<USER>\AppData\Roaming\logitray\config.toml - Written
C:\Users\<USER>\AppData\Roaming\logitray\logitray.log - Written
C:\Users\user\AppData\Roaming\logitray - Written
C:\Users\user\AppData\Roaming\logitray\.config.toml.6912.tmp - Written
C:\Users\user\AppData\Roaming\logitray\logitray.log
Show all 7 entries for files
- Deleted
C:\Users\<USER>\AppData\Roaming\logitray\.config.toml.3256.tmp
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Deleted
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\logitray
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 6e96e612c011a4861d94…b9d09bNot checkedno saved verdict
- 787def0b49fe1cf51446…1d496dNot checkedno saved verdict
- 68b935445d08763f9622…96a2f2Not checkedno saved verdict
Chapter 04
Technical details
2 of the 69 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
- APEXMalicious
- KingsoftWin32.Troj.shellloader.v
File fingerprint
- Last analyzed
- Sep 2, 2026, 3:14 PM UTC
- SHA-256
d0b678797836641d23d2d3006ddac27c536fd1089e0ea316a3519553986f3998- SHA-1
4d5ac2678681c660d59141f08eb99e732b8b55ca- MD5
94874a1eecf3b8335e53dc87beee58a7
About this file
logitray.exe is a Win32 EXE file of 2.2 MB.
- Type and size
- Win32 EXE · 2.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 16, 2026On VirusTotal.
- Submitted by
- 8 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.13 of 8
First scanned
Antivirus consensus
2 of 69 engines flagged this file
6 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-235 engines1flagged
- Low-trust17 engines1flagged
View all 75 engine results
- APEXMalicious: Malicious
- KingsoftMalicious: Win32.Troj.shellloader.v
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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?
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.