Is CAD Exchanger safe?
No engine detected the years-old DLL, and static analysis found neither packing nor high-entropy code, although its unsigned origin remains unverified.
All 73 antivirus engines returned no malicious or suspicious finding, including 17 tier-1 engines. The DLL is unsigned and lacks runtime analysis, but its multi-year history, ordinary PE structure, and absence of external-intelligence matches strongly favor benign software.
f56c2b201b4524063a…ef78db3249311bRecommended 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.
All 73 antivirus engines returned no malicious or suspicious finding, including 17 tier-1 engines. The DLL is unsigned and lacks runtime analysis, but its multi-year history, ordinary PE structure, and absence of external-intelligence matches strongly favor benign software.
The antivirus results are consistently reassuring: none of 73 engines flagged the sample, and all 17 reporting tier-1 engines found no detection. The DLL was first submitted more than four years ago and has appeared through 15 distinct sources, reducing concern that it is a newly introduced payload. Static PE analysis found no recognized packer, likely packing, or high-entropy code warning. Research-intelligence checks produced no matching malware record or YARA rule. The main limitation is that the file is unsigned and has no completed runtime observation, while contacted-host reputation was not available.
What We Detected
None of 73 antivirus engines reported a malicious or suspicious result. Seventeen tier-1 engines, including BitDefender, Kaspersky, ESET-NOD32, Avast, and Fortinet, returned no detection. Research-intelligence checks also found no matching malware record or YARA rule.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be assessed. Static PE inspection found no recognized packer, no likely-packing indication, and no high-entropy code warning. No complete contacted-host reputation result is available because network-contact data was not checked or saved.
What To Do Now
The evidence strongly supports normal software, but the DLL is unsigned and therefore lacks a verified publisher identity. Obtain it from the official CAD Exchanger distribution channel, keep endpoint protection enabled, and avoid loading it if its source or expected installation path cannot be verified.
Where this verdict could be wrong2 caveats
- signing.applicable=true while signing.signed=false, so no verified publisher identity supports the file.
- behaviour=null and contactedHosts=null, meaning no completed runtime observation or complete contacted-host reputation result 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 of 73 engines reported a malicious or suspicious result.
- All 17 reporting tier-1 engines returned no detection.
- The sample has been known for 1,733 days and submitted from 15 distinct sources.
- Static analysis found no packer, likely packing, or high-entropy code warning.
- MalwareBazaar, CIRCL, and YARAify returned no matching intelligence hit.
- The Win32 DLL is unsigned despite code signing being applicable.
- No completed sandbox run is available to evaluate runtime behavior.
- No complete contacted-host reputation result is available.
Use the DLL only if it came from the official vendor or a trusted installation package. Keep endpoint protection enabled and verify its installation path or package integrity before loading it.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 73 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 / 73engines flagged
- 15sources 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 73 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 16 times from 15 sources.
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 73 engines flagged this file
View all 73 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- CAD Exchanger
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 14.8 MB
- Last analyzed
- Sep 30, 2026, 6:30 PM UTC
f56c2b201b4524063a27ae3f387083a3fe14cd5373350c7926ef78db3249311bSafety & 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 CAD Exchanger safe?
What is CAD Exchanger?
How many antivirus engines detected CAD Exchanger?
What is the SHA-256 hash of CAD Exchanger?
Is it safe to open CAD Exchanger?
How up to date is this analysis of CAD Exchanger?
Community
Member reviews and reports for this exact file hash.