Blog Main Image
November 19, 2026

The Phishing Email That Got Every Detail Right

Most of us were taught the same rule for spotting a scam email. If it opens with "Dear Customer", be suspicious. If it uses your name, mentions your address and quotes a reference number, it's probably genuine. After all, how else would they know?

That rule served people well for years. In October, a group of people in Switzerland found out what happens when it quietly stops being true.

In short: criminals are reusing personal data from earlier breaches to make phishing emails accurate, in one recent case down to the recipient's social insurance number. They are also borrowing urgency from real security news, such as a widely reported PHP vulnerability. Correct details in a message prove only that someone has a copy of your data. They tell you nothing about who is asking.

What happened in Switzerland?

Switzerland's National Cyber Security Centre (NCSC) described the case in its weekly review published on 17 November 2026. On 7 October, a Swiss company that provides employment and management services for domestic helpers reported a data breach and warned the people affected that scammers might try to exploit it.

Just over two weeks later, on 24 October, that is exactly what happened. Scammers sent targeted emails posing as the company. According to the NCSC, the emails contained genuine personal details, including names, addresses and Old Age and Survivors' Insurance (OASI) numbers, roughly the Swiss equivalent of a National Insurance number. The links opened forms that were already filled in with the recipient's own information. The only boxes left empty were for credit card details, including the security code.

Picture that from the recipient's side: a company you really deal with, your name, your home address and a number few organisations should hold. It even saves you the bother of typing.

Why does a pre-filled form feel so trustworthy?

Because it reverses the usual direction of a scam. A crude phishing email asks you for information. This one shows you information first, and that feels like the sender proving who they are, in the same way a bank might quote the last few digits of your card before asking you anything.

The pre-filled fields do something subtler too. They turn the one request that actually matters, the card number and security code, into just another box on a page where every other box is already correct. Nothing about it stands out.

Where does the news story come in?

The same NCSC review describes a second campaign that borrowed credibility from the headlines rather than from a breach. In October, two critical flaws in PHP, the programming language behind a great many websites, were patched. Tracked as CVE-2026-109618 and CVE-2026-109619, they were nicknamed PHP2Shell, and Help Net Security reported that they let attackers run code on web servers without logging in. The Swiss NCSC's own warning of 21 October recommended updating affected systems without delay.

That advice was sound, and it was widely reported. Scammers then sent emails asking recipients to click a link to install an update or find out more. The link led to a fake website. Anyone who entered their login details there risked giving the attackers access to the administration panel of their real site, where they could alter it or take it over.

Notice how little of that email was false. The vulnerability was real. The urgency was real. Being told to patch was good advice. The only lie was the link.

Is this only a Swiss problem?

No. The UK NCSC's guidance on data breaches warns that "Criminals may even send messages pretending to be from an organisation that has suffered a recent data breach", and that such messages may arrive "some time after the breach is made public".

When some ASOS customers received an unauthorised push notification on 6 October, the UK NCSC's statement on the incident reported ASOS's position that names and contact details had been accessed, and that the company did not believe payment card information or account passwords were affected. Even so, the NCSC reminded customers that scam messages can arrive some time after a data breach incident.

The Swiss NCSC puts the timescale more bluntly. Once personal data falls into criminal hands, it says, "it can be used for targeted phishing attacks and other scams months or even years later."

So what was the old rule really testing?

We tend to read a personalised email as a sign that the sender knows us. But the "Dear Customer" rule was never really a test of who sent a message. It was a test of effort. Mass scammers couldn't afford to look up who you were, so a generic greeting gave them away. The rule worked because personal data was expensive to get.

Breaches made it cheap. Once a customer list has been stolen, the details that used to show a sender was genuine become something anyone holding the file can paste into a template. Accuracy now tells you that someone has a copy of your data. That's all it tells you, and it is every bit as true of the criminal as of the company.

Think of a stranger at your door who knows your name, your address and your dog's name. They might be a neighbour. They might also have read the label on your post. Either way, you would want to know which before handing over your house keys.

Pile as many correct details as you like on one side of the scale, and the question on the other side, who actually sent this, doesn't move at all.

Balance scale diagram: a stack of correct personal details on one pan, an unverified sender on the other, with three checks that do confirm who sent a message
Accurate personal details answer the wrong question. Only an independent check tells you who sent a message.

What should individuals do?

The Swiss and UK advice lines up neatly.

  • Treat correct personal details as neutral. The Swiss NCSC is explicit that accurate details in a message do not prove it is legitimate. They are a reason to check, not a reason to trust.
  • If a message mentions a breach, a problem with your account or an urgent update, go to the organisation's website or app yourself rather than using the link or phone number in the message.
  • Never enter card details, security codes or passwords on a page you reached from a link in an email or text.
  • Expect old breaches to echo. If you were told your data was exposed or stolen, expect scam messages to keep arriving long after the news has moved on.
  • In the UK, forward suspicious texts to 7726. If you have lost money, tell your bank and report it to Report Fraud.

What should organisations do?

  • Say plainly that updates arrive through normal channels: vendors, package managers and established IT processes, never a link in an unsolicited email.
  • If you suffer a breach, tell customers how you will and will not contact them, as the Swiss company did. It gives people a reference point when the fake emails turn up.
  • Make sure stolen details are not enough on their own. The UK NCSC recommends passkeys, or strong and separate passwords with two-step verification, so accounts stay secure even if personal data is breached.
  • Run phishing simulations that use this tactic: believable messages that reference real news and contain plausible details. People who have practised verifying a convincing message are better prepared than those taught only to look for spelling mistakes.
  • Make reporting quick and thank people who report, including the false alarms.

The smaller, calmer point

None of this means every personalised email is now fake. Your bank still knows your name. It simply means your name is no longer the evidence. The evidence is the route: a website you typed yourself, a number you already had, an update that arrived the usual way. Stick to the route, and a scammer's carefully copied details stop doing any work.

Key takeaways

  • Scammers in Switzerland used names, addresses and OASI numbers from a reported breach to send pre-filled phishing forms seeking card details.
  • A separate campaign used real news of the PHP2Shell vulnerabilities to push fake "update" links that harvested website logins.
  • Accurate details prove that someone has your data, not who they are.
  • Both the Swiss and UK NCSCs warn that breach-driven scams can arrive long after the breach itself.
  • Verify through a route you control, and never enter card details or passwords via a link in a message.

Frequently asked questions

Why do some phishing emails contain my real name and address?

Usually because those details were exposed or stolen in an earlier data breach, at the organisation being impersonated or somewhere else. Criminals reuse that data to make their messages more convincing.

If an email quotes my National Insurance or account number, does that prove it is genuine?

No. It proves only that the sender has a copy of that information. Contact the organisation through its official website, app or a phone number you already hold before acting.

How long after a data breach should I watch out for scams?

For a long time. The UK NCSC says scam messages may be sent some time after a breach is made public, and the Swiss NCSC warns stolen data can be used months or even years later.

How can a business stop staff falling for fake security update emails?

Set and repeat a clear rule that updates only come through vendors, package managers and normal IT processes. Check vendor advisories directly, and give staff an easy way to report suspicious update requests.

Phishing Tackle offers the tools businesses need to strengthen their human risk strategies, with multi-platform testing, real-time behavioural insights, and actionable data to keep your organisation ahead of modern cyber threats.

Contact us today to learn how Phishing Tackle can help safeguard your organisation from the growing array of cyber risks.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Scroll To Top Arrow