File scan report
Verdict Low Risk
Is DBCCB92
No antivirus engine detected this file, but absent evidence from the test run and minimal prevalence prevent a reliable determination of its purpose.
Read the whole reasonShow less
Why not Safe? Only one source had seen it when we scanned it.
Limited evidence · Nothing points to a problem, but little confirms who made it.
Good practice2 tips
Low Risk: no threat found, but we could not fully confirm this file.
Get it from the publisher's own website or app store, not from a re-upload or a link someone sent you.
Keep your security software on, and stop if the file does anything you didn't expect.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 60 flagged
- Flagged 0
- No detection 60
- No result 15
- Code signing Not applicable
- Test run Not run
- First seen 27d ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 60 antivirus engines that checked it were free of detections, including 17 major antivirus engines, and external intelligence produced no hits. However, the file has only one submission, no known type, no sandbox observation, and no complete network-reputation check, so its actual purpose remains unverified.
The sample received no malicious or suspicious detections from 75 antivirus engines, including no detections among 17 major antivirus engines. That is reassuring, and neither researcher rules nor external malware records identified the hash. However, it was first submitted on Sep 30, 2026 and has appeared only once, leaving little reputation history. No completed sandbox run is available, so execution behavior was not observed. The contacted-host cross-check is also unavailable, and the unknown file type prevents publisher verification or meaningful signing analysis. These limitations make the detection silence insufficient for a firm benign assessment.
What We Detected
None of the 60 antivirus engines that checked it flagged the sample, including 17 major antivirus engines. External intelligence returned no malware-record, reference-database, or researcher-rule match. The file type is unknown, and code-signing analysis is not applicable.
Threat Behavior
No completed sandbox observation is available, so the file's runtime actions were not observed. No complete contacted-host reputation result is available either. Although the .locky suffix resembles a ransomware-associated extension, the filename alone does not establish the file's contents or behavior.
What To Do Now
Keep security software enabled and avoid opening the file unless its source and intended purpose can be independently verified. If the file is expected, rescan it after engines have had more time to analyze it or test it only in an isolated environment.
Where this verdict could be wrong2 caveats
- The filename ends in .locky, which resembles a known ransomware-associated extension, but the detection-label list is empty and no behavioral or intelligence evidence supports that attribution.
- Detection silence across 75 engines is reassuring, but a first sighting today and a count of 1 submission limit how strongly it can establish benignity.
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/60 antivirus engines reported a detection
- All 17 reporting major antivirus engines were free of detections
- No MalwareBazaar, CIRCL, or YARAify hit
- No brand mismatch or adversarial text contamination was identified
- First observed on Sep 30, 2026 with only one submission from one source
- Unknown file type and unusual .locky extension
- No completed the test run
- No complete contacted-host reputation result
- No similar-file history or established publisher identity
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 60 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 30, 2026, 10:18 AM UTC
- SHA-256
7c66eb01db887a1820abc8fc5d71b4eca98b517c84d409030bd128f708fdde25- SHA-1
49345b419719bd478307c05abdd9574170f46ca3- MD5
812195f1ecfcb829156aee4631f3d151
About this file
DBCCB92A9D2CB371E46E7B90819C8EE7.locky is an unknown file of 99.7 kB.
- Type and size
- unknown · 99.7 kB
- Signer
- Not applicable
- First seen
- Sep 30, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 04
Questions & answers
Short answers to the 5 questions people ask most about this file.
Is DBCCB92A9D2CB371E46E7B90819C8EE7.locky safe?
What is DBCCB92A9D2CB371E46E7B90819C8EE7.locky?
How many antivirus engines detected DBCCB92A9D2CB371E46E7B90819C8EE7.locky?
What is the SHA-256 hash of DBCCB92A9D2CB371E46E7B90819C8EE7.locky?
How up to date is this analysis of DBCCB92A9D2CB371E46E7B90819C8EE7.locky?
Community
Member reviews and reports for this exact file hash.