Return to Threats

Flying Eagle Android RAT Traces Found on 170 Servers as Source Code Circulates

thehackernews.com 2026-07-29 malicious AI use High

What Happened

Source code for the Flying Eagle Android remote access trojan (RAT) framework is circulating through criminal Telegram channels. Hunt.io and independent researcher NetAskari traced matching control panels and certificates to 170 internet servers. They linked the framework to a fake "公安一网通办" Public Security service application targeting Android users in China. The kit supports payment-password

Why It Matters

Report facts: The article describes the Flying Eagle Android remote access trojan framework, whose full source code and turnkey Docker deployment (web stack, APK builder, phishing templates, default TLS cert) are circulating on criminal Telegram channels, and whose infrastructure fingerprints have been mapped to 170 servers hosting a fake Chinese Public Security service app used to steal payment data and remotely control Android devices.[2][1] The kit supports advanced surveillance and fraud capabilities including payment-password and keystroke capture, screen recording, camera access, and phishing for financial and government applications.[2] RealGround analysis: While Flying Eagle itself is not an AI system, its leaked, easily reusable framework and phishing tooling increase the likelihood that similar infrastructures will integrate AI-powered elements (e.g., automated targeting, content generation, or evasion), making it a relevant pattern for monitoring "malicious AI use" ecosystems. Continuous AI Red Teaming can help organizations simulate how such RAT/phishing frameworks could be augmented by AI agents, test their controls against evolving attacker tooling, and ensure that an

Healthcare Fintech SaaS SMB AI startups

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/07/flying-eagle-android-rat-traces-found.html

Talk to AI CISO