File scan report
Verdict Suspicious
Is keygen. exe safe? Treat it as suspicious.
Detection agreement is limited—5 of the 69 antivirus engines that checked it flagged it, only one at major—and the completed sandbox assigned a clean result, so the evidence does…
Read the whole reasonShow less
Why Suspicious? 5 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
5 of 69 flagged
- Flagged 5
- No detection 64
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Five of the 69 antivirus engines that checked it flagged the executable, including one major antivirus engine using the generic TL0101EQ26YX Trojan designation. More importantly, observation from the test run mapped and identified two processes receiving injected code. The file is unsigned, leaving no verified publisher identity that might explain such intrusive behavior. Counter-signals include a clean sandbox result, long-standing prevalence across 244 submitters, and no malware-specific external-intelligence match. Taken together, these mixed indicators warrant isolation and further investigation rather than execution.
What We Detected
Five of the 69 antivirus engines that checked it flagged the executable. TrendMicro-HouseCall supplied the only major detection, naming a generic Trojan designation rather than a well-established family; most major antivirus engines did not flag it.
Threat Behavior
The completed observation from the test run recorded MITRE T1055 process injection into WMIADAP.EXE and an updater process. The sandbox itself returned a clean result, so this is mixed behavioral evidence rather than sandbox consensus. The observed network contacts were identified as analysis-environment background activity and are not attributed to the sample.
What To Do Now
Do not run the executable on a production or personal system. Quarantine it, keep security software enabled, and obtain the intended software through its legitimate publisher rather than using an unverified key generator.
Where this verdict could be wrong3 caveats
- Only 5 of the 69 antivirus engines that checked it flagged the file, with just one detection from a major antivirus engine and no strong family consensus.
- The file has circulated since 2021 across 244 submitters, which weighs against a newly deployed threat.
- No malware-specific YARAify rule matched, although rule coverage gaps remain possible.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only five of the 69 antivirus engines that checked it flagged the executable, and there was no strong major family consensus.
- The completed sandbox run assigned a clean result.
- The file has been submitted by 244 sources since 2021 rather than appearing as a sample.
- No malware-specific researcher rules matched, and no inspected file it created had a saved malicious verdict.
- The executable showed no high-entropy code or recognized packing.
- The executable has no verified digital signature or attributable publisher.
- Five antivirus engines raised detections, including one major antivirus engine using a generic Trojan label.
- The key-generator filename indicates software intended to bypass licensing controls and offers no trustworthy provenance.
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
- 3network contacts
- 17filesystem & 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: Checked whether it was running on a test computer.
Note: Talked to servers over the internet during the test run.
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 recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry 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 7: FileSeen in the test run
keygen.exe
2dfbd25e7016e83238f1d740cda53fc5279517b19af19b645e24b7e4862b6ebc
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\AppData\Local\Temp\program.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
2dfbd25e7016e83238f1d740cda53fc5279517b19af19b645e24b7e4862b6ebc.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
ConDrv
\Device\ConDrv
Test run - Evidence 5 of 7: Written fileSeen in the test run
Connect
\Device\ConDrv\\Connect
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
23.223.54.201
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
104.86.182.8
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 10 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
5 of the 69 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 5
- TrendMicro-HouseCall (major engine)Trojan.Win32.Gen.TL0101EQ26YX
- APEXMalicious
- CrowdStrikewin/malicious_confidence_60% (D)
- MaxSecureTrojan.Malware.300983.susgen
- McAfeeDti!2DFBD25E7016
File fingerprint
- Last analyzed
- Oct 13, 2026, 6:57 PM UTC
- SHA-256
2dfbd25e7016e83238f1d740cda53fc5279517b19af19b645e24b7e4862b6ebc- SHA-1
864013e030a94dbda24d2b916e471337a5cfc568- MD5
87ed5dc74c7fd6dc06a53b4da44c9420
About this file
keygen.exe is a Win32 EXE file of 114.7 kB.
- Type and size
- Win32 EXE · 114.7 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jan 10, 2021On VirusTotal.
- Submitted by
- 244 distinct sources
- Packer
- None detected
- Entropy
- 6.07 of 8
First scanned
Includes every engine result (74), 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.