Is MAWS_Setup.exe safe?
Three of 75 engines flagged this unsigned installer, while one sandbox recorded several high-risk MITRE techniques without confirming malicious execution.
The unsigned installer drew three detections from 75 engines, none from tier-1 products, and no malware-family consensus. However, saved runtime evidence maps to process injection, destructive-impact, privilege, and persistence techniques, so execution should be avoided until the file’s origin and publisher can be independently verified.
3a081745e388b085ac…023caad91399b2Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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 unsigned installer drew three detections from 75 engines, none from tier-1 products, and no malware-family consensus. However, saved runtime evidence maps to process injection, destructive-impact, privilege, and persistence techniques, so execution should be avoided until the file’s origin and publisher can be independently verified.
Only 3 of 75 engines flagged the sample, and no tier-1 engine joined those detections, which weakens the generic Zpevdo and Agent labels. The executable is unsigned and lacks established publisher history, so there is no identity-based assurance to counter those warnings. One completed sandbox run was labeled clean, but its telemetry mapped activity to T1055, T1485, T1486, T1547.001, and other offensive techniques. Ten dropped files were inspected without a confirmed malicious child, although each child remains unclassified. Similar-file results are concerning but inconclusive because all three are imphash-only matches likely influenced by a shared installer framework. Taken together, the evidence warrants caution without establishing a specific malware family.
What We Detected
Three of 75 antivirus engines flagged MAWS_Setup.exe. Google and Varist supplied tier-2 detections, while Rising supplied a low-trust Zpevdo label; no tier-1 engine detected it, and there is no family consensus. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run was labeled clean, but its saved telemetry mapped activity to six offensive techniques, including process injection (T1055), file or data destruction (T1485), impact behavior associated with encryption (T1486), registry-run-key persistence (T1547.001), and privilege-related activity (T1548). These mappings indicate risk but do not prove that every technique occurred with malicious intent. Ten dropped children were inspected without a confirmed malicious child, although all ten remain unclassified. No complete contacted-host reputation result is available, and the sample recorded no network contacts in the saved run.
What To Do Now
Do not run the installer on a production system unless its source and expected publisher can be independently verified. Keep endpoint protection enabled; if testing is necessary, use an isolated disposable environment and investigate the dropped components separately.
Where this verdict could be wrong4 caveats
- No tier-1 engine detected the sample, and 13 tier-1 engines reported it undetected.
- behaviour.sandboxVerdicts contains one clean result, and behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children lack definitive verdicts.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage gaps.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine detected the sample
- One completed sandbox run returned a clean verdict
- No dropped child was confirmed malicious
- No YARAify, CIRCL, or MalwareBazaar corroboration was found
- No brand mismatch was detected
- Unsigned Win32 executable with no publisher history
- Three antivirus detections, including generic Agent and Zpevdo labels
- Runtime mapping to T1055 process injection
- Runtime mappings to T1485 and T1486 impact techniques
- Likely packed with WISE/INNO installer technology
- Ten dropped child files remain unclassified
Avoid execution until the download source and publisher are independently verified. Keep security protection enabled and quarantine the file if its provenance cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 24MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 32filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
MAWS_Setup.exe
3a081745e388b085ac8f2dc3f75c0c094fafecf56d50318052023caad91399b2
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-93V26.tmp\spchcpl.exe" /Q:A
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Users\<USER>\AppData\Local\Temp\IXP000.TMP\spchapi.exe /q:a
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
~TMP4352.TMP
C:\Users\<USER>\AppData\Local\Temp\IXP000.TMP\~TMP4352.TMP
04Isolated runtime analysis - Written fileObserved
SET5DF5.tmp
C:\Windows\System32\SET5DF5.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\SM_AccessoriesName
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\PF_AccessoriesName
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{C63A2B30-5543-11b9-C000-5611722E1D15}\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{6D40D820-0BA7-11ce-A166-00AA004CD65C}\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{6D40D820-0BA7-11ce-A166-00AA004CD65C}\LocalServer32\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{F1DC95A0-0BA7-11ce-A166-00AA004CD65C}\(Default)
- C:\Users\<USER>\AppData\Local\Temp\IXP000.TMP\~TMP4352.TMP
- C:\Windows\System32\SET5DF5.tmp
- C:\Windows\System32\speech.cpl
- C:\Windows\Help\SET5EC1.tmp
- C:\Windows\Help\spchcpl.hlp
- C:\Windows\System32\SET5DF5.tmp
- C:\Windows\Help\SET5EC1.tmp
- C:\Windows\MSAGENT\SET5F6E.tmp
- C:\Windows\Temp\OLD5F4C.tmp
- C:\Windows\MSAGENT
- cversions.3.m
- MicrosoftAgent2SingleInstanceMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- b9c02702961c35a23784…97fbacNever scannednever seen before
- 6f132475676faeebf082…f8dd4eNever scannednever seen before
- 5b6b9af99e2c38f8a709…86bbb3Never scannednever seen before
- 9ca0974c15e7f554ebea…ffd812Never scannednever seen before
- 146ecab699443c741514…254440Never scannednever seen before
- bd1295d19d010d4866c9…424e00Never scannednever seen before
- 8e0a80b885a73c8b62e8…c36a49Never scannednever seen before
- 709936902951fb684d0a…659331Never scannednever seen before
- 4751a3547f3b482bb4a2…e75c5eNever scannednever seen before
- 51d0efea836528cb1379…b11c57Never scannednever seen before
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
- 3 / 75engines flagged
- 7sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Google and Rising.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 7 times from 7 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: MAWS_Setup.exe — 3a081745e388b085ac8f2dc3f75c0c094fafecf56d50318052023caad91399b2
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-93V26.tmp\spchcpl.exe" /Q:A
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Users\<USER>\AppData\Local\Temp\IXP000.TMP\spchapi.exe /q:a
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ~TMP4352.TMP — C:\Users\<USER>\AppData\Local\Temp\IXP000.TMP\~TMP4352.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: SET5DF5.tmp — C:\Windows\System32\SET5DF5.tmp
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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXE
3 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- MAWS_Setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 6.2 MB
- Last analyzed
- Sep 30, 2026, 8:23 PM UTC
3a081745e388b085ac8f2dc3f75c0c094fafecf56d50318052023caad91399b2Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is MAWS_Setup.exe safe, or is it malware?
What is MAWS_Setup.exe?
How many antivirus engines detected MAWS_Setup.exe?
What should I do if I already installed MAWS_Setup.exe?
How do I remove MAWS_Setup.exe?
What is the SHA-256 hash of MAWS_Setup.exe?
How up to date is this analysis of MAWS_Setup.exe?
Community
Member reviews and reports for this exact file hash.