Email spoofing is all about sending out emails that seem legitimate, but often leave victims feeling pain. In keeping with that mindset, the number of email spoofing attacks from April to May, nearly doubled to 8,204 from 4,440.

This benefits the attacker by allowing them to download malware, gain access to systems or data, access personal details, transfer money and can also be part of larger, multi-stage attacks, such as those to dox corporations, according to researchers at Kaspersky.

These types of attacks can occur when using what’s called “legitimate domain spoofing,” where someone inserts the domain of the organization being spoofed into the “From” header, making it incredibly difficult to distinguish a fake email from a real one. They can also use “display name spoofing”, whereby attackers spoof the individual making it look as if it’s been sent by a real employee of the company.

More sophisticated spoofing attacks involve lookalike domains where the attackers use specific registered domains that look similar to those of legitimate organizations.

“Spoofing may seem primitive when compared to some of other techniques used by cybercriminals, but it can be very effective,” said Roman Dedenok, security researcher at Kaspersky. “It can also just be the first stage of a more complex business email compromise (BEC) attack — attacks that can lead to identity theft and business downtime, as well as significant monetary losses. The good news is that there are a range of anti-spoofing protection solutions available and new authentication standards that can keep your business email secure.”

Schneider Bold

In reality SMTP (Simple Mail Transfer Protocol, the main email transmission protocol in TCP/IP networks) offers no protection against spoofing, so it is fairly easy to spoof the sender’s address. In fact, all the would-be attacker needs is a tool for choosing in whose name the message will arrive. That can be another mail client or a special utility or script, of which there is no shortage online.

Email spoofing is used in fraudulent schemes and targeted attacks against organizations. Cybercriminals use this technique to convince victims that a message came from a trusted sender and nudge them into performing a specific action, such as clicking a phishing link, transferring money, downloading a malicious file, etc. For added credibility, attackers can copy the design and style of a particular sender’s emails, stress the urgency of the task, and employ other social engineering techniques.

In some cases, fake emails form part of a multi-stage attack, the first phase of which requires no suspicious actions on the part of the victim.

The simplest form of the technique is legitimate domain spoofing. This involves inserting the domain of the organization being spoofed into the From header, making it extremely difficult for the user to distinguish a fake email from a real one.

To combat spoofing, several mail authentication methods have been created that enhance and complement each other: SPF, DKIM and DMARC. By various means, these mechanisms verify the message was actually sent from the stated address.

The SPF (Sender Policy Framework) standard allows a mail domain owner to restrict the set of IP addresses that can send messages from this domain, and lets the mail server check that the sender’s IP address is authorized by the domain owner. However, SPF checks not the From header, but the sender’s domain specified in the SMTP envelope, which is used to transmit information about the email’s route between the mail client and the server, and is not shown to the recipient.

DKIM solves the problem of sender authentication by means of a digital signature generated on the basis of a private key stored on the sender’s server. The public key for authenticating the signature is placed on the DNS server responsible for the sender’s domain. If in reality the message was sent from a different domain, the signature will be invalid. However, this technology has a weakness: An attacker can send a fake email without a DKIM signature, and the message will be impossible to authenticate.

DMARC (Domain-based Message Authentication, Reporting and Conformance) will check the domain in the From header against a DKIM/SPF-validated domain. With DMARC, a message with a spoofed legitimate domain fails authentication. However, if the policy is strict, DMARC can also block wanted emails.

Click here for more information on the report.

Pin It on Pinterest

Share This