Is X-IBO-PRO.apk safe?
Unsigned Android APK showing PUA detections plus direct-IP behaviour with no domain usage.
Four engines flag the file as PUP/riskware or adware; one tier-1 engine labels it Android Xgen PUA. Direct-IP contacts without DNS and lack of code signing keep the sample in the suspicious range despite its age and moderate prevalence.
232892dd36a2d3873d…e6ef7a99be0768Recommended 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.
Four engines flag the file as PUP/riskware or adware; one tier-1 engine labels it Android Xgen PUA. Direct-IP contacts without DNS and lack of code signing keep the sample in the suspicious range despite its age and moderate prevalence.
The combination of a single tier-1 PUA detection, multiple adware-oriented labels, and the DirectIpC2 heuristic outweighs the clean external-intel and common_old history. Absence of signing and sandbox verdicts prevents a clean verdict, while the PUA-focused labels and lack of named malware families prevent a full malicious classification.
What We Detected
Four AV engines returned PUP or riskware labels; Sophos (tier-1) explicitly called the sample Android Xgen PUA. The APK is unsigned and contacted nine IP addresses directly without any domain resolution.
Threat Behavior
Ambient MITRE techniques are present but no offensive techniques were observed. The direct-IP pattern is a classic indicator used to evade domain-based reputation systems.
What To Do Now
Do not install the APK. If already present, uninstall and scan the device with a reputable mobile security product. Monitor for unexpected data usage or premium-SMS activity.
Where this verdict could be wrong2 caveats
- If the direct-IP behaviour is only connectivity checks (one URL is connectivitycheck.gstatic.com), the C2 heuristic may over-weight benign Android patterns.
- common_old prevalence and 771-day age suggest the file has circulated without widespread malicious reclassification.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- common_old prevalence (134 submitters)
- No malicious sandbox verdicts
- No dropped malicious children
- Unsigned APK
- Direct IP contacts without domains
- PUA / adware detections from tier-1 and tier-2 engines
Treat as unwanted software; avoid installation and remove if present.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Partial1 of 10 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Not runNo independent reference checks are recorded.
No timestamp recorded
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
X-IBO-PRO.apk
232892dd36a2d3873d0e6dc47f42fc87faf42a569ec30523dae6ef7a99be0768
01Uploaded file
Network
Hosts contacted
- Contacted hostObserved
198.54.120.71
Contact observed during runtime.
02Isolated runtime analysis - Contacted hostObserved
142.251.143.170
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
- 4 / 75engines flagged
- 134sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 75 antivirus engines flagged the file, including AhnLab-V3 and BitDefenderFalx.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 134 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 158 times from 134 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: X-IBO-PRO.apk — 232892dd36a2d3873d0e6dc47f42fc87faf42a569ec30523dae6ef7a99be0768
ProvenanceObservedSourceUploaded fileObserved at - 05
Contacted host: 198.54.120.71 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 142.251.143.170 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
This legacy report does not record whether the independent reference checks completed.
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.
Evidence198.54.120.71 · 142.251.143.170 · 142.251.143.132
4 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
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
- X-IBO-PRO.apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 20.6 MB
- Last analyzed
- May 25, 2026, 10:36 PM UTC
232892dd36a2d3873d0e6dc47f42fc87faf42a569ec30523dae6ef7a99be0768Safety & 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 X-IBO-PRO.apk safe, or is it malware?
What is X-IBO-PRO.apk?
How many antivirus engines detected X-IBO-PRO.apk?
What should I do if I already installed X-IBO-PRO.apk?
How do I remove X-IBO-PRO.apk?
What kind of malware is X-IBO-PRO.apk?
What is the SHA-256 hash of X-IBO-PRO.apk?
How up to date is this analysis of X-IBO-PRO.apk?
Community
Member reviews and reports for this exact file hash.