Is Voidstrap.dll safe?
Unsigned 37 MB PE with zero engine detections, common_new prevalence, and no sandbox malice signals.
All 75 engines returned clean. The file is unsigned and shows only ambient behaviour in one sandbox run. Widespread submissions and a prior safe verdict on the same imphash support a benign classification.
110b919436013679bf…d4bd2c2f6eff02Recommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used 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 engines returned clean. The file is unsigned and shows only ambient behaviour in one sandbox run. Widespread submissions and a prior safe verdict on the same imphash support a benign classification.
Zero malicious detections across 75 engines, including 17 tier-1 engines, removes any engine-based risk. The unsigned status is a neutral factor given the complete absence of detections. Sandbox execution produced only ambient techniques and no malicious verdict. The file is already common_new with 1545 submitters, indicating wide benign distribution. A prior similar-hash verdict of safe on the same imphash adds modest corroboration.
What We Detected
75 antivirus engines scanned the 37 MB unsigned PE; none flagged it malicious or suspicious. One sandbox recorded ambient system queries and a single direct-IP connection to 162.159.36.2, but no malicious verdict or offensive MITRE techniques.
Threat Behavior
No dropped children, no persistence indicators beyond a mutex, and no external-intel hits on CIRCL, MalwareBazaar, or YARAify. The file shows high prevalence (common_new) with 1857 submissions from 1545 sources.
What To Do Now
Keep endpoint protection enabled. The sample can be executed in a controlled environment if further validation is required, but current evidence indicates no threat.
Where this verdict could be wrong1 caveat
- communityComments link the hash to Amadey/Glassworm/HijackLoader families, yet no engine detections or external-intel hits corroborate the claim.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- High prevalence (common_new)
- No sandbox malice verdict
The file presents no observable malicious indicators; it can be treated as safe for normal use while standard protections remain active.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
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
- 9MITRE ATT&CK techniques
- 4spawned processes
- 1network contacts
- 1filesystem & mutex artifacts
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
Voidstrap.dll
110b919436013679bff6743ddcc9d899cb4be85077a3e1736fd4bd2c2f6eff02
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Voidstrap.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\Voidstrap.exe" -install
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
04Isolated runtime analysis
4 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- 162.159.36.2
- \Sessions\1\BaseNamedObjects\DBWinMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 1,545sources 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 been submitted 1,857 times from 1,545 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Voidstrap.dll — 110b919436013679bff6743ddcc9d899cb4be85077a3e1736fd4bd2c2f6eff02
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\Voidstrap.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\Voidstrap.exe" -install
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 162.159.36.2 — Contact observed during runtime.
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.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- Voidstrap.dll
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 35.9 MB
- Last analyzed
- Sep 5, 2026, 2:28 PM UTC
110b919436013679bff6743ddcc9d899cb4be85077a3e1736fd4bd2c2f6eff02Safety & 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
Use it only as part of software obtained from the developer's official site or another source 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 Voidstrap.dll safe?
What is Voidstrap.dll?
How many antivirus engines detected Voidstrap.dll?
What is the SHA-256 hash of Voidstrap.dll?
Is it safe to use Voidstrap.dll?
How up to date is this analysis of Voidstrap.dll?
Community
Member reviews and reports for this exact file hash.