New to ShortSpan? We distil the AI-security research that matters into practitioner takeaways — edited by Ben Williams (NCC Group).Get the weekly email
// Analysis
Local SLM turns RAT into autonomous intruder
Published: Wed, 05 Aug 2026 • By Elise Veyron
Agents
A lab build shows a Remote Access Trojan (RAT) paired with a local Small Language Model (SLM) can run the observe–decide–act loop without cloud help or an operator. The 8B model occasionally gained root on Metasploitable2, but achieved only 10.9% task success amid hallucinations and brittle recovery, shifting detection to on‑host telemetry.
Agentic malware is no longer a thought experiment. A new lab study wires a locally hosted Small Language Model (SLM) into a Remote Access Trojan (RAT) and lets it run the whole observe–decide–act loop on an endpoint. No cloud. No operator in the chair. The question was simple: can a small model think enough to break in?
The team stood up a controlled, network‑isolated environment: an agent container, a Kali attacker, and a Metasploitable2 target. An 8‑billion‑parameter Dolphin‑family model served locally via LM Studio handled the “reasoning”. A controller fed it ranked reconnaissance from Nmap, validated suggested commands, executed approved ones on Kali over SSH, parsed terminal output, and iterated until a verification check was met or attempts ran out.
Architecturally, it worked. On commodity hardware, the SLM closed the loop without any external service. It interpreted scan evidence, picked tools, and in some runs drove to verified root‑shell access against real services. That is the headline capability: decision‑making embedded on‑host, out of sight of network‑based detection.
Operationally, it was shaky. Across three checklist runs the agent attempted 55 service‑level tasks and completed 6, a 10.91% hit rate, with an average runtime of 251.16 seconds. Success clustered on two services: a 1524/tcp bind shell and 21/tcp FTP/vsftpd, both cases where a single inference bridged observation to exploitation. Everywhere else, it stumbled: hallucinated flags and commands, misread terminal output, wrong tool choices, commands that stalled waiting for interactive input, and unhelpful repetition instead of real replanning.
Resource use inside the agent container was trivial in the lab, roughly 0.1 to 0.31% CPU and 35 to 47 MB RAM, though the authors note this is not representative of a real host. More interesting are the behavioural traces: chains of repeated invocations and dead‑end loops, which would show up in execution telemetry. Because the “thinking” happens locally, you cannot rely on spotting C2 chatter; you need eyes on the process graph.
This is not a turnkey intrusion machine. It is a proof that a small, local model can autonomously push a compromise over the line in narrow cases. The paper argues real‑world incidents in 2025–2026 already point that way, and the obvious next step for attackers is better error recovery and multi‑stage planning. As more decision‑making shifts into endpoints, we will face awkward questions: what counts as an AI component for policy and control, how to make on‑host audit trails tamper‑evident, and where to anchor kill‑switch authority when there is no external operator to cut off.
Additional analysis of the original ArXiv paper
📋Original Paper Title and Abstract
Tiny Enough to Break In: Agentic Remote Access Trojans Powered by Small Language Models
Authors: Yuhan You, Suhas Adavelly, Victoria Lovelace, Cameron Berryman, Joel Sadler, and Daniel Graham
Agentic artificial intelligence raises a new security concern: cyber threats that reason, act, and adapt locally without continuous human direction. We examine this threat through an Agentic Remote Access Trojan (agentic RAT): a Remote Access Trojan augmented with a locally deployed Small Language Model (SLM). The SLM interprets host and network observations, selects actions, recovers from failed steps, and reduces reliance on an external operator. We implement the concept in a controlled, network-isolated lab built from Kali Linux, a Metasploitable2 target, LM Studio, and a local 8-billion-parameter Dolphin-family model. We then test whether a model this small can support autonomous cyber decision-making. This is architecturally feasible today. On commodity hardware, with no cloud service and no operator in the loop, the SLM closed the full observe-decide-act cycle: it interpreted ranked reconnaissance evidence supplied by the controller, selected actions, and obtained verified root-shell access on real vulnerable services. However, it is not yet operationally reliable. The same model hallucinated commands, misread output, and recovered from failure inconsistently, completing 10.9% of a deliberately strict checklist. That gap reflects the limits of today's small models, not a ceiling on the concept. As SLMs improve, agentic endpoint systems may become more practical, more autonomous, and harder to detect, straining existing monitoring, containment, and policy-enforcement mechanisms. Real-world incidents in 2025-2026 already show AI-driven intrusions moving from concept toward practice. That makes the local, self-contained variant we study a plausible near-term direction, not a hypothetical one.
🔍ShortSpan Analysis of the Paper
Problem
The paper studies agentic Remote Access Trojans (agentic RATs): conventional RATs augmented by a locally hosted Small Language Model (SLM) that closes a continuous observe-decide-act loop on an endpoint. This matters because a local SLM can reason, select actions, and adapt without cloud connectivity or a human operator, reducing network-dependent detection opportunities and potentially making intrusions more autonomous and stealthy.
Approach
The authors implemented a reproducible, network-isolated laboratory using Docker Compose: an agent container, a Kali attacker container, and a Metasploitable2 target. They served an 8-billion-parameter Dolphin-family model locally through LM Studio. A controller fed structured reconnaissance evidence from Nmap to the SLM, validated model-proposed commands, executed approved commands on Kali over SSH, parsed terminal output, and iterated until a verification criterion was met or attempts were exhausted. Runs were scored on checklist completion, efficiency, and reliability. The experiment avoided building any implant, persistence, evasion, or command-and-control; it focused solely on whether an off-the-shelf SLM can sustain the decision loop against real services and real command output.
Key Findings
Architectural feasibility demonstrated: a local SLM on commodity hardware closed the full observe-decide-act loop with no cloud service and no operator in the loop, interpreting ranked reconnaissance and proposing executable commands.
Operational capability limited: across three checklist runs the agent attempted 55 service-level tasks and completed 6, a 10.91% success rate; the average run score was 12.72/100 and average runtime 251.16 seconds.
Successes were narrow and consistent: two services succeeded repeatedly (the 1524/tcp bind shell and 21/tcp FTP/vsftpd), both cases where a single inferential step transformed observation into verified shell access.
Principal failure modes: hallucinated commands and flags, misreading terminal output, tool-to-service mismatches, commands requiring interactive input, and poor error recovery with repeated ineffective strategies rather than meaningful replanning.
Instrumented resource use in the container was low but not representative of a deployed host: roughly 0.1 to 0.31% CPU and 35 to 47 MB RAM for the agent container.
Limitations
The study is constrained by a single vulnerable target and one model family, possible training-data overlap with Metasploitable2 so successes may reflect memorisation rather than reasoning, absence of a rule-based control ablation that would isolate the SLM's contribution, short supervised sessions rather than long-horizon operation, and no adversarial or defensive-product testing. No implant, persistence, evasion, or C2 channels were built.
Implications
An attacker could deploy agentic behaviour locally to triage and act on host information without cloud dependence, lowering the skill floor and enabling inexpensive, high-volume attempts where even a one-in-ten success rate scales into impact. Offline autonomy reduces network-based detection opportunities because decisions occur on-host. Early offensive development would most plausibly focus on improving error recovery and multi-stage planning. Defenders should note that the observed failure modes create detectable behavioural signals: chains of repeated tool invocations and dead-end loops are visible in execution telemetry and offer an avenue for detection, while audit trails and richer host sensing will be important forensic artefacts.
- It shows a real risk: attackers can steer AI agents by embedding harmful instructions in external content, often leaving no obvious signs in the fin...
- Highlights a new, more dangerous attack class: backdoors planted in one step (a file or tool output) that Activate later to give an attacker persist...
- It presents a dynamic deception system (AgentSnare) that continually creates and validates decoy environments to steer autonomous penetration agents...
- It shows a practical foot-in-the-door prompt injection: harmless questions can nudge an agent to “think” about a tool in its plan, then push it towa...
- Addresses a real blind spot: misuse can be spread across many accounts so each transcript looks safe, evading typical per-session monitors.
- Propo...
- It analyzes how automated, model-guided jailbreak attempts against agentic AI can bypass traditional defenses, highlighting a key risk in scalable a...
- It demonstrates an autonomous multi-agent system that coordinates reconnaissance and exploitation, illustrating how AI-driven agents could streamlin...
- Core idea: embedded hints in automatically generated URL previews can nudge an agent to make outbound requests that leak runtime context, even if th...
- It studies how to detect covert coordination among many tool-using AI agents sharing infrastructure when you can only observe behavior, not internal...
Get the weekly digest
The few AI-security papers that matter, with the practitioner takeaway. No spam.