Is dinput8wrapper.url safe?
90-byte .url file with zero detections but only one submission and no runtime data.
No engines flagged the file, yet coverage is low and the file is brand new. Similar filetype matches produced mostly unknown verdicts. Without sandbox or external-intel results, the sample remains inconclusive.
d720d0248b698c2b6b…4a36e86a529ee7Recommended next actions
Before opening
Treat the file as unverified and avoid opening it until more evidence is available.
If you already opened it
Run a full device scan. If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source.
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.
No engines flagged the file, yet coverage is low and the file is brand new. Similar filetype matches produced mostly unknown verdicts. Without sandbox or external-intel results, the sample remains inconclusive.
All 75 engines returned clean results, including 17 tier-1 engines. The file is a 90-byte .url of unknown type, first seen today, with no signing, no sandbox data, and no external-intel hits. Similar filetype matches in the RAG set were mostly unknown due to low coverage. The absence of malicious signals is noted, but the lack of completed analysis prevents a definitive safe classification.
What We Detected
Zero detections across 75 engines; 61 engines reported. File is a 90-byte Internet shortcut (.url) with no code-signing metadata.
Threat Behavior
No sandbox execution data available. No contacted hosts, dropped children, or external-intel matches recorded.
What To Do Now
Re-scan after more engines report or obtain sandbox results. Treat the file as unverified until additional evidence appears.
Where this verdict could be wrong1 caveat
- similarHashes shows one prior suspicious verdict on filetype match, but that file was an executable with 2 malicious detections, unlike this 90-byte URL file.
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 engines malicious
- no heuristic triggers
- rare_new prevalence
- unknown file type
- no sandbox coverage
Keep the file quarantined or delete it until sandbox or additional engine coverage confirms its purpose.
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
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
No completed runtime observation is available for this file.
Verdict inputView chapterProvenanceDerivedSourceRuntime coverageObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved 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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- dinput8wrapper.url
- Format
- unknown
- Code signing
- Not applicable to this file type
- Size
- 90 B
- Last analyzed
- Aug 9, 2026, 4:37 PM UTC
d720d0248b698c2b6b609086b99b3ddcf5f7f2d69b6b257a9e4a36e86a529ee7Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
There isn't enough information to give this file a clear rating.
- Recovery step 01
Be cautious — an unknown rating is not the same as a clean bill of health.
- Recovery step 02
Open it only when its sender or download source is one you independently trust.
- Recovery step 03
When in doubt, don't open it — or scan it again later once it's more widely seen.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is dinput8wrapper.url safe? What is it?
What is dinput8wrapper.url?
How many antivirus engines detected dinput8wrapper.url?
What is the SHA-256 hash of dinput8wrapper.url?
How up to date is this analysis of dinput8wrapper.url?
Community
Member reviews and reports for this exact file hash.