What Happened
A new Mirai-derived botnet called Tengu can use a compromised Linux device's hardware watchdog to trigger a reboot when defenders kill its main process. If that happens, Tengu's other persistence mechanisms get another chance to relaunch it. Nozomi Networks Labs observed the dropper reaching its honeypots through Telnet credential brute force. Tengu supports 25 distributed denial-of-service (
Why It Matters
The article reports that the Mirai-derived Tengu botnet targets internet-facing Linux and IoT devices, uses Telnet brute-force access, supports 25 DDoS methods, and can trigger a reboot via the device watchdog if defenders kill its main process.[1][3][5] It also uses persistence and self-defense mechanisms, including relaunching from other startup paths, to keep the infection active.[1][4] RealGround analysis: this is primarily a botnet/persistence threat rather than an AI-specific incident, but it is relevant because autonomous defense and response tooling must account for anti-removal behaviors that can interfere with remediation and monitoring.
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/tengu-botnet-reboots-compromised-linux.html
