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

Email Attack

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

An email attack is a malicious message-based attack that uses email to deliver fraud, malware, or credential theft. It commonly relies on spoofed sender details, deceptive links, malicious attachments, or impersonation of trusted people to trick a recipient into taking unsafe action or revealing access credentials.

How Email Attack Works

Email attack is effective because it turns ordinary inbox trust into an execution path. The message itself may be the payload, or it may only be the delivery vehicle for a link, attachment, or social engineering prompt that pushes the recipient into disclosure, code execution, or a harmful business action. The core danger is not the message format alone, but the ability of the message to bypass attention and authority checks.

Attackers often rely on sender impersonation, lookalike domains, reply-chain abuse, or urgent language that compresses decision time. In practice, the email is usually designed to create a moment where the recipient acts before verifying identity, context, or request legitimacy.

Common Email Attack Techniques

Phishing, malware delivery, and credential theft are the most familiar outcomes, but email attacks also include invoice fraud, password reset abuse, gift-card fraud, and support impersonation. The technique can be low sophistication or highly targeted, but the common pattern is message-driven manipulation of a human decision.

Attachments may carry macro malware, malicious archives, or staged documents. Links may lead to credential-harvesting pages, consent grants, or fake portal login screens. In more advanced campaigns, the message may redirect the victim to a call or chat channel where the social engineering continues outside the inbox.

Why Email Attacks Remain Effective

Email remains attractive because it is universal, expected, and often allowed to cross trust boundaries by design. Defenses must therefore distinguish legitimate business communication from adversarial communication, which is difficult at scale when attacker language, branding, and timing continuously adapt.

Attackers also benefit from the fact that email can target many stages of the kill chain at once: initial access, credential capture, malware delivery, and follow-on fraud. A single successful message can create broad downstream exposure if the recipient has authority to reset passwords, approve payments, or open a remote access path.

Detection and Defensive Controls for Email Attack

Effective defence depends on layered controls rather than message filtering alone. Mail authentication, attachment and link inspection, tenant hardening, user reporting, and alerting on suspicious mailbox behaviour all matter, because email attacks often evolve after the first message lands.

Practitioners should also watch for signs that an inbox has become part of an attack chain, such as unexpected forwarding rules, unusual sign-in prompts, mass mailbox activity, or repeated failed login attempts after a lure is delivered. For threat-relevant campaign patterns and defender mapping, see MITRE ATT&CK T1667 Email Bombing, Storm-1811 Threat Actor Profile Guide, and AML.T0066 Retrieval Content Crafting for a related view of how message content can be deliberately shaped to manipulate downstream systems.

Response and Recovery After an Email Attack

Once an email attack is suspected or confirmed, response should focus on containment, credential protection, and mailbox review. If a user interacted with the lure, the organisation should assume the message may have exposed authentication material, session tokens, or delegated access paths, not just the visible email content.

Recovery usually requires more than deleting the message. It may require mailbox search and purge, endpoint inspection, user account review, password resets where credentials may have been exposed, and validation that no malicious forwarding, delegation, or persistence mechanism remains in place.

Risk and Threat Considerations

Email attacks are dangerous because they exploit both trust and speed. Even a single successful message can produce credential theft, malware execution, payment fraud, or a foothold for broader compromise, especially when the recipient has elevated access or can initiate further trust decisions.

Failure mechanism: The attacker succeeds when the recipient treats an untrusted message as legitimate, then clicks, opens, pays, signs in, or approves without independent verification.

Impact: The result can be account compromise, malware infection, business email compromise, financial loss, or secondary intrusion from the compromised mailbox or 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, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1566 — PhishingEmail attacks commonly use deceptive messages to gain access or trigger action.
T1114 — Email CollectionEmail compromise often leads to mailbox access and follow-on abuse.
Recommendation — Map suspicious email lures to T1566 and hunt for the delivery, reply, or credential capture chain. Review mailbox access, forwarding, and inbox rules when email attack activity is suspected.
CIS Controls v8CIS-9 — Email and Web Browser ProtectionsEmail attacks are delivered through mail clients and links, so browser and mail protections are central.
Recommendation — Harden mail and browser controls to reduce malicious link, attachment, and impersonation success.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementEmail attacks often aim to steal or abuse passwords, tokens, or other authenticators.
Recommendation — Protect and rotate authenticators that may be exposed through malicious email interaction.
OWASP ASVSV10 — OAuth and OIDCEmail lures can redirect users into fake sign-in and consent flows.
Recommendation — Apply strong federation and consent controls to reduce credential and token theft from email lures.

Practitioner Guidance

Why practitioners should care: Email attack handling is not just a mail-filtering problem, it is an identity, endpoint, and business-process problem. Defenders need to assume that a successful message may be the first step in a broader compromise rather than the final event.

What to watch for: Prioritise messages that pressure urgency, request credential reuse, redirect to external sign-in pages, or ask the user to bypass normal process. Pay special attention when the lure targets finance, support, executive, or IT workflows, because those paths can convert one message into disproportionate downstream impact.

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