File scan report
Verdict Safe
Is baad.
None of the 70 antivirus engines that checked it flagged this unsigned 64-bit program, and three sandbox runs recorded no high-risk behaviour or hostile network activity.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Run this program only if it came from a source you trust. Keep your antivirus protection enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The combined sandbox verdict was clean, with no injection into other processes, no persistence and no network contact beyond the analysis machine's background traffic. The file is unsigned and not widely seen, so its publisher cannot be confirmed.
None of the 70 antivirus engines that checked it flagged the file, and every major antivirus engine reported it undetected. Three sandbox runs completed with a clean result. They recorded no process injection, no persistence and no registry changes. The only network contacts were the analysis machine's own background traffic. Malware databases and community rule sets hold no listing for this file, and its structure shows no packing or obfuscation. The main gap is the absence of a code signature combined with limited circulation, which lowers confidence somewhat.
What We Detected
None of the 70 antivirus engines that checked it flagged this 12 MB 64-bit Windows executable, including all 18 major antivirus engines. It has no listing in public malware-sample databases and matches no community malware rules. Its sections show normal entropy, with no packer or protector.
Threat Behavior
Three sandbox runs completed with a clean result. The program started itself and wrote nothing beyond console output. It created no persistence, changed no registry keys and injected into no named process. The only network contacts were background certificate and CDN traffic from the analysis machine. Some generic technique labels were mapped to the runs without any matching activity being observed.
What To Do Now
If you obtained this program from a source you trust, the evidence does not point to a threat. Because it is unsigned and not widely distributed, confirm where it came from before running it. Keep your security software enabled.
Where this verdict could be wrong1 caveat
- The file is unsigned and seen by only six submitters, so there is no publisher identity or broad reputation to vouch for it.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged the file.
- The combined sandbox verdict was clean, with no injection, persistence or hostile network activity.
- No listing in public malware databases or matches in community malware rules.
- No packing or obfuscation found in the file structure.
- The program carries no code signature, so its publisher cannot be verified.
- Few people have submitted this file, so there is little reputation history for it.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 6sandbox rule tags
- 2spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
What this file did when executed
This file was detonated in 3 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
6MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1055· Process injection
- T1071· Application protocol
- T1082· System recon
- T1562.001· Disables security
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
baad.exe"C:\Users\<USER>\Desktop\baad.exe"baad.exe"C:\Users\user\Desktop\baad.exe"
Files
1Files the file created, changed or deleted.
- Written
\Device\ConDrv\\Connect
Sandbox background — not the file
3The analysis machine's own processes and connections, recorded in every run.
- VM process
conhost.exeC:\Windows\System32\conhost.exe C:\Windows\system32\conhost.exe 0xffffffff -ForceV1 - VM host
a1672.dscr.akamai.net - VM host
eip-terr-na.cdp1.digicert.com.akahost.net
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 20, 2026, 1:04 PM UTC
- SHA-256
359dfcc44222fe86e8caf23cb9ca4e83e35c05aad68378b943eb3b207e3879ac- SHA-1
c856ac3b0b78f5835fd0b4160893e04d232f2330- MD5
424cc05ad6f9c792fef567f51f8906c8
About this file
baad.exe is a Win32 EXE file of 12.0 MB.
- Type and size
- Win32 EXE · 12.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 17, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.13 of 8
First scanned
Antivirus consensus
0 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-235 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is baad.exe safe?
What is baad.exe?
How many antivirus engines detected baad.exe?
What is the SHA-256 hash of baad.exe?
Is it safe to run baad.exe?
How up to date is this analysis of baad.exe?
Community
Member reviews and reports for this exact file hash.