Phishing awareness case study

Inside a Sextortion Phishing Email: How to Identify Fake Hacking Threats

Cybercriminals send emails claiming to have hacked a computer, accessed its webcam or recorded private activity, then threaten to expose the "material" unless a cryptocurrency ransom is paid.

Receiving such an email does not, by itself, prove that your device has been compromised.

Laptop protected by a shield while a suspicious email with a warning sign is stopped

What you'll learn

  • How a real sextortion email was built to frighten its recipient
  • Which parts were claims by the sender β€” and what was actually verified
  • What SPF Softfail and DMARC Fail mean in the email headers
  • Calm, proportionate steps to take if one reaches you
Case study

The email: an anonymised summary

A message like this reached a client's mailbox address on 11 November 2026 and was quarantined by the incoming email filter. Personal details have been removed and the domain replaced with example.com.
Claims made by the senderNot established facts
Subject
SECURITY INCIDENT: Unauthorized Access Detected on Node
  • Pretended to come from the recipient's own email address.
  • Claimed spyware had been installed while the recipient browsed an inappropriate website.
  • Claimed full access to the webcam, microphone, emails, chats and contacts.
  • Threatened to send an alleged private recording to all of the recipient's contacts.
  • Demanded USD 950 in Bitcoin.
  • Set a 50-hour deadline, supposedly starting when the email was opened.
  • Warned the recipient not to tell anyone about the message.

The Bitcoin wallet address and the original recipient are deliberately not published.

What the evidence shows
  • No proof of access. No image, file name, contact or detail that only someone with real access would know.
  • The sender address was forged. The message was not sent through the domain's authorised mail servers: SPF soft-failed and DMARC failed.
  • A generic template. The wording matches mass-mailed extortion scams, including the false claim that a "notification" fires when the email is opened.
  • Stopped before the inbox. The filter classified the message as phishing and quarantined it under the domain's DMARC policy.
Original message

The original email, word for word

This is the message exactly as it was quarantined, with only our client's details hidden. It is shown as text, not a screenshot, and contains no links.

What we changed

  • Our client's name, mailbox and domain are replaced with [email protected].
  • The Bitcoin wallet address is removed so nobody pays it by mistake.
  • Two explicit words are masked with asterisks.
  • Message, filter and quarantine IDs are removed from the headers.

Everything else β€” wording, spelling, punctuation and the odd .^. β€” is unchanged.

Received the same email?

The text is copied word for word to thousands of people. Do not pay or reply β€” see what to do.

Show the full headers (anonymised)
Received: from static-190-181-30-110.acelerate.net ([190.181.30.110]) by mx278.antispamcloud.com with esmtp (Exim 4.94.2) (envelope-from <[email protected]>) id [removed] for [email protected]; Wed, 11 Nov 2026 07:57:33 +0100
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From: [email protected]
Mime-Version: 1.0 (1.0)
Date: Wed, 11 Nov 2026 02:51:32 -0400
Subject: SECURITY INCIDENT: Unauthorized Access Detected on Node
Message-Id: <[email protected]>
To: [email protected]
X-Mailer: iPhone Mail (21G93)
Received-SPF: softfail (mx278.antispamcloud.com: transitioning domain of example.com does not designate 190.181.30.110 as permitted sender) client-ip=190.181.30.110; [email protected]; helo=static-190-181-30-110.acelerate.net;
X-SPF-Result: mx278.antispamcloud.com: transitioning domain of example.com does not designate 190.181.30.110 as permitted sender
Authentication-Results: mx278.antispamcloud.com; iprev=pass (static-190-181-30-110.acelerate.net) smtp.remote-ip=190.181.30.110; spf=softfail smtp.mailfrom=example.com; dmarc=fail header.from=example.com
Authentication-Results: antispamcloud.com; spf=softfail [email protected]
X-N-ableSpamExperts-Class: phish
X-N-ableSpamExperts-Evidence: DMARC - Quarantine
X-Filter-ID: [removed]
X-Report-Abuse-To: [email protected]
X-Complaints-To: [email protected]
X-Quarantine-Release-ID: [removed]
Manipulation techniques

