File scan report
Verdict Suspicious
Is Cyberleek
Nine of the 70 antivirus engines that checked it flagged this unsigned executable, including two major detections, although one sandbox run found no offensive behavior.
Read the whole reasonShow less
Why Suspicious? 9 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
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
9 of 70 flagged
- Flagged 9
- No detection 61
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file has substantial warning signs: 9 of the 70 antivirus engines that checked it flagged it, including two major detections, and several labels identify Yogi. However, the detections collapse to three independent votes, while one sandbox run found no offensive behavior and the observed host had no adverse reputation entry, leaving meaningful uncertainty.
Nine of the 70 antivirus engines that checked it flagged the executable, with two major detections and three independent engine votes after vendor relationships were collapsed. BitDefender and Emsisoft use the Yogi label, while TrendMicro-HouseCall reports a generic trojan label, so the family attribution has support but not strong major consensus. The executable is unsigned and has no publisher history to counterbalance those detections. Conversely, the completed sandbox run returned clean, recorded no high-risk techniques, and the fully inspected contacted domain had no malicious or suspicious cache entry. No malware-specific external-intelligence hit, malicious child, packing indicator, or high-entropy code corroborates the engine findings, making isolation and source verification more appropriate than execution.
What We Detected
Nine of the 70 antivirus engines that checked it flagged CyberleekViewer.exe. Two major antivirus engines contributed detections, and the results reduce to three independent engine votes after related products are accounted for. BitDefender and Emsisoft identify Gen:Variant.Yogi.88021, while TrendMicro-HouseCall reports TROJ_GEN.R002H09J126. The file is unsigned, so there is no verified publisher identity to help establish provenance.
Threat Behavior
One completed sandbox run did not issue a malicious verdict and recorded no high-risk techniques, persistence changes, injected processes, written files, or files it created. Its only observed domain was fully covered by the host-reputation check and had no malicious or suspicious cache entry. No malware-specific YARAify rules, MalwareBazaar record, high-entropy code, or recognized packer provided additional corroboration. A prior malicious file shared the import-table fingerprint, but it had a different filename and no matching signer, so that similarity is supporting context rather than proof.
What To Do Now
Do not run the file on a normal system unless its origin and expected publisher can be independently verified. Keep security software enabled, let your antivirus remove the executable, and obtain a fresh copy from the software publisher's official release channel if the program is needed.
Where this verdict could be wrong4 caveats
- The completed sandbox run did not issue a malicious verdict and recorded no high-risk techniques.
- The one observed contacted domain was fully covered by the host-reputation check and had no malicious or suspicious cache entry.
- Most engines did not flag the file, and the Yogi family agreement does not meet the strong major consensus threshold.
- No malware-specific YARAify rule, MalwareBazaar record, malicious file it created, packing indicator, or high-entropy code was found.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- One completed sandbox run did not issue a malicious verdict.
- No high-risk techniques, injected processes, persistence changes, or dropped files were observed.
- The one observed domain was fully inspected and had no malicious or suspicious reputation entry.
- No malware-specific external-intelligence match, recognized packer, or high-entropy code was found.
- Nine of the 70 antivirus engines that checked it reported malicious detections.
- Two major antivirus engines flagged the executable.
- Several detections use the Yogi trojan label.
- The Windows executable is unsigned and has no established publisher history.
- A previously analyzed malicious file shared the same import-table fingerprint, although the publisher relationship could not be established.
6 sources checked · all complete. 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- 10sandbox rule tags
- 2spawned processes
- 0network contacts
- 0filesystem & 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).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host 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 3: FileSeen in the test run
CyberleekViewer.exe
fe3c88cf0227310aa46f52e0040555d329277add347a9a544c9514269ff9a1f7
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 3: ProcessSeen in the test run
CyberleekViewer.exe
"C:\Users\<USER>\Desktop\CyberleekViewer.exe"
Test run - Evidence 3 of 3: ProcessSeen in the test run
CyberleekViewer.exe
"C:\Users\user\Desktop\CyberleekViewer.exe"
Test run - +1 more recorded observation
3 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 10 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
9 of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 9
- BitDefender (major engine)Gen:Variant.Yogi.88021
- Emsisoft (major engine)Gen:Variant.Yogi.88021 (B)
- GData (major engine)Gen:Variant.Yogi.88021
- TrendMicro-HouseCall (major engine)TROJ_GEN.R002H09J126
- ALYacGen:Variant.Yogi.88021
- APEXMalicious
- ArcabitTrojan.Yogi.D157D5
- MicroWorld-eScanGen:Variant.Yogi.88021
File fingerprint
- Last analyzed
- Oct 10, 2026, 4:55 PM UTC
- SHA-256
fe3c88cf0227310aa46f52e0040555d329277add347a9a544c9514269ff9a1f7- SHA-1
9590fde1a54b9b397fd750d2afa7fb238bae8743- MD5
3d602a8af9d17d93e965cce3b52c86f9
About this file
CyberleekViewer.exe is a Win32 EXE file of 4.1 MB.
- Type and size
- Win32 EXE · 4.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 23, 2026On VirusTotal.
- Submitted by
- 30 distinct sources
- Packer
- None detected
- Entropy
- 6.70 of 8
First scanned
Includes every engine result (75), PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is CyberleekViewer.exe safe, or is it malware?
What is CyberleekViewer.exe?
How many antivirus engines detected CyberleekViewer.exe?
What should I do if I already ran CyberleekViewer.exe?
What is the SHA-256 hash of CyberleekViewer.exe?
How up to date is this analysis of CyberleekViewer.exe?
Community
Member reviews and reports for this exact file hash.