What Causes Email Spoofing Attacks at Work?

A convincing email appearing to come from a director, supplier or trusted colleague can be enough to trigger a fraudulent payment, disclose sensitive information or spread malware. Understanding what causes email spoofing attacks helps businesses focus on the real issue: attackers are exploiting the trust people place in familiar names and established processes.

Email spoofing is not always a sign that someone has broken into your systems. In many cases, criminals simply manipulate the visible sender details of an email so it looks as though it came from a legitimate address. The message can then be tailored to a particular business, department or individual, making it far more believable than a generic phishing attempt.

What causes email spoofing attacks?

At its core, email spoofing exists because the original email system was designed to deliver messages reliably, not to prove beyond doubt who sent them. Although modern protections have improved matters significantly, a receiving mail server can still be presented with sender information that is misleading, incomplete or deliberately forged.

Attackers take advantage when technical email controls are absent, poorly configured or not enforced by the receiving organisation. They also rely on everyday business pressures: busy finance teams, urgent supplier requests, senior staff travelling, and colleagues who naturally want to be helpful.

The most successful attacks normally combine a technical weakness with a human one. A forged sender address alone may not fool a well-prepared recipient. A forged address accompanied by a genuine-looking invoice, a familiar signature and an urgent request for payment is much more likely to succeed.

How attackers make a message look genuine

Forged sender details

The visible “From” field in an email can be made to display almost any name or address. An attacker may send a message that appears to come from accounts@yourcompany.co.uk or from a director’s name, even though it originated elsewhere.

Without effective authentication checks, the recipient’s mail system may accept that claim. This is why a message can look legitimate at first glance while its true sending source tells a different story.

Lookalike domains and display names

Not every apparent spoof uses a forged domain. Criminals often register domains that closely resemble a real one, perhaps replacing a letter, adding a hyphen or using a different top-level domain. They may also use a free email account but set the display name to match a director, supplier or member of staff.

For example, an email from a lookalike address can be displayed simply as “Jane Williams”. On a mobile phone, where the full address is not always immediately visible, that may be enough to cause confusion. These messages are technically different from direct domain spoofing, but the business risk is similar.

Compromised genuine accounts

Sometimes the email really does come from a trusted account. A criminal who obtains a user’s password, bypasses weak access controls or steals an active session can send messages from a legitimate mailbox. This is particularly dangerous because standard sender checks may pass.

Compromised accounts are often used in business email compromise attacks. The attacker may quietly monitor conversations, learn how a supplier invoices the business and intervene at the point when a payment is due. A change-of-bank-details request sent within an existing email thread can look highly credible.

Weak or incomplete email authentication

Three standards work together to help receiving systems assess whether email is genuine: SPF, DKIM and DMARC.

SPF identifies which servers are authorised to send email for a domain. DKIM adds a digital signature to verify that a message has not been altered and that it was sent by an approved system. DMARC tells receiving providers how to handle messages that fail those checks and supplies reports that reveal unauthorised use of a domain.

Problems arise when these records are missing, incomplete or configured only to monitor failures rather than reject them. It is common for businesses to have some authentication in place but no enforcement policy. That may provide useful visibility, yet it does not fully prevent attackers from impersonating the domain.

Configuration needs care. A business may send email through Microsoft 365, a hosted email platform, a marketing platform, a customer relationship system, an invoicing service or a website. Every legitimate sender must be accounted for. Overly broad SPF records or poorly aligned DKIM settings can create gaps, while rushed changes can interrupt genuine mail flow.

Poorly protected domains

A business may own several domains, including older brands, domains used for campaigns or domains reserved for future use. These are easy to overlook. If an unused domain has no DMARC policy, criminals may use it to impersonate the organisation or exploit its similarity to the main brand.

Domain protection is therefore not a one-off technical task. It requires an inventory of domains and sending services, regular review, and clear ownership when systems or suppliers change.

Why people remain central to the risk

Technical controls can block a large proportion of malicious messages, but they cannot remove every risk. Attackers adapt quickly, particularly when they have researched an organisation through public websites, social media profiles or previous data breaches.

They may know who approves payments, which suppliers a company uses or when a senior manager is away. They use urgency to discourage verification: a confidential acquisition, an overdue invoice, a last-minute payroll correction or a request from a director who is “in a meeting”.

The most common weakness is not carelessness. It is a process that permits a single person to approve an unusual financial or data-related request based only on email. People working under pressure need a clear, practical way to pause and check without feeling that they are delaying the business.

The controls that reduce spoofing risk

Effective protection is layered. No single setting, training session or security product is sufficient on its own. For small and medium-sized businesses, the priority is to put proportionate controls around the most damaging outcomes: fraudulent payments, account takeover, data loss and disruption.

A sensible programme should include the following measures:

  • Configure SPF, DKIM and DMARC correctly for every domain, then move DMARC from monitoring towards a quarantine or reject policy once legitimate sources have been validated.
  • Protect email accounts with multi-factor authentication, strong conditional access policies and prompt removal of access when staff leave or change role.
  • Use email security filtering that checks sender reputation, malicious links, attachments and impersonation patterns before messages reach users.
  • Train staff with realistic examples and make reporting suspicious emails quick and straightforward.
  • Require an independent verification step for changes to supplier bank details, high-value payments, payroll amendments and requests for sensitive information.
  • Keep systems, devices and browsers patched, as account compromise often begins with a separate weakness rather than the email itself.

The verification step deserves particular attention. If a supplier asks to change bank details, staff should use a known telephone number from an existing record, not a number included in the email. The same principle applies to requests that appear to come from a director. A quick call, Teams message or face-to-face check can prevent a significant loss.

Email authentication needs ongoing management

DMARC is often discussed as if it were a simple switch. In practice, it is a controlled process. Start by identifying every system that sends email using your domain. Review authentication reports, correct failures and make sure legitimate services are properly aligned. Only then should enforcement be increased.

This approach avoids an unnecessary trade-off between security and reliable communication. A strict policy implemented without preparation can cause genuine messages to be rejected. Leaving a policy in monitoring mode indefinitely, however, leaves the organisation exposed to impersonation.

For businesses without an in-house security team, this is where specialist support can be valuable. iData can help organisations assess their email environment, align protection with existing workflows and provide ongoing support rather than leaving a complex configuration unmanaged.

What to do if a spoofing email gets through

If a suspicious message arrives, do not reply, click links, open attachments or use contact details within the email to verify it. Report it to your IT team or managed support provider. If payment details have been changed or money has been sent, contact the bank immediately and preserve the email, including its headers where possible.

Where an account may be compromised, change credentials, revoke active sessions, review mailbox forwarding rules and check for unauthorised access. It is also worth reviewing whether other staff or suppliers received similar messages. Attackers frequently target multiple people while posing as the same individual.

A calm, documented response matters. The aim is not to blame the person who received the message, but to contain the risk, establish what happened and strengthen the controls that should stop the next attempt.

Email will remain a critical business tool, which is precisely why criminals continue to impersonate it. The safest organisations treat every unexpected request involving money, credentials or confidential information as a process to verify, not merely a message to answer.

« Back to Blog