Anatomy of the scam

These six techniques appear in almost every sextortion email. None of them is evidence that a device was accessed.

Impersonation

The From and To fields both show the recipient's own address, so the message seems to come from inside the mailbox. The address was simply typed in β€” spoofed.

Fear

The sender claims to hold a compromising recording. Embarrassment is meant to stop the recipient from thinking clearly or asking for help.

Technical intimidation

Words like Trojan, spyware, driver-based malware, webcam and microphone make the threat sound credible, but no technical proof is offered.

Urgency

A 50-hour deadline and a claimed "countdown" pressure the recipient to pay before checking the facts.

Extortion

Payment in cryptocurrency is demanded because transfers are hard to reverse and the receiver is hard to identify.

Isolation

The recipient is told not to share the message. Isolation keeps victims away from the IT teams and friends who would recognise the scam.

Technical analysis

What the email headers reveal

Headers record how a message travelled and how the receiving system judged it. These are the relevant results from this message.
Email header evidence
FieldObserved result
Observed sending IP190.181.30.110

The mail server endpoint that delivered the message. It does not identify the person behind it.

Observed sending hostnamestatic-190-181-30-110.acelerate.net

Reverse DNS for that IP (iprev=pass only means the name and IP match each other).

SPF Softfail

The sending IP was not authorised under the domain's SPF policy.

DMARC Fail

The message did not meet the domain's DMARC authentication and alignment requirements.

Receiving security classification Phish

The receiving gateway classified the message as phishing.

Security gateway N-able SpamExperts

Applied the domain's DMARC quarantine policy, so the message never reached the inbox.

Sanitised header excerpt

Received-SPF: softfail
  client-ip=190.181.30.110

Authentication-Results:
  spf=softfail smtp.mailfrom=example.com;
  dmarc=fail header.from=example.com

X-N-ableSpamExperts-Class: phish
X-N-ableSpamExperts-Evidence: DMARC - Quarantine

Important limitation

In this context these results are strong warning signs, but authentication failures alone do not prove who sent the message, and they say nothing about whether any device was compromised. The IP address identifies the mail-sending endpoint that was observed, not the criminal.

SPF Softfail

The observed sending IP was not authorised under the domain's SPF policy. The precise meaning depends on the published SPF record β€” a softfail (~all) asks receivers to be suspicious rather than reject.

DMARC Fail

The message did not satisfy DMARC: neither SPF nor DKIM passed in alignment with the domain shown in the From address.

SpamExperts: phish

The receiving gateway classified the message as phishing and applied the domain's published DMARC quarantine policy.

Enet Email Header Analyzer report for the sextortion email: trust score 40, treat as suspicious, SPF softfail, DMARC fail, not DKIM signed
Enet Email Header Analyzer

The same headers, checked with our free tool

We pasted the anonymised headers above into our Email Header Analyzer. It gave the message a trust score of 40 out of 100 and told us to treat it as suspicious:

  • DMARC failed β€” nothing proves the message came from the domain in the From line.
  • SPF soft fail β€” the sending server is not authorised for that domain.
  • No DKIM signature β€” nothing shows the message is unaltered.

The tool works entirely in your browser, so a suspicious message you paste is never uploaded. Screenshot taken 13 November 2026.

Check an email yourself
Email authentication

How SPF, DKIM and DMARC work

Together, these DNS records help receiving mail systems decide whether a message is authorised to use a domain.

SPF

Lists the mail servers authorised to send email for a domain.

DKIM

Adds a cryptographic signature to each message that receiving systems can verify.

DMARC

Checks that SPF or DKIM align with the visible From domain, and tells receivers how to handle messages that fail.

  1. Step 1

    Sending server

    Delivers the message and claims a sender domain.

  2. Step 2

    SPF & DKIM checks

    Is the IP authorised? Is the signature valid?

  3. Step 3

    DMARC alignment & policy

    Do the results match the From domain? Monitor, quarantine or reject?

  4. Step 4

    Receiving mail system

    Delivers, quarantines or rejects the message.

