File scan report
Verdict Malicious
Is cr- keygen. exe safe? No, we rate this exact file malicious.
Unsigned keygen executable flagged by 11 major antivirus engines with evidence from the test run mapped to process-injection behavior.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Remove the file immediately; do not trust or redistribute key generators regardless of claimed functionality.
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.
From another device you trust, change the passwords of your important accounts (email and banking first) and turn on two-step verification.
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
43 of 70 flagged
- Flagged 43
- No detection 27
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
43 of the 70 antivirus engines that checked it detect this file as malicious, including 11 major antivirus engines that label it a keygen or hacktool.
The engine consensus is decisive: 11 major detections plus the corroborated hacking-tool label outweigh the absence of sandbox malice or dropped malicious files it created. The file is unsigned with no publisher history, and its filename and mapping align with known keygen tooling. Prevalence as widely seen and long established indicates wide distribution but does not confer legitimacy. No similar-hash RAG hits exist to suggest prior benign classification.
What We Detected
43 of the 70 antivirus engines that checked it flagged the sample, 11 of them major. Microsoft labels it HackTool:Win32/Keygen; BitDefender, Emsisoft and GData converge on Gen:Variant.Barys.500433. The file is unsigned and contains no code-signing certificate.
Threat Behavior
Sandbox execution recorded MITRE T1055 (Process Injection) and wrote multiple temporary DLLs. The filename 'cr-keygen.exe' and program markers names referencing 'MOHO Pro v14 Keygen' confirm its purpose as unlicensed software activation tooling.
What To Do Now
Delete the file and avoid executing any key generators. Scan the system for additional dropped DLLs and monitor for persistence mechanisms. Use only licensed software to eliminate the need for such tools.
Where this verdict could be wrong3 caveats
- No sandbox returned a malicious verdict and no dropped file is known to be malicious — no runtime malicious verdict or malicious files it created observed.
- contactedHosts.maliciousHosts=null and externalIntel.yaraify.hit=false — no corroborating host or YARA hits.
- If the keygen is a legitimate dual-use research tool, the hacking tool label could be a false positive, but 11 major antivirus engines and confirmed activity make this unlikely.
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 sandbox verdict
- no malicious files it created
- widely seen and long established prevalence
- 11 major antivirus engines detections
- A hacking-tool label is corroborated by several engines
- unsigned executable
- filename matches keygen pattern
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- 7sandbox rule tags
- 4spawned processes
- 0network contacts
- 25filesystem & 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 contacting a server, but no contacted host 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.
Threat context
How password stealers work
A password stealer runs quietly in the background and copies your private data, such as saved passwords, browser cookies, autofill details and crypto wallets, then sends it to criminals. You usually won't notice anything.
Bottom line:Stolen logins are used to break into your accounts or sold in bulk, so change passwords from another device.
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
cr-keygen.exe
05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
file.exe
"C:\Users\<USER>\Desktop\file.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cr-keygen.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Test.dat
C:\Users\<USER>\AppData\Local\Temp\Test.dat
Test run - Evidence 5 of 5: Written fileSeen in the test run
zrFBIoNdKsgQLkWFcpWl.DLL
C:\Users\<USER>\AppData\Local\Temp\zrFBIoNdKsgQLkWFcpWl.DLL
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
7MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1055· Process injection
- T1071· Application protocol
- T1082· System recon
- T1574.002· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"cr-keygen.exe%SAMPLEPATH%\cr-keygen.execr-keygen.exe"C:\Users\user\Desktop\cr-keygen.exe"software.exe"C:\Users\user\Desktop\software.exe"
Files
20Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\Test.dat - Written
C:\Users\<USER>\AppData\Local\Temp\zrFBIoNdKsgQLkWFcpWl.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\npNQqtgLpLHLfMjaudJJ.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\SlhbLPhFsE.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\joYHGPCNEpSPXVJuiqgE.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\LDmyhkYeQrTuODaTSGpY.DLL
Show all 20 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\kbyFTTGZbi.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\RoQgBVabpcaZPysfRKFf.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\ZGYgLOeIywVoYjFPqTFB.DLL - Written
C:\Users\<USER>\AppData\Local\Temp\ZRSjDIWsZa.DLL - Written
C:\Users\user\AppData\Local\Temp\FFRqjsTqRy.DLL - Written
C:\Users\user\AppData\Local\Temp\Test.dat - Written
C:\Users\user\AppData\Local\Temp\guOzAYnmIRiOwWSPdeHN.DLL - Written
C:\Users\user\AppData\Local\Temp\uBOceenCYFMOcMXqmYOC.DLL - Written
C:\Users\user\AppData\Local\Temp\GepMpDTRHriNnJAWDAZn.DLL - Deleted
C:\Users\<USER>\AppData\Local\Temp\Test.dat - Deleted
%USERPROFILE%\AppData\Local\Temp\Test.dat - Deleted
C:\Windows\System32\wbem\Performance\WmiApRpl.h - Deleted
C:\Windows\System32\wbem\Performance\WmiApRpl.ini - Deleted
C:\Users\user\AppData\Local\Temp\Test.dat
Mutexes
5Named locks a program uses so only one copy runs; malware families often reuse them.
MOHO Pro v14 KeygenLocal\MidiMapper_modLongMessage_RefCnt\Sessions\1\BaseNamedObjects\MOHO Pro v14 Keygen\Sessions\1\BaseNamedObjects\Local\MidiMapper_modLongMessage_RefCnt\Sessions\1\BaseNamedObjects\NULL
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
23.216.81.152
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache. 4 have no saved verdict and were not checked; that is missing coverage, not a finding.
- b141412d0611571df381…7a9ac6Not checkedno saved verdict
- a1a7c4f74d4fe7784ed0…8a2c0aNot checkedno saved verdict
- 532eaabd9574880dbf76…345e25Not checkedno saved verdict
- 8ad9e47693e292f381da…dd547fNot checkedno saved verdict
Chapter 04
Technical details
43 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 43
- Avast (major engine)Win32:Evo-gen [Trj]
- AVG (major engine)Win32:Evo-gen [Trj]
- Avira (major engine)TR/Crypt.XPACK.Gen
- BitDefender (major engine)Gen:Variant.Barys.500433
- DrWeb (major engine)Trojan.PWS.Spy.21260
- Emsisoft (major engine)Gen:Variant.Barys.500433 (B)
- ESET-NOD32 (major engine)Win32/Keygen.TN potentially unsafe application
- F-Secure (major engine)Packed:W32/PeCan.A
File fingerprint
- Last analyzed
- Jul 25, 2026, 1:34 AM UTC
- SHA-256
05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49- SHA-1
5270361d34e9034ee779c24d9840352c29e47ab8- MD5
8344ca17b5f23ef7dbcec522779ec742
About this file
cr-keygen.exe is a Win32 EXE file of 704.5 kB.
- Type and size
- Win32 EXE · 704.5 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jan 20, 2025On VirusTotal.
- Submitted by
- 380 distinct sources
- Packer
- None detected
- Entropy
- 7.72 of 8
First scanned
Antivirus consensus
43 of 70 engines flagged this file
4 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 43 detections come from 32 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines12flagged16 vendors sharing 12 engines
- Tier-235 engines14flagged18 vendors sharing 14 engines
- Low-trust17 engines9flagged
View all 74 engine results
- ALYacMalicious: Gen:Variant.Barys.500433
- APEXMalicious: Malicious
- ArcabitMalicious: Trojan.Barys.D7A2D1
- AvastMalicious: Win32:Evo-gen [Trj]
- AVGMalicious: Win32:Evo-gen [Trj]
- AviraMalicious: TR/Crypt.XPACK.Gen
- BitDefenderMalicious: Gen:Variant.Barys.500433
- BkavMalicious: W32.Malware.8395D404
- CrowdStrikeMalicious: win/malicious_confidence_70% (D)
- CTXMalicious: exe.trojan.keygen
- CylanceMalicious: Unsafe
- CynetMalicious: Malicious (score: 100)
- DrWebMalicious: Trojan.PWS.Spy.21260
- ElasticMalicious: malicious (high confidence)
- EmsisoftMalicious: Gen:Variant.Barys.500433 (B)
- ESET-NOD32Malicious: Win32/Keygen.TN potentially unsafe application
- F-SecureMalicious: Packed:W32/PeCan.A
- FortinetMalicious: W32/BDoor.EXZ!tr.bdr
- GDataMalicious: Gen:Variant.Barys.500433
- GoogleMalicious: Detected
- IkarusMalicious: Backdoor.Win32.Zegost
- K7AntiVirusMalicious: Unwanted-Program ( 005d0bc71 )
- K7GWMalicious: Unwanted-Program ( 005d0bc71 )
- KingsoftMalicious: Win32.HackTool.Keygen.v
- LionicMalicious: Trojan.Win32.Keygen.4!c
- MalwarebytesMalicious: Malware.AI.2288763968
- MaxSecureMalicious: Trojan.Malware.4397318.susgen
- McAfeeDMalicious: ti!05B4DFFE16C9
- MicrosoftMalicious: HackTool:Win32/Keygen
- MicroWorld-eScanMalicious: Gen:Variant.Barys.500433
- PaloaltoMalicious: generic.ml
- RisingMalicious: PUA.Keygen!8.3EB (CLOUD)
- SangforMalicious: Trojan.Win32.Save.a
- SentinelOneMalicious: Static AI - Malicious PE
- SkyhighMalicious: BehavesLike.Win32.Trojan.jc
- SophosMalicious: ZProtected (PUA)
- SymantecMalicious: ML.Attribute.HighConfidence
- TrellixENSMalicious: Artemis!8344CA17B5F2
- TrendMicro-HouseCallMalicious: Trojan.Win32.VSX.PE04CA3
- VaristMalicious: W32/ABApplication.GWVR-0436
- VBA32Malicious: BScope.Trojan.Tiggre
- VIPREMalicious: Gen:Variant.Barys.500433
- ZillyaMalicious: Trojan.Keygen.Win32.12768
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- Antiy-AVLClean
- Avast-MobileNo result
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- GridinsoftClean
- huorongClean
- JiangminClean
- KasperskyClean
- NANO-AntivirusClean
- PandaClean
- SUPERAntiSpywareClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrustlookNo result
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is cr-keygen.exe malware?
What is cr-keygen.exe?
How many antivirus engines detected cr-keygen.exe?
I already downloaded and ran cr-keygen.exe — what should I do?
How do I remove cr-keygen.exe?
What kind of malware is cr-keygen.exe?
What is the SHA-256 hash of cr-keygen.exe?
How up to date is this analysis of cr-keygen.exe?
Community
Member reviews and reports for this exact file hash.