Our call: Is AstroLauncher.dll safe?Suspicious
Unsigned 53 MB .NET launcher with one tier-1 detection, process-injection signals, and direct-IP traffic.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 2 of 75 antivirus engines flagged the file, including Bkav and Microsoft.Observed · Antivirus analysis
- The hash has been submitted 47 times from 45 sources.Derived · Saved report facts
6535091e16f95ce6e5…60fe6ba858Recommended next actions
Before using
Do not use it until the source and publisher can be verified independently.
If you already used it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Reinstall the parent software from the developer's official site instead of replacing this component by itself.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
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
AstroLauncher.dll
6535091e16f95ce6e5b9f12e2dc996ae828fe7e62aad1d4d66a79960fe6ba858
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Astro-Launcher-1.7.0.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
fisch.png
C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\fisch.png
04Isolated runtime analysis - Written fileObserved
launcher-manifest.json
C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\launcher-manifest.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
64.29.17.131
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
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
2 of 75 antivirus engines flagged the file, including Bkav and Microsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 47 times from 45 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: AstroLauncher.dll — 6535091e16f95ce6e5b9f12e2dc996ae828fe7e62aad1d4d66a79960fe6ba858
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Astro-Launcher-1.7.0.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: fisch.png — C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\fisch.png
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: launcher-manifest.json — C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\launcher-manifest.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 64.29.17.131 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Two engines flagged the file, one of them tier-1, but no family consensus exists. Sandbox evidence shows process injection and LSASS access while the file remains unsigned and contacts two external IPs with no known-malicious reputation.
The file is a large unsigned .NET executable submitted only one day ago. Microsoft’s tier-1 engine labels it Trojan:Win32/Wacatac.B!ml while 67 engines remain silent. Runtime behaviour includes T1055 process injection and LSASS memory access, yet the sandbox itself did not return a malicious verdict. Direct-IP connections were made to two addresses that our cache does not flag as malicious, and no dropped child files are known-bad. Medium prevalence and lack of similar-hash history leave the sample in mixed-signal territory.
What We Detected
75-engine scan returned two malicious detections: Microsoft (tier-1) and Bkav (low-trust). No tier-1 family consensus formed. The PE is unsigned and contains no packers.
Threat Behavior
Sandbox execution recorded MITRE T1055 process injection, LSASS access, and direct-IP traffic to 64.29.17.131 and 162.159.36.2. Ten dropped files were inspected; none carried a malicious verdict. No persistence mechanisms or registry modifications were observed.
What To Do Now
Keep antivirus enabled. Do not run the file on production systems until additional sandbox or community analysis is available. Monitor the contacted IPs for further indicators.
Where this verdict could be wrong3 caveats
- Single tier-1 detection with no family consensus and 67/75 undetected engines leaves room for false-positive.
- contactedHosts coverage is partial (only 1 inspected host) so complete host-reputation result is unavailable.
- behaviour.hasMaliciousSandboxVerdict=false despite offensive MITRE techniques observed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 67/75 engines undetected
- No malicious dropped children
- Medium prevalence across 45 sources
- Unsigned executable
- Process-injection technique observed
- LSASS memory access
- Direct-IP network traffic
Treat the file as untrusted; run it only in an isolated environment and await further reputation data.
Behavior
Plain-English impact first, then the observed runtime evidence.
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: Attempted to impair or bypass security controls.
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.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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.
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.
- 64.29.17.131
- 162.159.36.2
- https://ae-storefront.vercel.app:443/launcher/manifest.json
- https://ae-storefront.vercel.app:443/anime-expeditions.png
- https://ae-storefront.vercel.app:443/launcher/fisch.png
- https://ae-storefront.vercel.app/launcher/manifest.json
- https://ae-storefront.vercel.app/anime-expeditions.png
- https://ae-storefront.vercel.app/launcher/fisch.png
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\fisch.png
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\catalog\launcher-manifest.json
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\launcher.config.json
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\AstroLauncher.dll
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94\AstroLauncher.runtimeconfig.json
- C:\Users\<USER>\AppData\Local\Temp\.net\Astro-Launcher-1.7.0\a94
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- Local\SessionImmersiveColorMutex
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- a5104941ae1fafa59ef2…24ddf1Never scannednever seen before
- a109e807cfd061523a2c…fc063bNever scannednever seen before
- 1b7f631b1909648a9c2f…f7c917Never scannednever seen before
- f80683ac255bf215b062…037605Never scannednever seen before
- ef5d4bff35ed3d17e351…9cbd1cNever scannednever seen before
- 8d3ce78a9b693d124656…015795Never scannednever seen before
- 09b24af28410940e731e…08e6f6Never scannednever seen before
- f1928da80470e1f7a098…8fda61Never scannednever seen before
- 190d9e13ec667b7c311c…c170efNever scannednever seen before
- 4b2e3b646a85c9db9046…4ce1cfNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence64.29.17.131 · 162.159.36.2
2 of 75 engines flagged this file
View all 75 engine results
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.
Fingerprint and provenance
- File name
- AstroLauncher.dll
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 50.6 MB
- Last analyzed
- Aug 1, 2026, 4:24 AM UTC
6535091e16f95ce6e5b9f12e2dc996ae828fe7e62aad1d4d66a79960fe6ba858Safety & 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.
Don't use it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
Do not delete or replace the component manually. Quarantine it with your antivirus or repair the parent software from its official source. Reinstall the parent software from the developer's official site instead of replacing this component by itself.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.