File scan report
Verdict Suspicious
Is Airwindows Consolidated- 2026- 06- 27- 9cf9ddf- Windows- 64bit- setup. exe safe? Treat it as suspicious.
One less reliable engine flagged the file while 68 others did not.
Why Suspicious? One antivirus engine (APEX) flags it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious pending further verification; do not execute on production systems without sandboxing.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 69 flagged
- Flagged 1
- No detection 68
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
2 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file is an unsigned Windows installer with medium prevalence. Engines show only a single less reliable detection and zero malicious flags from major antivirus engines. Similar-hash RAG returns one safe verdict on an import-table fingerprint match that lacks signer correlation. The combination of unsigned status, suspicious activity in the test run, and lack of strong malicious consensus places the sample in mixed-signals territory.
What We Detected
73 engines scanned the sample; only APEX (low_trust) returned a malicious label. All 17 major antivirus engines reported clean. The binary is unsigned and exhibits high-entropy sections typical of installers.
Threat Behavior
Two files it created were inspected and found clean. No complete contacted-host reputation result was available. No persistence mechanisms or registry changes were observed. The observed behaviour matches aggressive installer patterns but also overlaps with credential-access tooling.
What To Do Now
Run the installer in a controlled virtual machine if the source is trusted. Monitor for unexpected network activity or credential-store access. Consider re-scanning after the file has aged further or obtaining a signed build from the official Airwindows project site.
Where this verdict could be wrong1 caveat
- similarHashes match is import-table fingerprint-only with signerCoMatch=false, so it is a framework collision rather than strong provenance evidence.
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 malicious detections from major antivirus engines
- No malicious files it created
- Medium prevalence with 6 submitters
- Unsigned binary
- High-severity behaviour rule matched
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 17sandbox rule tags
- 5spawned processes
- 0network contacts
- 14filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
AirwindowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.exe
7a2be93276d1d191429eabb82c1fd99b0f4955904941a911dee3f6cf1908c457
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.exe
"C:\Users\<USER>\Desktop\ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-92UUN.tmp\ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.tmp" /SL5="$50026,9953561,832512,C:\Users\<USER>\Desktop\ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-92UUN.tmp\ndowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 17 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
1 of the 69 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- APEXMalicious
File fingerprint
- Last analyzed
- Jul 8, 2026, 4:50 AM UTC
- SHA-256
7a2be93276d1d191429eabb82c1fd99b0f4955904941a911dee3f6cf1908c457- SHA-1
e7c08eec92472ab1dbdb9d1e92c09d5441dfff55- MD5
6ffcb9a0238e86427428e97569981fca
About this file
AirwindowsConsolidated-2026-06-27-9cf9ddf-Windows-64bit-setup.exe is a Win32 EXE file of 10.8 MB.
- Type and size
- Win32 EXE · 10.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 28, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Includes every engine result (73), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is this file safe, or is it malware?
What is this file?
How many antivirus engines detected this file?
What should I do if I already installed this file?
What is the SHA-256 hash of this file?
How up to date is this analysis of this file?
Community
Member reviews and reports for this exact file hash.