Is title.keys safe?
No engine detected a threat, and the small text file has extensive historical prevalence without offensive behavior or external threat-intelligence matches.
All 75 antivirus engines were free of detections, including 17 high-trust engines. The file is a small, widely submitted text artifact, and its completed sandbox run produced no malicious verdict, offensive behavior, persistence, or dropped payloads.
3ed66f7e82df799227…d51013bd8c0677Recommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 75 antivirus engines were free of detections, including 17 high-trust engines. The file is a small, widely submitted text artifact, and its completed sandbox run produced no malicious verdict, offensive behavior, persistence, or dropped payloads.
The strongest evidence is complete detection silence across 75 engines, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. One completed sandbox run produced no malicious verdict and recorded no offensive techniques, persistence changes, written files, or dropped hashes. The sample has appeared through 2,670 sources and 3,276 submissions, giving it substantial history without a threat label. MalwareBazaar, YARAify, and CIRCL returned no matches. Code signing is irrelevant for this text file, while the unavailable contacted-host cross-check does not materially weaken the result because no network contacts were observed.
What We Detected
No threat detections were reported by any of the 75 antivirus engines. All 17 high-trust engines that contributed results, including Microsoft, Kaspersky, ESET-NOD32, BitDefender, and Avast, reported no detection.
Threat Behavior
One completed sandbox run produced no malicious verdict. It recorded no offensive techniques, persistence indicators, file writes, dropped hashes, or network contacts; the listed T1071, T1082, and T1218.011 techniques were ambient observations rather than offensive findings. No complete contacted-host reputation check was saved, although there were no observed hosts requiring such a check.
What To Do Now
No special remediation is indicated by the available evidence. Keep endpoint protection enabled and obtain the file from its expected source if its origin or purpose remains uncertain.
Where this verdict could be wrong1 caveat
- contactedHosts=null, so no completed host-reputation cross-check is available; however, behaviour.contactedDomains, contactedIps, and contactedUrls are all empty.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines reported a detection.
- 17/17 reporting tier-1 engines returned no detection.
- behaviour.hasMaliciousSandboxVerdict=false with behaviour.offensiveCount=0.
- 2,670 unique sources and 3,276 submissions indicate broad historical prevalence.
- MalwareBazaar, YARAify, and CIRCL returned no hits.
No special action is needed based on the available evidence. Keep endpoint protection enabled and verify the source if the file appeared unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 3MITRE ATT&CK techniques
- 2spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
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.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 2,670sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 2,670 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 3,276 times from 2,670 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: title.keys — 3ed66f7e82df79922739c6c2d34de90bc36a48d13acdff24f9d51013bd8c0677
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\title.keys"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\rundll32.exe "C:\Windows\system32\rundll32.exe" cryptext.dll,CryptExtOpenCAT C:\Users\user\Desktop\title.cat
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- title.keys
- Format
- Text
- Code signing
- Not applicable to this file type
- Size
- 1.2 KB
- Last analyzed
- Oct 5, 2026, 5:23 AM UTC
3ed66f7e82df79922739c6c2d34de90bc36a48d13acdff24f9d51013bd8c0677Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open it only when its sender or download source is one you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is title.keys safe?
What is title.keys?
How many antivirus engines detected title.keys?
What is the SHA-256 hash of title.keys?
Is it safe to open title.keys?
How up to date is this analysis of title.keys?
Community
Member reviews and reports for this exact file hash.