Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› APT35 (Charming Kitten)
Threats, Abuse & Incident Response

APT35 (Charming Kitten)

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

APT35 (Charming Kitten) is a threat actor group associated with phishing, credential theft and account takeover against targets of intelligence value. Defenders should watch for impersonation lures, password reset abuse, suspicious OAuth consent activity and unusual mailbox access, then enforce phishing-resistant MFA, tighten mail filtering and investigate anomalous sign-ins quickly.

What APT35 Means in Practice

APT35, also known as charming kitten, is best understood as a persistent phishing and account-compromise threat. The group’s value to defenders is not just the label, but the repeatable pattern: social lures, credential theft, mailbox abuse and access that blends into normal user activity.

Because the group is associated with intelligence-driven targeting, the practical question is often less “who are they?” and more “what access did they gain, and how far did it spread?” That makes campaign tracing, mailbox review and identity-centric investigation central to understanding the term.

Why This Group Matters to Defenders

APT35-style operations are dangerous because they often begin with ordinary-looking emails and end with durable access. Once credentials or tokens are captured, attackers can pivot into mailboxes, password reset flows and connected applications without immediately triggering obvious malware detections.

The main defensive challenge is that these compromises can look legitimate from the perspective of the target system. A successful login, an OAuth grant or a mailbox rule may be an attacker action that appears to the platform as normal user behaviour.

Common Attack Patterns Associated with APT35

The group is commonly linked to impersonation, credential harvesting, session theft and follow-on account takeover. In practice, that means defenders should pay attention to brand impersonation, urgent account prompts, fake login portals and messages designed to trigger a password reset or consent grant.

Mailbox-centric abuse is especially important because access to email can unlock other services. If a threat actor can read messages, search for reset links, approve risky prompts or create forwarding rules, they may sustain access even after an initial password change.

For a useful overview of how threat actor naming, campaign clustering and aliasing work, see the Threat Actor Groups Guide.

How to Investigate and Reduce Exposure

Exposure checks should start with user inventory, email protection and recent sign-in review. Look for suspicious inbox rules, unusual OAuth consent events, impossible travel, legacy authentication use, and alerts from the identity provider or mail platform that indicate account misuse.

Mitigation is strongest when phishing-resistant MFA is paired with tight mail filtering, limited consent permissions and fast review of anomalous sign-ins. When compromise is suspected, treat the mailbox as a control point, not just a communications tool, because it may reveal persistence, lateral movement and secondary targets.

Defenders should map these behaviours to adversary tradecraft in the MITRE ATT&CK Enterprise Matrix and use phishing-resistant authentication guidance from NIST SP 800-63 Digital Identity Guidelines when reviewing sign-in protections.

Risk and Threat Considerations

APT35 is especially risky because the campaign path often starts with human trust and ends with control over identity-bearing systems such as email and federated accounts. That gives the operator a quiet way to persist, impersonate the victim and search for further access opportunities.

Failure mechanism: The attacker steals credentials or session access through phishing, then abuses mailbox or account trust to reset passwords, approve prompts, create forwarding rules or reach connected services.

Impact: The result can be account takeover, message exposure, identity impersonation and wider compromise of the victim’s connected business or intelligence-related accounts.

Standards & Framework Alignment

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

MITRE ATT&CK and OWASP API Security Top 10 address the attack and risk surface, while NIST SP 800-63 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1566 — PhishingAPT35 operations center on phishing and credential theft as an intrusion path.
Recommendation — Map lure patterns to T1566 and hunt for email-delivered initial access indicators.
NIST SP 800-63AAL2 — Authenticator Assurance Level 2The term directly involves account takeover and phishing-resistant authentication decisions.
Recommendation — Require phishing-resistant authenticators to raise assurance against account takeover.
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)The threat targets organisational user accounts and their authentication controls.
AU-6 — Audit Record Review, Analysis, and ReportingMailbox abuse and sign-in anomalies require review of authentication and mail activity records.
Recommendation — Verify organizational-user authentication controls and investigate anomalous sign-ins. Review authentication and mail audit records for takeover indicators and persistence.
OWASP API Security Top 10API2 — Broken AuthenticationAccount takeover and stolen-session abuse align with authentication failure patterns.
Recommendation — Check API-authentication dependencies for weaknesses that could enable token or session abuse.

Practitioner Guidance

What to watch for: Treat mailbox rules, OAuth grants and password reset activity as high-signal investigation points when they appear alongside sign-in anomalies or suspicious lures. The presence of these events often means the compromise has moved beyond a single phishing click.

Governance implication: Response ownership should sit with identity, messaging and incident response teams together, because the threat crosses mail, authentication and account recovery boundaries. If the compromise is confirmed, rotate affected credentials and review all sessions and delegated access linked to the account.

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