Is ExLoader_Installer.zip safe?
No antivirus engine identified a threat, but defense-impairment behavior, negative reputation, and unresolved extracted files justify caution with this installer archive.
None of 75 engines detected the archive, including all 17 tier-1 engines, and the completed sandbox did not issue a malware finding. However, it recorded defense-impairment technique T1562.001, while the ten extracted files lack individual verdicts and no complete host-reputation check is available.
ed76f841d866a82c26…dcb0212c073e0dRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
None of 75 engines detected the archive, including all 17 tier-1 engines, and the completed sandbox did not issue a malware finding. However, it recorded defense-impairment technique T1562.001, while the ten extracted files lack individual verdicts and no complete host-reputation check is available.
The strongest signal is broad antivirus agreement: 0 of 75 engines flagged the archive, including no detections from 17 tier-1 engines. One completed sandbox did not produce a malware finding and recorded no network contacts, persistence indicators, or malicious child verdict. Nevertheless, T1562.001 indicates possible interference with defenses and deserves caution rather than dismissal. The ten extracted children all remain individually unresolved, so their rollup cannot establish benign contents. Negative reputation and community allegations add concern, but no engine family, malicious sandbox conclusion, external-intelligence hit, or known malicious host corroborates those claims.
What We Detected
No detections were reported by 75 antivirus engines, including 17 tier-1 engines. Research feeds also returned no MalwareBazaar match, CIRCL hit, or YARAify rule match. The archive has nevertheless accumulated a reputation score of -11, and several unverified community annotations allege adware or information-stealing activity.
Threat Behavior
One sandbox run extracted an executable and supporting libraries and did not issue a malware finding. It recorded T1562.001, a technique associated with impairing defenses, alongside six more common environmental or discovery techniques. No domains, IP addresses, persistence indicators, or malicious child verdicts were recorded. However, every one of the ten extracted children still has an unknown individual verdict, and no complete host-reputation cross-check is available.
What To Do Now
Keep endpoint protection enabled and obtain the installer only from the project's verified official release channel. Before execution, scan the extracted executable separately and consider testing it in an isolated environment without sensitive accounts or data.
Where this verdict could be wrong4 caveats
- T1562.001 was observed in the sandbox and concerns impairing defenses, which is more concerning than the six ambient techniques.
- file.reputation=-11 and several communityComments allege adware, stealer, or RAT behavior, but the comments have zero votes and lack independent payload corroboration.
- All 10 extracted children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false reflects no confirmed bad child rather than positive clearance.
- contactedHosts=null means no completed host-reputation cross-check 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/75 antivirus engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox.
- No persistence indicators or network contacts were recorded.
- MalwareBazaar, CIRCL, and YARAify returned no hits.
- Sandbox recorded defense-impairment technique T1562.001.
- The archive carries file.reputation=-11.
- All 10 extracted children have unknown individual verdicts.
- No complete contacted-host reputation check is available.
- Community annotations allege adware, stealer, and RAT behavior without independent corroboration.
Do not run this archive unless it came from a verified official source; scan the extracted executable separately and use isolation for testing. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 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
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 flight recorder
Capture complete- 1isolated sandbox run
- 7MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
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
ExLoader_Installer.zip
ed76f841d866a82c26d0f5b59a41ea89deef85d5819f3ba9e7dcb0212c073e0d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\ExLoader_Installer.zip"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\yrnlttrr.13s" "C:\Users\user\Desktop\ExLoader_Installer.zip"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
unarchiver.log
C:\Users\user\AppData\Local\Temp\unarchiver.log
04Isolated runtime analysis - Written fileObserved
yrnlttrr.13s
C:\Users\user\AppData\Local\Temp\yrnlttrr.13s
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.
- C:\Users\user\AppData\Local\Temp\unarchiver.log
- C:\Users\user\AppData\Local\Temp\yrnlttrr.13s
- C:\Users\user\AppData\Local\Temp\yrnlttrr.13s\ExLoader_Installer.exe
- C:\Users\user\AppData\Local\Temp\yrnlttrr.13s\flutter_windows.dll
- C:\Users\user\AppData\Local\Temp\yrnlttrr.13s\msvcp140.dll
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 1fe8436a743884cb6507…c604afNever scannednever seen before
- a728e91375dcadbdf6ef…d015edNever scannednever seen before
- 448a32b3d50aea55f6c8…9dfe2aNever scannednever seen before
- 52b039c90766568a35f3…802b70Never scannednever seen before
- 24c92d4d8fca5b981e05…4c88b7Never scannednever seen before
- 3c4bf83afb0b8533d068…68be73Never scannednever seen before
- 4e963580446656de3ede…fa6df1Never scannednever seen before
- 96a65b3d9c24a86a2831…58f00bNever scannednever seen before
- e741a4c79c808620c2b1…6930ccNever scannednever seen before
- bedb223a118926170d8d…e483b1Never 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.
- 0rule hits recorded
- 0 / 75engines flagged
- 3,698sources 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 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 20,148 times from 3,698 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: ExLoader_Installer.zip — ed76f841d866a82c26d0f5b59a41ea89deef85d5819f3ba9e7dcb0212c073e0d
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — C:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\ExLoader_Installer.zip"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\yrnlttrr.13s" "C:\Users\user\Desktop\ExLoader_Installer.zip"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: unarchiver.log — C:\Users\user\AppData\Local\Temp\unarchiver.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: yrnlttrr.13s — C:\Users\user\AppData\Local\Temp\yrnlttrr.13s
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- ExLoader_Installer.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 23.7 MB
- Last analyzed
- Oct 3, 2026, 11:06 PM UTC
ed76f841d866a82c26d0f5b59a41ea89deef85d5819f3ba9e7dcb0212c073e0dSafety & 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 open or extract 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 archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- 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 ExLoader_Installer.zip safe, or is it malware?
What is ExLoader_Installer.zip?
How many antivirus engines detected ExLoader_Installer.zip?
What should I do if I already opened or extracted ExLoader_Installer.zip?
How do I remove ExLoader_Installer.zip?
What is the SHA-256 hash of ExLoader_Installer.zip?
How up to date is this analysis of ExLoader_Installer.zip?
Community
Member reviews and reports for this exact file hash.