A correctly configured DMARC policy helps reduce exact-domain impersonation. It does not eliminate phishing: criminals can still use lookalike domains or free email accounts. Learn more in our guide to email spoofing.

Your next steps

What to do if you receive a sextortion email

  1. 1Do not panic. The claims may be completely fabricated.
  2. 2Do not pay the ransom.
  3. 3Do not reply to the sender.
  4. 4Do not click suspicious links or open unexpected attachments.
  5. 5Keep the original email and its full headers for investigation.
  6. 6Report the message to your email administrator or security provider.
  7. 7If you have concerns, review recent sign-ins and active sessions on important accounts.
  8. 8Change passwords if there is evidence of account compromise, and use unique passwords.
  9. 9Turn on multi-factor authentication.
  10. 10Run an updated security scan if you suspect your device may be compromised.
Phone approving a two-factor sign-in beside a padlock and a shield

Already paid?

Contact the financial or cryptocurrency service you used immediately, and report the incident to the authorities β€” in Kenya, the Directorate of Criminal Investigations or the National KE-CIRT/CC.

Keep your response proportionate to the evidence. There is no need to reinstall your computer or change every password because of this email alone.

Answers

Frequently asked questions

01Does receiving this email mean my webcam has been hacked?
No. Receiving the message alone does not establish that anyone accessed your webcam or device. The same text is sent to very large numbers of people, and it contains no proof.
02Can someone hack my computer just by sending an email?
Normally, simply receiving an email does not give the sender access. Software vulnerabilities can be exploited in some circumstances, which is why updates matter, but the message itself is not proof of compromise.
03Can the sender know when I open an email?
Some emails use tracking pixels or remote images to report that a message was opened. That does not give the sender access to your camera, microphone or files. Blocking remote images in your email app prevents it.
04Should I pay the Bitcoin ransom?
No. Payment does not prove the sender has any material, does not guarantee they will delete anything and often leads to further demands.
05What does SPF Softfail mean?
It indicates that the sending IP was not authorised under the domain's SPF policy. Softfail (~all) asks receivers to treat the message with suspicion rather than reject it outright; the exact meaning depends on the published SPF record and how it is evaluated.
06What does DMARC Fail mean?
The message did not meet the domain's DMARC requirements: it did not pass SPF or DKIM in a way that aligns with the domain in the visible From address. The receiver then applies the domain's DMARC policy β€” in this case, quarantine.
For business owners & IT teams

Recommendations for domain and email administrators

The controls that let this message be identified and quarantined automatically.
  • Publish and maintain an accurate SPF record.
  • Enable DKIM signing for all outbound mail.
  • Publish a DMARC record and monitor its aggregate reports.
  • Move to an enforcement policy (quarantine or reject) after validating every legitimate sending source.
  • Require MFA for email accounts and administrative access.
  • Monitor suspicious outbound mail and unusual account sign-ins.
  • Keep mail servers, control panels and endpoints patched.
  • Give staff a clear, simple way to report suspicious messages.

Do not rush enforcement

Publishing an aggressive SPF or DMARC policy before you have identified every legitimate sending service β€” mail server, website forms, invoicing and newsletter tools β€” can block genuine business email. Start with monitoring, review reports, then tighten.

Report a suspicious email

Received a suspicious email?

Do not forward it to strangers or publish personal information. Preserve the original message and full headers, then report it to your organisation's IT team or email provider.

If Enet hosts or filters your email, our support team can help you check your filtering and domain settings.

Contact Enet support
Keep learning

More phishing and scam guides

Stay safe online

Stay alert. Verify before you trust.

Phishing attacks rely on fear, urgency and deception. Take a moment to verify suspicious messages, protect your accounts with multi-factor authentication and report suspected scams. Do not let threats pressure you into paying cybercriminals.

  • Verify first
  • Turn on MFA
  • Never pay
  • Report it