Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What is the difference between a stealer and…
Cyber Security

What is the difference between a stealer and a RAT in a supply chain malware campaign?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Cyber Security

A stealer focuses on collecting secrets such as browser credentials, cookies, tokens, and wallet data, then exfiltrating them quickly. A RAT adds interactive control, letting the attacker issue commands, move around the machine, and maintain access over time. When both are combined, defenders face immediate data theft plus a persistent foothold for follow-on activity.

How a stealer differs from a RAT in a supply chain intrusion

A stealer is built for fast collection: it hunts for browser credentials, cookies, tokens, wallet data, and similar secrets, then gets them out quickly before defenders react. A RAT is built for control: it gives the operator interactive access, command execution, and a way to stay resident on the host. In a supply chain campaign, the distinction often determines whether the malware is a smash-and-grab or an ongoing platform for follow-on abuse.

That difference matters because a stealer can create immediate exposure across downstream accounts and services, while a RAT can turn one compromised endpoint into a pivot point for broader intrusion. Shai Hulud npm malware campaign is a good example of secret theft in a software supply chain context, where the operational priority is to assume exposed tokens and credentials may already have been copied elsewhere.

When both behaviours are present in the same campaign, the attacker gains two different advantages at once: rapid secret harvesting and a durable foothold. That combination is especially damaging in build, developer, and CI/CD environments because stolen secrets can be reused outside the infected host, while interactive access can be used to search for more secrets, alter tooling, or stage the next phase of the operation.

What defenders should look for in the malware and in the environment

On the malware side, stealer behaviour is usually characterised by targeted discovery of high-value identity material, aggressive collection, and short dwell time. RAT behaviour is usually visible through remote command handling, tasking, persistence, file manipulation, process spawning, lateral movement, or staged payload delivery. In practice, the same campaign may begin as a stealer and later unpack RAT-like control, or use a RAT first to locate secret stores and then exfiltrate them.

In supply chain cases, the environment often provides the real signal. Build logs, developer workstations, package managers, browser profile stores, token caches, and CI variables are all attractive because they can contain material that grants access far beyond the compromised machine. tj-actions/changed-files compromise 2025 shows how a poisoned supply chain artifact can expose CI/CD secrets at scale, which is the kind of blast radius a pure stealer is designed to exploit.

RAT indicators are more operationally noisy than stealer indicators, but they can be harder to contain because they enable second-stage decision-making by the attacker. CircleCI breach 2023 is useful for understanding why session theft plus interactive follow-on access is so dangerous: once the attacker can act as a real user, they can reach secrets, keys, and internal systems that a one-time dump might not expose on its own.

Why the distinction changes incident response and containment

The practical response differs because the expected blast radius differs. With a stealer, the immediate question is which secrets may have been copied, whether those secrets unlock other systems, and how far the theft may have propagated through reuse. With a RAT, the immediate question is what the attacker could still do from the live foothold, which accounts or hosts were touched, and whether persistence, scheduled tasks, or remote tooling still exist.

That is why campaign response should not stop at malware removal. If a stealer was present, rotate exposed credentials, revoke sessions, and review downstream access that those secrets could unlock. If a RAT was present, also treat the host as an attacker-controlled workspace until you have evidence that persistence and lateral access paths are gone. In supply chain incidents, both conditions may be true at once, so containment has to address theft and access.

The mix also affects what you should preserve for forensics. Stealer cases often need rapid capture of browser artefacts, token locations, and exfiltration paths. RAT cases often need process trees, command history, network connections, persistence mechanisms, and remote control channels. If you only hunt for one pattern, you can miss the other and understate the incident.

Risk and Threat Considerations

Supply chain malware that combines stealer and RAT functions creates two attack advantages: fast credential loss and durable operator control. That combination increases the chance that stolen secrets will be reused outside the original machine while the attacker continues to operate inside the environment.

Failure mechanism: the stealer extracts identity material quickly, then the RAT preserves access long enough for the attacker to search for more secrets, stage additional payloads, or pivot to other systems before the compromise is discovered.

Impact: defenders may face both immediate data theft and a longer intrusion window, which raises the likelihood of account compromise, follow-on supply chain abuse, and recovery work that extends beyond the infected endpoint.

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, SLSA and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1555 — Credentials from Password StoresStealer campaigns target browser and token stores for credential theft.
T1059 — Command and Scripting InterpreterRATs rely on remote command execution to control the host interactively.
Recommendation — Map secret-harvesting behaviour to T1555 and hunt exposed credential stores quickly. Track command execution paths and isolate hosts that receive interactive tasking.
CIS Controls v8CIS-5 — Account ManagementStolen secrets and RAT access both create account abuse and rotation needs.
Recommendation — Revoke exposed access paths and rotate affected accounts and tokens immediately.
SLSASupply Chain Levels for Software ArtifactsThe subject is a supply chain malware campaign where artifact integrity matters.
Recommendation — Verify build provenance and reject poisoned artifacts before they reach users.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementStolen secrets in a supply chain campaign require rotation and revocation.
Recommendation — Rotate exposed authenticators and invalidate any sessions or tokens they enabled.

Practitioner Guidance

What to verify: confirm whether the malware only harvested secrets, or whether it also created interactive control, persistence, or outbound command channels. That distinction determines whether response should centre on credential rotation alone or on host eradication plus broader intrusion scoping.

Decision rule: if any recovered artefact can authenticate to production, assume downstream compromise until you have revoked or rotated it. If the malware had RAT behaviour, do not trust the host as a source of truth until you have checked for persistence and secondary access paths.

Practitioner takeaway: the real difference is not just feature set, it is blast radius. A stealer steals access; a RAT turns access into an ongoing operator-controlled foothold, and supply chain compromise can combine both.

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 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org