Is install_all.bat safe?
No antivirus engine detected this widely submitted batch installer, although one sandbox observed defense-related scripting and direct-IP traffic that lacks complete host-reputation coverage.
All 74 antivirus engines were free of detections, including 17 tier-1 engines, and the file has accumulated 7,015 submissions over several years. One sandbox recorded T1562.001 and direct-IP traffic, but produced no malicious runtime verdict; because host reputation was not fully checked, the script should still come from a trusted source.
492ee4c16ac45a5483…34d61673538f17Recommended 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 the file has accumulated 7,015 submissions over several years. One sandbox recorded T1562.001 and direct-IP traffic, but produced no malicious runtime verdict; because host reputation was not fully checked, the script should still come from a trusted source.
The strongest evidence is the complete absence of detections across 74 antivirus engines, including all 17 participating tier-1 engines. The batch file is also broadly established, with 3,605 submitters and 7,015 submissions since May 2023, which weighs against a newly distributed threat. A completed sandbox run observed one offensive technique, T1562.001, along with otherwise common installer and network activity, but it did not issue a malicious verdict or record persistence. The medium-severity direct-IP heuristic is a genuine counter-signal, not a standalone finding of command-and-control. No complete host-reputation result is available for the observed IP addresses, so the no complete contacted-host reputation result was available. Research feeds, malicious-child checks, and engine family labels provide no corroborating malware evidence.
What We Detected
The file is a 1,633-byte DOS batch installer known since May 2023. None of 74 antivirus engines flagged it, and all 17 participating tier-1 engines reported no detection. It has been submitted 7,015 times by 3,605 distinct sources, indicating broad and long-standing circulation.
Threat Behavior
One sandbox run recorded T1562.001, a technique associated with impairing defenses, plus direct connections to several IP addresses. A medium-severity direct-IP heuristic therefore fired, but the sandbox did not return a malicious verdict, create persistence, or record a malicious dropped child. The contacted-host reputation check was not completed or saved, so the observed no complete contacted-host reputation result was available or malicious from this evidence.
What To Do Now
Only run the script if it came from the expected software vendor or another trusted source, and inspect its short batch contents if practical. Keep endpoint protection enabled and avoid running it with administrator privileges unless the installation genuinely requires them.
Where this verdict could be wrong2 caveats
- T1562.001 indicates attempted impairment of defenses, an offensive behavior that warrants caution even though no engine or completed sandbox verdict identified malware.
- MalwareTips.Synth.DirectIpC2 fired after direct-IP traffic was observed, and contactedHosts=null means those contacts did not receive a complete saved reputation cross-check.
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 reported a malicious or suspicious result.
- All 17 participating tier-1 engines reported no detection.
- The hash has 3,605 unique sources and 7,015 submissions over more than three years.
- behaviour.hasMaliciousSandboxVerdict=false and no persistence indicators were recorded.
- No MalwareBazaar, CIRCL, or YARAify hit corroborated a threat.
- behaviour.offensiveTechniques includes T1562.001.
- MalwareTips.Synth.DirectIpC2 fired at medium severity.
- contactedHosts=null leaves the observed IP addresses without a complete saved reputation result.
- Batch scripts are unsigned by design, so publisher identity cannot be verified through code signing.
Use the batch file only when its download source and intended installation purpose are trusted. Keep endpoint protection enabled, and review the script before granting elevated privileges.
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
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
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
- 9MITRE ATT&CK techniques
- 7spawned processes
- 20network contacts
- 2filesystem & mutex artifacts
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
install_all.bat
492ee4c16ac45a5483088583c9caa08252d3a1bb3922dbbec834d61673538f17
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\install_all.bat"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\Desktop\install_all.bat"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
.exe
C:\Users\<USER>\Downloads\.exe
04Isolated runtime analysis - Written fileObserved
Connect
\Device\ConDrv\\Connect
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
151.101.3.6
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.45.173.142
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 151.101.3.6
- 23.45.173.142
- 192.229.211.108
- 17.253.5.203
- 23.208.144.168
- 17.248.193.18
- 17.253.144.10
- 17.253.83.220
- 44.228.151.38
- 17.253.82.117
- C:\Users\<USER>\Downloads\.exe
- \Device\ConDrv\\Connect
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
- 0 / 74engines flagged
- 3,605sources 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
The hash has a long, established submission history across 3,605 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 7,015 times from 3,605 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: install_all.bat — 492ee4c16ac45a5483088583c9caa08252d3a1bb3922dbbec834d61673538f17
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c start /wait "" "C:\Users\<USER>\Desktop\install_all.bat"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\Desktop\install_all.bat"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: .exe — C:\Users\<USER>\Downloads\.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 151.101.3.6 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.45.173.142 — Contact observed during runtime.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence151.101.3.6 · 23.45.173.142 · 192.229.211.108
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- install_all.bat
- Format
- DOS batch file
- Code signing
- Not applicable to this file type
- Size
- 1.6 KB
- Last analyzed
- Sep 11, 2026, 1:23 PM UTC
492ee4c16ac45a5483088583c9caa08252d3a1bb3922dbbec834d61673538f17Safety & 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 install_all.bat safe?
What is install_all.bat?
How many antivirus engines detected install_all.bat?
What is the SHA-256 hash of install_all.bat?
Is it safe to run install_all.bat?
How up to date is this analysis of install_all.bat?
Community
Member reviews and reports for this exact file hash.