Is RaidSetup.exe safe?
No antivirus engine detected this installer, although its unsigned, newly observed status and absent runtime data justify verifying its download source before execution.
All 74 antivirus engines were free of detections, including 17 tier-1 engines, and no external intelligence source identified a known threat. However, the executable is unsigned, newly observed, and has no completed sandbox analysis, so its origin should be verified before running it.
cd10fcc34b1e22d7b6…7f1a009b49499cRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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 74 antivirus engines were free of detections, including 17 tier-1 engines, and no external intelligence source identified a known threat. However, the executable is unsigned, newly observed, and has no completed sandbox analysis, so its origin should be verified before running it.
Static scanning produced no detections across 74 antivirus engines, with all 17 reporting tier-1 engines silent. Research intelligence also returned no MalwareBazaar, CIRCL, or YARAify hit, and the PE analysis did not identify packed or high-entropy code. These findings strongly reduce the likelihood of known malware. The principal uncertainty is that this unsigned executable has only one known submission and no publisher history. No completed runtime observation or comprehensive contacted-host reputation check is available, so post-launch activity remains unverified.
What We Detected
None of 74 antivirus engines flagged the executable, including 17 tier-1 engines. MalwareBazaar, CIRCL, and YARAify supplied no matching threat intelligence, while PE analysis found neither likely packing nor high-entropy code.
Threat Behavior
No completed sandbox run is available, so there is no observed runtime behavior to assess. Contacted-host reputation was also not checked or saved, meaning network safety cannot be inferred from this scan.
What To Do Now
Confirm that RaidSetup.exe came directly from the expected vendor or official release channel. Keep endpoint protection enabled, and avoid launching it if its origin cannot be verified or if the expected publisher normally signs its installers.
Where this verdict could be wrong3 caveats
- The file is unsigned and has only one known submission, so the clean engine result has little historical reputation behind it.
- behaviour=null and contactedHosts=null, leaving runtime activity and complete host-reputation results unavailable.
- similarHashes provides only generic filetype matches with mixed prior outcomes, not signer or imphash corroboration.
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/74 antivirus engines detected a threat
- 17 tier-1 engines reported no detection
- No MalwareBazaar, CIRCL, or YARAify hit
- peAnalysis.likelyPacked=false
- brandMismatch is not detected
- Unsigned Windows executable with signing.signed=false
- Only one known source and one submission
- No completed sandbox observation
- No complete contacted-host reputation result
Verify the installer against the publisher's official download channel or checksum before opening it. Keep antivirus and endpoint protection enabled during any further testing.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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 / 74engines 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
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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 74 engines flagged this file
View all 74 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
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
- RaidSetup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.9 MB
- Last analyzed
- Sep 15, 2026, 5:39 AM UTC
cd10fcc34b1e22d7b6c8b803aea891425dbbdb312f2992dfd47f1a009b49499cSafety & 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
Run it only when it came 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 RaidSetup.exe safe?
What is RaidSetup.exe?
How many antivirus engines detected RaidSetup.exe?
What is the SHA-256 hash of RaidSetup.exe?
Is it safe to run RaidSetup.exe?
How up to date is this analysis of RaidSetup.exe?
Community
Member reviews and reports for this exact file hash.