What Happened
RatHat's operators build and publish the Android banking trojan and control infected phones from a web console, according to security company Cleafy. Cleafy has traced nearly 100 deployments of that console since April 2026. It said this fits a malware-as-a-service model, in which each customer runs a separate copy. The console stores what the malware collects from each phone,
Why It Matters
According to Cleafy, the RatHat Android banking-trojan console uses Gemini to estimate victims’ bank balances from stolen messages and rank infected phones by likely value; analyzed samples did not use Gemini to move money. This is malicious use of a commercial AI model to improve victim prioritization within a malware-as-a-service operation. RealGround analysis: organizations should assess AI-enabled abuse pathways, monitor model-integrated criminal workflows, and red-team controls against AI-assisted targeting and data misuse.
RealGround Analysis
This signal maps to malicious AI use. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.
Recommended Actions
- Restrict AI agent tool permissions and production write paths.
- Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
- Add human approval workflows for high-impact or state-changing actions.
- Run prompt injection and indirect prompt injection tests against affected workflows.
- Document the owner, control gap, and remediation deadline for this risk class.
Source
https://thehackernews.com/2026/09/rathat-android-malware-console-uses.html