Our call: Is cr-keygen.exe safe?Malicious
Unsigned keygen executable flagged by 11 tier-1 engines with confirmed process-injection behaviour.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 43 of 74 antivirus engines flagged the file, including ALYac and APEX.Observed · Antivirus analysis
- One or more independent reference checks were incomplete or unavailable.Derived · External-intelligence coverage
05b4dffe16c941e1c6…57d0d08d49Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete43 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
cr-keygen.exe
05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\cr-keygen.exe
03Isolated runtime analysis
Files
Created or changed
- Written fileObserved
Test.dat
C:\Users\<USER>\AppData\Local\Temp\Test.dat
04Isolated runtime analysis - Written fileObserved
zrFBIoNdKsgQLkWFcpWl.DLL
C:\Users\<USER>\AppData\Local\Temp\zrFBIoNdKsgQLkWFcpWl.DLL
05Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
23.216.81.152
Contact observed during runtime.
06Isolated runtime analysis
6 recorded facts from one runtime window. Every fact remains independently traceable in the evidence ledger below.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
43 of 74 antivirus engines flagged the file, including ALYac and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: cr-keygen.exe — 05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\cr-keygen.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Test.dat — C:\Users\<USER>\AppData\Local\Temp\Test.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: zrFBIoNdKsgQLkWFcpWl.DLL — C:\Users\<USER>\AppData\Local\Temp\zrFBIoNdKsgQLkWFcpWl.DLL
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.216.81.152 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
43 of 74 engines detect this file as malicious, including 11 tier-1 engines that label it a keygen or hacktool. The sample is unsigned, exhibits T1055 process injection, and matches the filename pattern of a key generator.
The engine consensus is decisive: 11 tier-1 detections plus hacktoolConfirmed=true outweigh the absence of sandbox malice or dropped malicious children. The file is unsigned with no publisher history, and its filename and MITRE T1055 mapping align with known keygen tooling. Prevalence as common_old indicates wide distribution but does not confer legitimacy. No similar-hash RAG hits exist to suggest prior benign classification.
What We Detected
43 of 74 engines flagged the sample, 11 of them tier-1. 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. One direct-IP connection to 23.216.81.152 was observed without domain resolution. The filename 'cr-keygen.exe' and mutex 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
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false — no runtime malicious verdict or malicious dropped children 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 hacktool label could be a false positive, but 11 tier-1 engines and confirmed T1055 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 dropped children
- common_old prevalence
- 11 tier-1 engine detections
- hacktoolConfirmed=true
- T1055 process injection observed
- unsigned executable
- filename matches keygen pattern
Remove the file immediately; do not trust or redistribute key generators regardless of claimed functionality.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 23.216.81.152
- C:\Users\<USER>\AppData\Local\Temp\Test.dat
- C:\Users\<USER>\AppData\Local\Temp\zrFBIoNdKsgQLkWFcpWl.DLL
- C:\Users\<USER>\AppData\Local\Temp\npNQqtgLpLHLfMjaudJJ.DLL
- C:\Users\<USER>\AppData\Local\Temp\SlhbLPhFsE.DLL
- C:\Users\<USER>\AppData\Local\Temp\joYHGPCNEpSPXVJuiqgE.DLL
- C:\Users\<USER>\AppData\Local\Temp\Test.dat
- %USERPROFILE%\AppData\Local\Temp\Test.dat
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\Users\user\AppData\Local\Temp\Test.dat
- MOHO Pro v14 Keygen
- Local\MidiMapper_modLongMessage_RefCnt
- \Sessions\1\BaseNamedObjects\MOHO Pro v14 Keygen
- \Sessions\1\BaseNamedObjects\Local\MidiMapper_modLongMessage_RefCnt
- \Sessions\1\BaseNamedObjects\NULL
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- b141412d0611571df381…7a9ac6Never scannednever seen before
- a1a7c4f74d4fe7784ed0…8a2c0aNever scannednever seen before
- 532eaabd9574880dbf76…345e25Never scannednever seen before
- 8ad9e47693e292f381da…dd547fNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
Category: hacktool
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\<USER>\Desktop\file.exe"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence23.216.81.152
43 of 74 engines flagged this file
View all 74 engine results
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.
Fingerprint and provenance
- File name
- cr-keygen.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 688.0 KB
- Last analyzed
- Jul 25, 2026, 1:34 AM UTC
05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
If you typed any passwords while it was open, change them from a device you trust.
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
- Yes — cr-keygen.exe is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 43 of 74 antivirus engines flag it (family: keygen). It behaves as a hacktool — dual-use offensive tooling that is dangerous regardless of intent. If you've already run it, see the removal and recovery steps below.
- cr-keygen.exe is a Windows executable program, about 688 KB. Our analysis identifies it as malicious (family: keygen) — a hacktool — dual-use offensive tooling that is dangerous regardless of intent. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
- 43 of 74 antivirus engines flagged cr-keygen.exe, 43 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove cr-keygen.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- cr-keygen.exe is classified as a hacktool — dual-use offensive tooling that is dangerous regardless of intent. Engines attribute it to the keygen family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- The SHA-256 hash of cr-keygen.exe is 05b4dffe16c941e1c64357c9d13673b58f6d1dcc0deeb11759851957d0d08d49, and its MD5 is 8344ca17b5f23ef7dbcec522779ec742. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 25, 2026. Because a file's hash never changes, the identity of cr-keygen.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.