Is LoonaByTK9.apk safe?
One tier-1 engine flags a banking trojan while the remaining 73 engines stay silent and no sandbox or external-intel data exists.
A single tier-1 detection (Ikarus) labels the APK Trojan-Spy.AndroidOS.Banker, yet 73 other engines report clean and no sandbox execution or host-reputation results are available. The file is 111 days old with medium prevalence and no external-intel hits.
bff83bd4e58b15e1b9…e3103a0f366476Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from Google Play or the developer's official store.
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.
A single tier-1 detection (Ikarus) labels the APK Trojan-Spy.AndroidOS.Banker, yet 73 other engines report clean and no sandbox execution or host-reputation results are available. The file is 111 days old with medium prevalence and no external-intel hits.
The lone tier-1 malicious label is not backed by any other high-trust engine or family consensus. Direct-IP traffic triggered a heuristic, but the rule itself cautions against treating it as conclusive without host reputation. Absence of sandbox runs and external-intel corroboration leaves the detection unverified. Medium prevalence over 111 days suggests the file is not brand-new, yet the lack of corroborating signals keeps the verdict in mixed-signals territory.
What We Detected
One of 75 engines (Ikarus) reports Trojan-Spy.AndroidOS.Banker; Google adds a generic detection. All other tier-1 engines remain silent.
Threat Behavior
No sandbox execution occurred. The APK contacted ten external IP addresses without recorded domains, but host-reputation data is unavailable. No dropped children or persistence indicators were observed.
What To Do Now
Do not sideload the APK. Keep Android security features enabled and consider scanning the file with additional Android-focused engines before installation.
Where this verdict could be wrong1 caveat
- Single tier-1 detection on an Android sample with no sandbox run and no external-intel corroboration leaves the malicious label unconfirmed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 73 of 75 engines report clean
- Medium prevalence over 111 days
- No external-intel hits
- Single tier-1 detection on Android sample
- Direct-IP traffic without domain names
- No sandbox or external-intel corroboration
Treat the file as unverified; avoid installation until additional Android-specific scans or sandbox results become available.
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
Partial10 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.
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
LoonaByTK9.apk
bff83bd4e58b15e1b944dad4d2ef1a8d617810d585a197dab9e3103a0f366476
01Uploaded file
Network
Hosts contacted
- Contacted hostObserved
142.251.157.119
Contact observed during runtime.
02Isolated runtime analysis - Contacted hostObserved
173.194.194.94
Contact observed during runtime.
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
3 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
- 25sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 75 antivirus engines flagged the file, including Google and Ikarus.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 27 times from 25 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: LoonaByTK9.apk — bff83bd4e58b15e1b944dad4d2ef1a8d617810d585a197dab9e3103a0f366476
ProvenanceObservedSourceUploaded fileObserved at - 04
Contacted host: 142.251.157.119 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Contacted host: 173.194.194.94 — 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.
Evidence142.251.157.119 · 173.194.194.94 · 173.194.193.113
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
- LoonaByTK9.apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 11.8 MB
- Last analyzed
- Aug 28, 2026, 11:42 PM UTC
bff83bd4e58b15e1b944dad4d2ef1a8d617810d585a197dab9e3103a0f366476Safety & 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 install 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 app and use a fresh copy from a trusted source. Get a fresh copy from Google Play or the developer's official store.
- 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 LoonaByTK9.apk safe, or is it malware?
What is LoonaByTK9.apk?
How many antivirus engines detected LoonaByTK9.apk?
What should I do if I already installed LoonaByTK9.apk?
How do I remove LoonaByTK9.apk?
What is the SHA-256 hash of LoonaByTK9.apk?
How up to date is this analysis of LoonaByTK9.apk?
Community
Member reviews and reports for this exact file hash.