Is Niagara Launcher_v1_16_20.apk safe?
Two low-trust engines flagged a medium-prevalence Android launcher with no tier-1 support or malicious host evidence.
Only two low-trust detections exist against 75 engines, both generic PUP labels. No tier-1 consensus, no sandbox results, and contacted-no complete contacted-host reputation result was available. Medium prevalence and absence of external-intel hits support a safe classification.
fbb2b33429e70f7d8e…b464d5a0bb79e2Recommended next actions
Before installing
Install it only from Google Play, the developer's official store, or another source you independently trust.
If you already installed 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.
Only two low-trust detections exist against 75 engines, both generic PUP labels. No tier-1 consensus, no sandbox results, and contacted-no complete contacted-host reputation result was available. Medium prevalence and absence of external-intel hits support a safe classification.
The engine pattern matches the low-trust-only false-positive shape: two detections, none from tier-1 engines, and no family consensus. Contacted-host reputation cross-check inspected two hosts and found none malicious. No sandbox data exists, so runtime claims cannot be asserted. Medium prevalence and zero external-intel hits further reduce risk.
What We Detected
Two low-trust engines (AhnLab-V3, TrellixENS) reported generic PUP/Android.Moda and Artemis labels. All 16 tier-1 engines remained silent. No code signing applies to Android APKs.
Threat Behavior
No sandbox execution occurred. The sample contacted 14 IP addresses, but our host-reputation cache shows none flagged malicious. No dropped children or persistence indicators were recorded.
What To Do Now
Install from the official Niagara Launcher distribution channel and keep Android security updates enabled. Monitor for unusual battery or data usage after installation.
Where this verdict could be wrong1 caveat
- Direct-IP traffic to 14 addresses with no domain recorded (MalwareTips.Synth.DirectIpC2) could indicate C2, but contactedHosts shows no complete contacted-host reputation result was 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.
- Zero tier-1 malicious detections
- Medium prevalence across 283 sources
- no complete contacted-host reputation result was available in contacted-host cache
- Direct-IP traffic pattern (no domain recorded)
The file can be considered safe for installation from trusted sources; continue using standard Android security practices.
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
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Partial2 of 16 contacted hosts were cross-checked; coverage is incomplete.
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.
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
Niagara Launcher_v1_16_20.apk
fbb2b33429e70f7d8e221724825bd6e4579b21880ce550ec0ab464d5a0bb79e2
01Uploaded file
Files
Created or changed
- Written fileObserved
FirebaseHeartBeatW0RFRkFVTFRd+MToxMTI3MzkwMTM1MzU6YW5kcm9pZDpmYWQ0MjEwZjRiMmZlMWY1.xml
/data/user/0/bitpit.launcher/shared_prefs/FirebaseHeartBeatW0RFRkFVTFRd+MToxMTI3MzkwMTM1MzU6YW5kcm9pZDpmYWQ0MjEwZjRiMmZlMWY1.xml
02Isolated runtime analysis - Written fileObserved
2e8609309d0b3256.uid
/data/user/0/bitpit.launcher/cache/media/2e8609309d0b3256.uid
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.217.116.4
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
104.21.17.246
Contact observed during runtime.
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.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 2 / 75engines flagged
- 283sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 02
2 of 75 antivirus engines flagged the file, including AhnLab-V3 and TrellixENS.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 338 times from 283 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Niagara Launcher_v1_16_20.apk — fbb2b33429e70f7d8e221724825bd6e4579b21880ce550ec0ab464d5a0bb79e2
ProvenanceObservedSourceUploaded fileObserved at - 05
File written: FirebaseHeartBeatW0RFRkFVTFRd+MToxMTI3MzkwMTM1MzU6YW5kcm9pZDpmYWQ0MjEwZjRiMmZlMWY1.xml — /data/user/0/bitpit.launcher/shared_prefs/FirebaseHeartBeatW0RFRkFVTFRd+MToxMTI3MzkwMTM1MzU6YW5kcm9pZDpmYWQ0MjEwZjRiMmZlMWY1.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 2e8609309d0b3256.uid — /data/user/0/bitpit.launcher/cache/media/2e8609309d0b3256.uid
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 172.217.116.4 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 104.21.17.246 — 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.
Evidence172.217.116.4 · 104.21.17.246 · 172.67.178.228
2 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
- Niagara Launcher_v1_16_20.apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 13.5 MB
- Last analyzed
- Sep 7, 2026, 6:36 PM UTC
fbb2b33429e70f7d8e221724825bd6e4579b21880ce550ec0ab464d5a0bb79e2Safety & 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
Install it only from Google Play, the developer's official store, 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 Niagara Launcher_v1_16_20.apk safe?
What is Niagara Launcher_v1_16_20.apk?
How many antivirus engines detected Niagara Launcher_v1_16_20.apk?
What is the SHA-256 hash of Niagara Launcher_v1_16_20.apk?
Is it safe to install Niagara Launcher_v1_16_20.apk?
How up to date is this analysis of Niagara Launcher_v1_16_20.apk?
Community
Member reviews and reports for this exact file hash.