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

Raccoon

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

Raccoon is malware sold as an infostealer and malware-as-a-service offering. It is typically used to harvest browser data, saved passwords, cookies and cryptocurrency wallet information, then send that data to an operator for account takeover and follow-on fraud.

What Raccoon Is Built To Do

Raccoon is commodity malware sold as a service, which means the operator rents a ready-made theft capability rather than building it from scratch. That model lowers the barrier to entry for opportunistic intruders and makes the malware easier to reuse across campaigns, especially when the goal is credential theft, session theft and financial fraud.

What Raccoon Steals And Why That Matters

Raccoon is typically used to collect browser-stored data, saved passwords, cookies and cryptocurrency wallet material. Those data types are valuable because they can expose active sessions, bypass some login friction and support immediate account takeover without needing a full password reset cycle.

In practical terms, cookies can be as dangerous as passwords when they preserve authenticated sessions, while wallet information can create direct financial loss. Theft of this material also gives attackers a foothold for follow-on abuse, including fraud, impersonation and reuse of recovered credentials elsewhere.

How Raccoon Fits The Malware-As-A-Service Ecosystem

Malware-as-a-service turns a single infostealer into a repeatable access pipeline. The developer, affiliates and downstream operators can each focus on a different stage of abuse, such as delivery, theft, collection or monetisation, which makes takedown and attribution harder.

This business model also encourages rapid iteration. New loaders, delivery methods and theft modules can appear quickly, and operators can swap infrastructure or payloads while keeping the same core collection logic. The result is a resilient criminal supply chain built around stolen secrets and browser artefacts.

What Organisations Should Understand About Exposure

Exposure is usually broader than a single infected endpoint. Any unmanaged browser profile, reused password, synced credential store or exposed workstation can become a source of stolen access material, especially where users hold privileged, finance or cryptocurrency-related accounts.

That is why asset visibility and user behaviour both matter. A single successful infection can disclose credentials that were never intended to leave the device, and the attacker may not need continued malware presence once the harvested data is exported.

Strong identity and access controls help limit the downstream value of stolen material, and you can map that response thinking to NIST SP 800-53 Rev 5 Security and Privacy Controls, which includes controls for authentication, access control, logging and system integrity. If sessions are the real prize, organisations should also treat NIST SP 800-63 Digital Identity Guidelines as a useful reference for stronger authenticators that reduce the usefulness of stolen passwords alone.

How To Respond After Suspected Raccoon Activity

When Raccoon is suspected, response should focus on both endpoint cleanup and post-compromise review. Removing the malware does not by itself undo session theft, password exposure or wallet compromise, so organisations should assume harvested material may already be circulating.

That means reviewing browser sessions, recent sign-ins, token use, password reuse and any accounts that stored sensitive credentials on the affected machine. A broader detection and containment lens is also warranted, and the MITRE ATT&CK Enterprise Matrix is useful for mapping credential access, persistence and follow-on movement, while the NIST Cybersecurity Framework 2.0 helps structure the response across identify, protect, detect, respond and recover.

Risk and Threat Considerations

Raccoon is dangerous because infostealers convert a single endpoint compromise into reusable access material. Once passwords, cookies or wallet data are exfiltrated, the attacker may be able to bypass normal authentication controls, impersonate the user, and pivot into downstream fraud or account takeover.

Failure mechanism: The malware harvests secrets and session artefacts from the browser profile, then exports them to an operator who can reuse the data before defenders notice the original infection.

Impact: Organisations can lose active sessions, customer or employee accounts, and in some cases cryptocurrency assets, while investigation becomes harder because the malicious access may look like legitimate login activity.

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

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementRaccoon steals passwords and session material that IA-5 is meant to manage.
AC-2 — Account ManagementAccount takeover from harvested secrets directly affects account lifecycle and access control.
AU-6 — Audit Record Review, Analysis, and ReportingPost-exploitation review depends on log analysis of suspicious logins and session reuse.
Recommendation — Rotate exposed authenticators and revoke stale credentials after infostealer compromise. Disable or reissue compromised accounts and review dormant or reused access paths. Correlate sign-in and session logs to find abuse after suspected credential theft.
NIST CSF 2.0DE.CM-01 — Monitoring for Anomalies and EventsRaccoon is detected through abnormal endpoint, login and exfiltration activity.
Recommendation — Watch for unusual host activity and login anomalies that suggest infostealer execution.
MITRE ATT&CKT1555 — Credentials from Password StoresRaccoon’s core theft pattern includes browser-stored passwords and similar secrets.
T1539 — Steal Web Session CookieSession cookies are a key abuse path for account takeover after theft.
Recommendation — Hunt for credential-store access and protect browser vaults and synced secrets. Search for session-cookie theft and revoke sessions when compromise is suspected.
CIS Controls v8CIS-5 — Account ManagementThe malware’s end goal is account misuse, making account lifecycle control central.
Recommendation — Enforce account review, revocation and rapid reset for exposed user access.

Practitioner Guidance

What to watch for: Treat browser-stored credentials, synced passwords and long-lived sessions as high-value targets, not convenience features. If a user or device is compromised, assume the attacker may already possess reusable access material and prioritise revocation over simple malware removal.

Governance implication: Organisations should make session revocation, credential rotation and device-based trust review part of the standard incident playbook for infostealer cases. Password resets alone are often insufficient if cookies, tokens or other session artefacts remain valid.

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