How to report phishing in Switzerland
How to report phishing in Switzerland
You report phishing in Switzerland in two layers: first inside your company so IT can protect mailboxes and payments, then optionally to the National Cyber Security Centre (BACS) so analysts can warn others. Most SMEs are not legally required to report every suspicious mail to BACS. Voluntary reports still matter. In the second half of 2025, BACS received about 29’006 voluntary reports and 145 under the mandatory cyberattack duty; fraud made up about 52 % of submissions (BACS semi-annual report 2025/2). Start with your employer’s channel. External reporting comes after you preserved headers and stopped spreading live links.
This how-to is for office staff and the person who «does IT» in a Swiss firm of roughly 20 to 250 employees. It does not repeat the first hour after a click; see clicked a phishing link at work. If personal data may have left the firm, documentation habits overlap with data breach logs.
Report internally the same day
Use the phishing mailbox, ticket system, or MSP address your company published. Include time, subject, and whether anyone clicked or typed credentials.
Preserve evidence safely
Forward as attachment or use «report message» in Outlook so headers stay. Do not click links again. IT may ask for the original .eml file.
Block and warn
IT blocks sender domains or signs, and sends a short internal warning without naming individuals unless a payment left the account.
Report voluntarily outside if useful
After internal handling, use antiphishing.ch or the BACS reporting page. Check bacs.admin.ch before you submit; form URLs move.
What to send internally
- Full message with headers (or IT’s reporting button in Microsoft 365)
- List of people who clicked, if known
- Any related SMS or voicemail number
- Whether a payment or new IBAN was requested
- Ticket or mailbox name you used, for later insurer or audit questions
Finance must know if the mail mentioned invoices or IBAN changes, even when nobody paid. Business e-mail compromise often chains mail with follow-up calls (BACS on BEC).
BACS, antiphishing.ch, and when to use which
External reporting is voluntary for most companies. It helps block fake sites, especially on .ch or .swiss domains, and feeds national warnings.
Share of BACS submissions in H2 2025 classified as fraud, per the semi-annual report. Not our survey.
Quick path, no reply needed: forward the suspicious mail to reports@antiphishing.ch or submit the link at antiphishing.ch. That channel is aimed at phishing and fake websites.
Path when you want BACS to see full context: start from the BACS reporting page. The page is in German. The exact form address changes; the reporting page is the stable entry BACS lists.
Do both only if IT asks you to. A duplicate with stripped headers does not help analysts. One clean .eml with headers is enough.
CEO-style payment requests are common in the same statistics stream: BACS counted 719 CEO-fraud reports in 2024 and 971 in 2025 (BACS week 4/2026). Mention payment pressure in the internal report even when you skip external filing.
What not to forward
- Do not forward the live mail into WhatsApp, Teams chat, or a group thread. You copy active links to people who have not clicked yet.
- Do not click «just to see» whether the page still loads. IT needs the message, not another visit.
- Do not send only a screenshot of the subject line. Headers carry return-path, authentication results, and routing IT uses for blocks.
- Do not mail the sample to your private Gmail «to keep a copy». Use the ticket or security mailbox.
- Do not attach passwords, one-time codes, or card numbers in the same ticket as the phishing mail.
- Do not wait until Monday if the mail asks for an urgent transfer the same afternoon.
If someone already entered credentials, say that in the first sentence of the internal report so resets happen before you draft an external note.
Suspicious SMS or parcel links belong in the same internal report as mail phishing. A number and a screenshot without a clickable link are enough for the first escalation. Externally, report the URL to antiphishing.ch once IT has started the internal block. Do not mix smishing into an invoice thread while finance is still checking whether a real supplier wrote.
What BACS reporting is not
It is not a substitute for a police report when money left the account. It is not an FDPIC data-breach notification. It does not automatically trigger an investigation of your firm. Analysts aggregate campaigns to issue warnings. A voluntary report does not replace your internal ticket.
A made-up example: Friday afternoon reporting chain
A made-up example: a 60-person logistics firm near Basel. On Friday at 14:40 an accountant receives a fake SBB refund mail. She reports via the «security@» address, attaches the .eml, and states she did not click. By 15:10 IT blocks the domain in the filter and sends a three-line note to all staff. On Monday the office lead files a voluntary report through the BACS reporting page with the same attachment and notes the domain. No customer data left the firm; no FDPIC filing follows. The internal ticket closes with «blocked» and is kept for audit.
Who can skip external reporting
If IT already sees the same campaign nationally, your duplicate helps less, but it still does not hurt when headers are clean. If you lack headers and only have a screenshot, fix internal process first. External reporting never replaces the internal one.
Report inside when
- Any suspicious mail or SMS
- After a click or password entry
- When payment instructions change
Consider BACS or antiphishing.ch when
- New domain or large wave at your firm
- Impersonation of Swiss brands
- You have a .eml or full headers to share
Headers and the .eml file
When you export a message, include full headers so analysts see originating IP and authentication results. IT can show staff how to use «Report message» in Microsoft 365 rather than forward a stripped copy. If someone already clicked, reporting still helps block the domain for colleagues who have not.
Legal and insurance context
Reporting phishing internally supports Art. 8 FADP organisational measures (fedlex); it does not by itself notify the FDPIC. If credentials or customer files leaked, privacy leads use a separate breach process. Cyber insurers may ask whether you have a reporting culture; keep ticket IDs, not only verbal «we told IT». This is orientation, not legal advice.
Phishing simulations elsewhere
If your company later runs simulations, staff must know beforehand and results must not target individuals for discipline (FDPIC on workplace monitoring). That topic has its own article; here the focus is real malicious mail.
Common mistakes
Paying an invoice because the phishing mail arrived the same day as a real one mixes two threads; finance must separate them on the phone. Punishing the reporter hides the next wave. Publishing click league tables from simulations is a different mistake; see measuring security awareness for what to track instead.
Security awareness training covers internal reporting, smishing, and when to involve finance, in a live one- to two-hour session for your team.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
Clicked a phishing link at work: what now
Clicked a phishing link at work: disconnect, tell IT, and let them reset the mailbox. First hour for a Swiss team, not a private inbox.
Are phishing simulations allowed in Switzerland?
Phishing simulations are allowed in Switzerland if staff are told first and clicks are not used to judge a person. Swiss labour law, not German rules.
Security awareness training topics for Swiss SMEs
Which security awareness training topics belong in a session for Swiss SMEs: phishing, payments, passwords, reporting and role-specific risks.