Android banker: accessibility service abuse with overlay injection

DEX references AccessibilityService event hooks together with window-overlay creation and credential-capture primitives. This combination is the canonical Android banking-trojan pattern: the app reads screen content and injects fake login windows over legitimate banking apps.

Boot-triggered restart with disguised foreground service

Restarts itself on device boot and holds a foreground service with a low-visibility notification channel, keeping the process alive across reboots and outside normal background limits. Malicious use is distinguished by pairing this with surveillance or remote-control primitives.

Cleartext HTTP C2 to a hardcoded public IP literal

Embeds an http:// URL pointing at a raw public IP address, frequently on a non-standard port. Modern applications use TLS and DNS names, so a hardcoded cleartext IP endpoint usually indicates a disposable command-and-control host chosen to survive domain takedown.

Covert microphone or camera capture with exfiltration

Opens audio or camera capture outside any user-facing recording feature and pairs it with file staging and network transmission. The absence of a foreground recording interface alongside these primitives indicates surveillance rather than a legitimate media function.

Persistent WebSocket channel used for remote tasking

Bundles a WebSocket client and opens a long-lived bidirectional connection, the transport typically used by Android remote-access tooling for live command dispatch and streaming. Suspicious when paired with surveillance capabilities rather than an obvious in-app messaging feature.

Root, emulator and instrumentation-framework detection

Probes for superuser binaries, emulator build properties and dynamic instrumentation frameworks. Malware uses these checks to stay dormant inside analysis environments, so a sample matching this rule with an otherwise empty behavioural report should be treated as evasive rather than benign.