File scan report
Verdict Malicious
Is project. exe safe? No, we rate this exact file malicious.
Eight major antivirus engines and 22 YARA rules flag this unsigned 64-bit PE as GenKryptik.
Strong evidence · Two or more major antivirus engines agree.
Remove the file and scan the host with current signatures; monitor for any persistence mechanisms left behind.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (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
39 of 70 flagged
- Flagged 39
- No detection 31
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
4 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
39 of the 70 antivirus engines that checked it detect the file, including eight major detections converging on GenKryptik. The sample is unsigned, exhibits two offensive MITRE techniques, and matches 22 community YARA rules.
Major consensus on the GenKryptik family, combined with a high volume of YARA rule matches, outweighs the absence of sandbox malice and incomplete host-reputation data. The file is unsigned and shows privilege-escalation and defense-evasion techniques. Medium prevalence and lack of trusted signer history further support the malicious classification.
What We Detected
39 of the 70 antivirus engines that checked it flagged the 25 MB Win32 EXE. Eight major antivirus engines (Avast, AVG, BitDefender, Emsisoft, ESET-NOD32, Fortinet, GData, Microsoft, Sophos, Symantec, TrendMicro) returned GenKryptik or Yogi family labels. YARAify matched 22 rules, five of which fired in our heuristics.
Threat Behavior
The antivirus analysis shows two offensive MITRE techniques (T1134 token manipulation, T1562.001 disable security tools). The sample wrote temporary files and contacted one external IP address; sandbox execution produced no malicious verdict. No files for files it created were flagged malicious.
What To Do Now
Quarantine or delete the file. Do not execute it. Keep security software enabled and scan any systems that ran or received the sample.
Where this verdict could be wrong2 caveats
- No contacted-host reputation result was saved — host-reputation cross-check incomplete.
- No dropped file is known to be malicious
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 malicious files it created
- sandbox returned no malicious verdict
- 8 malicious detections from major antivirus engines
- 22 YARA rule matches
- unsigned executable
- offensive MITRE techniques T1134, T1562.001
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- 18sandbox rule tags
- 3spawned processes
- 0network contacts
- 11filesystem & 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: 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 recording keystrokes; no keylogging was confirmed.
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.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
project.exe
5d4ad3e19d7bd5da58e294dff1e4c5f47fa65bfb208581a96537e87db967cccd
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
cmd.exe
cmd.exe /d /c exit 0
Test run - Evidence 3 of 5: ProcessSeen in the test run
project.exe
"C:\Users\user\Desktop\project.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
obseswiee_preflight_00000A40.tmp
C:\Users\<USER>\AppData\Local\Temp\obseswiee_preflight_00000A40.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Volumeid.exe
C:\Users\<USER>\AppData\Local\Temp\obseswieeMem_0003977E_2624\Volumeid.exe
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 18 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
39 of the 70 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 39
- Avast (major engine)Win64:MalwareX-gen [Misc]
- AVG (major engine)Win64:MalwareX-gen [Misc]
- BitDefender (major engine)Gen:Variant.Yogi.18390
- Emsisoft (major engine)Gen:Variant.Yogi.18390 (B)
- ESET-NOD32 (major engine)Win64/GenKryptik.GKCV trojan
- Fortinet (major engine)W64/GenKryptik.GKCV!tr
- GData (major engine)Gen:Variant.Yogi.18390
- Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
File fingerprint
- Last analyzed
- Aug 30, 2026, 11:32 PM UTC
- SHA-256
5d4ad3e19d7bd5da58e294dff1e4c5f47fa65bfb208581a96537e87db967cccd- SHA-1
a6cfba819ec10f845454eac303d64046d82d83d2- MD5
0fd0605f9162d6533f46de40058e74f5
About this file
project.exe is a Win32 EXE file of 25.1 MB.
- Type and size
- Win32 EXE · 25.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 27, 2026On VirusTotal.
- Submitted by
- 24 distinct sources
- Packer
- None detected
- Entropy
- 7.60 of 8
First scanned
Includes every engine result (75), 22 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is project.exe malware?
What is project.exe?
How many antivirus engines detected project.exe?
I already downloaded and ran project.exe — what should I do?
How do I remove project.exe?
What kind of malware is project.exe?
What is the SHA-256 hash of project.exe?
How up to date is this analysis of project.exe?
Community
Member reviews and reports for this exact file hash.