Is doorstop_config.ini safe?
No engine among 75 flagged this small, widely submitted INI configuration file, and independent intelligence sources supplied no threat corroboration.
The file has no detections among 75 antivirus engines, including no flags from 17 tier-1 engines. Its long history and 5,649 submissions strongly support an ordinary configuration file, although no completed runtime or host-reputation assessment is available.
4d5c6dfa0f771c6a5b…8dc3b73ce73cfcRecommended 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.
The file has no detections among 75 antivirus engines, including no flags from 17 tier-1 engines. Its long history and 5,649 submissions strongly support an ordinary configuration file, although no completed runtime or host-reputation assessment is available.
All 75 antivirus engines are free of malicious or suspicious detections, with 17 tier-1 engines reporting no detection. The sample is a 1,460-byte INI file, for which code signing is not applicable. It has been observed for 841 days across 3,256 sources and 5,649 submissions, providing substantial prevalence history. Research intelligence produced no MalwareBazaar, CIRCL, or YARAify match, and no heuristic rules fired. No sandbox execution or complete contacted-host reputation result is available, but those coverage gaps do not outweigh the extensive static and prevalence evidence.
What We Detected
None of 75 antivirus engines flagged the 1,460-byte INI file, and all 17 reporting tier-1 engines showed no detection. No threat family was identified, no heuristic rules fired, and research intelligence produced no MalwareBazaar, CIRCL, or YARAify match.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be characterized. The contacted-host reputation check was also not completed or retained, meaning no comprehensive network-reputation conclusion can be drawn.
What To Do Now
The file's 841-day history, 3,256 observed sources, and 5,649 submissions are consistent with a broadly distributed configuration file. It may be retained if it came with expected software; if its origin is unfamiliar, verify which application installed it before changing or deleting it.
Where this verdict could be wrong2 caveats
- behaviour=null, so there is no completed runtime execution evidence.
- contactedHosts=null, so no complete host-reputation cross-check is available.
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 tier-1 engines reported no detection
- Observed from 3,256 sources across 5,649 submissions
- No MalwareBazaar, CIRCL, or YARAify hit
- No triggered heuristics or brand mismatch
- No completed sandbox runtime observation
- No complete contacted-host reputation result
Keep the file if it belongs to software you recognize. If its origin is unexpected, confirm the associated application rather than opening or editing it blindly.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
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 behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 3,256sources 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 3,256 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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
- doorstop_config.ini
- Format
- INI
- Code signing
- Not applicable to this file type
- Size
- 1.4 KB
- Last analyzed
- Sep 30, 2026, 9:57 PM UTC
4d5c6dfa0f771c6a5b1b0c559aca0bd0ece7d08b08fff894708dc3b73ce73cfcSafety & 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 doorstop_config.ini safe?
What is doorstop_config.ini?
How many antivirus engines detected doorstop_config.ini?
What is the SHA-256 hash of doorstop_config.ini?
Is it safe to open doorstop_config.ini?
How up to date is this analysis of doorstop_config.ini?
Community
Member reviews and reports for this exact file hash.