Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

PoetRAT

← Back to Glossary
By NHI Mgmt Group Updated October 17, 2026 Domain: Threats, Abuse & Incident Response

PoetRAT is a remote access trojan that gives an attacker persistent control of an infected Windows system. It is used for spying, command execution, and file theft after compromise. Defenders should watch for suspicious persistence, encoded or unusual network traffic, and child processes spawned by office documents or other initial access vectors.

What Poetrat Does

PoetRAT is a remote access trojan designed to keep an attacker connected to a compromised Windows host. It is dangerous because it turns an initial intrusion into an ongoing foothold for spying, command execution, and file theft.

How PoetRAT Maintains Control

Remote access trojans usually combine persistence with remote command handling so the attacker can return after reboots or user activity. In practice, that means the malware is not just a one-time payload, but a control channel that can survive long enough to support follow-on abuse.

The persistence layer matters because it reduces the attacker’s need to re-enter the environment. If defenders only remove the visible process and miss the startup mechanism, scheduled task, registry change, or other persistence hook, the compromise can reappear.

Why PoetRAT Is a Security Problem

PoetRAT’s value to an attacker comes from post-compromise reach: visibility into the system, the ability to run commands, and the ability to collect files. That combination makes it useful for credential theft, internal reconnaissance, and staged exfiltration even when the initial access vector is no longer active.

Because the malware operates on a Windows endpoint, defenders should treat unusual child processes from office documents or other user-facing launch points as a strong warning sign. That pattern often reflects a user execution chain rather than normal application behaviour.

How Defenders Detect and Contain PoetRAT

Detection should focus on the behaviours in the primary definition, not only on file hashes or names. Suspicious persistence, encoded or unusual outbound traffic, and document-spawned child processes are the most useful signals for triage and correlation.

Containment should assume that the host may have been used for more than one task. After isolation, defenders should review what the trojan accessed, what commands were executed, and whether any files, browser data, or local credentials were collected during the session.

Risk and Threat Considerations

PoetRAT matters because remote access trojans convert a single compromise into durable attacker presence. The main risk is not only the malware itself, but the secondary abuse that follows, especially surveillance, data theft, and repeated command execution from a trusted endpoint.

Failure mechanism: The attacker establishes persistence and a command channel, then uses that foothold to blend remote activity into normal endpoint traffic while avoiding immediate removal.

Impact: The organisation can lose confidentiality, internal control of the host, and confidence that the endpoint has been fully cleaned after incident response.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1071 — Application Layer ProtocolPoetRAT uses unusual network traffic for remote control and evasive communication.
T1053 — Scheduled Task/JobRAT persistence commonly relies on jobs or tasks to survive reboot and user sessions.
T1204 — User ExecutionThe definition notes child processes spawned by office documents or other initial access vectors.
Recommendation — Map suspicious outbound sessions to application-layer command channels and hunt for nonstandard beaconing. Search for scheduled persistence mechanisms and remove them during containment. Correlate user-launched document activity with spawned processes to identify the initial execution chain.
CIS Controls v8CIS-8 — Audit Log ManagementDetection of RAT activity depends on reviewing process, network, and endpoint telemetry.
Recommendation — Centralise and review endpoint and network logs for persistence, execution, and exfiltration indicators.
NIST SP 800-53 Rev 5AU-6 — Audit Review, Analysis, and ReportingInvestigating PoetRAT requires analysis of endpoint and network events after compromise.
SI-4 — System MonitoringPoetRAT detection depends on monitoring for suspicious child processes and abnormal network behaviour.
Recommendation — Review and correlate telemetry to reconstruct commands, persistence, and data-access activity. Monitor hosts for abnormal process trees, persistence changes, and encoded outbound traffic.

Practitioner Guidance

What to watch for: Treat Office-driven child processes, odd encoded network sessions, and any unexplained persistence mechanism as a single incident thread rather than isolated alerts. That combination is often more informative than any one indicator on its own.

Practitioner takeaway: A RAT incident is not resolved when the visible malware is removed, it is resolved when the persistence path, remote access path, and post-compromise exposure have all been accounted for.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 17, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org