File scan report
Verdict Suspicious
Is Keygen. exe safe? Treat it as suspicious.
Nine of the 70 antivirus engines that checked it flag the file, none major.
Why Suspicious? 9 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 untrusted; obtain any needed functionality from a verified, signed vendor distribution.
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 5mo 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
Similar import-table fingerprint matches are mostly safe but lack signer correlation.
The import-table fingerprint matches are framework collisions rather than strong provenance signals. Overall the evidence sits in the borderline-mixed zone.
What We Detected
9 of the 70 antivirus engines that checked it returned malicious labels; none from major antivirus engines. The file is a 20 KB unsigned Win32 EXE whose internal name is Keygen.exe. Sandbox execution recorded MITRE techniques T1055 (process injection) and T1562.001 (impair defences). No domains or files it created were observed.
Threat Behavior
Static and behavioural signals are consistent with dual-use tooling or a generic trojan dropper. Filename rules and the security_tool_classifier rule both fired, but the lack of major consensus and external corroboration limits confidence in a malicious verdict.
What To Do Now
Do not execute the file on production systems. If reverse-engineering is required, run it only in an isolated VM with current security tooling enabled. Consider obtaining the software from an official, signed source instead.
Where this verdict could be wrong1 caveat
- similarHashes shows 3 safe verdicts on the same import-table fingerprint despite signerCoMatch=false, indicating framework collision rather than strong similarity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero malicious detections from major antivirus engines
- No external intelligence hits
- No contacted malicious hosts recorded
- Unsigned executable
- Filename suggests key-generation / cracking tool
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- 11sandbox rule tags
- 2spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Read basic details of the test computer, such as its Windows version.
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 code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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 4: FileSeen in the test run
Keygen.exe
d8e4668af72d2d8bc26dd7a6854741121d521c5c7551c2a9ecf32959660e58cc
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 4: ProcessSeen in the test run
software.exe
"C:\Users\<USER>\Desktop\software.exe"
Test run - Evidence 3 of 4: ProcessSeen in the test run
file.exe
"C:\Users\user\Desktop\file.exe"
Test run - +1 more recorded observation
- 1
Files
Created or changed
- Evidence 4 of 4: Written fileSeen in the test run
Roaming
C:\Users\user\AppData\Roaming
Test run
4 facts from the test run. See the full activity list.
Includes 11 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 · 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 9
- APEXMalicious
- BkavW32.Malware.2B39B854
- CrowdStrikewin/malicious_confidence_60% (W)
- DeepInstinctMALICIOUS
- MaxSecureTrojan.Malware.300983.susgen
- SentinelOneStatic AI - Suspicious PE
- tehtrisGeneric.Malware
- Trapminesuspicious.low.ml.score
File fingerprint
- Last analyzed
- Sep 7, 2026, 11:48 AM UTC
- SHA-256
d8e4668af72d2d8bc26dd7a6854741121d521c5c7551c2a9ecf32959660e58cc- SHA-1
93ece398654637f4af03b2a8e88f7d223132f5ec- MD5
aeac8c70da55b692deec5cab3793a80e
About this file
Keygen.exe is a Win32 EXE file of 20.5 kB.
- Type and size
- Win32 EXE · 20.5 kB
- Signer
- UnsignedNo code signature.
- First seen
- May 15, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 5.36 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, 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 Keygen.exe safe, or is it malware?
What is Keygen.exe?
How many antivirus engines detected Keygen.exe?
I already downloaded and ran Keygen.exe — what should I do?
What is the SHA-256 hash of Keygen.exe?
How up to date is this analysis of Keygen.exe?
Community
Member reviews and reports for this exact file hash.