vishing

Vishing: phone fraud at work

AA
Aurum Avis Labs Author
5 min read

Vishing: phone fraud at work

Vishing is voice phishing: criminals call your office pretending to be bank fraud desks, tax offices, IT support, or executives. They create urgency so you reveal passwords, approve payments, or install remote access. Vishing at work often hits finance on Friday afternoon, reception on Monday morning, or assistants while leadership is travelling. The text is for staff and team leads in Swiss firms of about 20 to 250 people. The pattern is live social engineering on the phone, not a premium-rate number you dial from mail.

52 %

Share of fraud in voluntary NCSC reports in the second half of 2025, per the semi-annual report. Not our survey.

E-mail markers are covered in how to spot phishing e-mails. The classic “Microsoft support” call with remote control is narrower in fake Microsoft support call at work. Callback phishing starts in mail with a number you dial yourself: that is a different pattern, not vishing in the strict sense.

  • Hang up and call back on your published IT or bank number
  • Never read one-time codes or MFA prompts aloud to a caller
  • Escalate payment requests to a second person
  • Log caller ID without treating it as proof

How vishing differs from neighbouring scams

In vishing the attacker drives the call live, through a menu, or via a synthetic voice on voicemail. They want action on the line: read a code, start TeamViewer, “just confirm” a transfer. Callback phishing starts with mail that pushes you to dial an attacker number. Deepfake boss calls overlap with payment fraud; see CEO fraud in Switzerland for that lane.

Common pretences

  • ”Fraud department” needing account access
  • ”Lawyer” or “notary” with an urgent transfer
  • ”New IT vendor” right after a real outage

Your response

  • Pause and verify on a known number
  • Confirm internally on Teams or chat
  • No payment details from the call alone

Reception and assistants

Reception can say: “We do not handle banking by phone. I will pass you to finance on our main line.” Do not transfer cold “Microsoft” or “security” calls to executive mobiles. If someone claims an on-site visit, log time and caller ID in the visitor book and confirm internally.

When a caller wants personal data before you know who is on the line, use the same caution as in verifying identity on the phone. Health data from medical certificates does not belong in a spontaneous call; see medical certificates and the employer when HR mixes the two topics.

  • Finance and accounts payable

    ”Fraud desk” asks you to release a “blocked” payment. Stop: IBAN and amount never from the call alone; ring the number on the contract.

  • IT and admins

    Caller knows your name and “must reset a password urgently”. Stop: reset runs through your ticket system, not a cold call.

  • Voicemail with synthetic voice

    Voice note “from the CEO” ordering payment. Stop: four-eyes and callback to a stored number even when the voice sounds familiar.

Finance and payment approval

Vishing often targets the same weakness as mail fraud: payment under time pressure. Your written rule stays: new IBAN, new payee, or “urgent” exception only with a second person and callback to a known number. A caller who wants to “confirm the mail” does not replace that process. Executive assistants should know that “confidential transfer on the phone” is not a normal workflow.

MFA and vishing

Callers may already hold a password from an old breach. MFA helps, but vishing can push staff to approve prompts. Train explicitly: “No codes on the phone”, including “for IT”. Reading a code aloud often hands the session to the attacker. Prompts that appear during the call still mean: hang up before you approve.

Synthetic voice and recorded menus

AI-generated voices sound fluent today. Bank “voicemails” may point to a callback number that still reaches the attacker. Treat every unexpected voice note like a live call: no payment, no code, out-of-band verification via stored contacts. Deepfake CEO calls are a separate pattern; this page covers everyday office phone pretence.

Who needs these rules first

Reception, assistants, and finance take most cold calls. IT admins are called less often, but “password reset on the phone” hits them hard. Production and warehouse staff should know that “supplier calls about express payment” deserves the same pause. Private individuals and firms with their own SOC need different guides.

Report instead of hiding it

When in doubt, forward to your internal phishing mailbox or IT partner. Headers and caller ID beat a verbal summary. External reporting to the NCSC is a separate topic; internally, early warnings help colleagues block the same number. Managers who say “just bad luck” lower reporting rates: thank people for reporting even when nothing happened.

IT partners and telephony

Put your external IT partner on the reporting path. They need caller number, time, and whether anyone read codes aloud, not only “weird call”. If your provider can filter calls, repeated reports beat one-off anecdotes. That does not replace training, but it cuts repeats.

Is every unexpected call vishing?

No. Customers, authorities, and suppliers call too. Red flags are pressure, secrecy (“only you”), and actions your written rules normally forbid.

What if the display shows “Swisscom” or “Bank”?

Caller ID can be spoofed. Call back using the number on your contract, admin portal, or official website.

Who should not rely on this page alone?

IT teams configuring telephony filters need technical docs. Private individuals can use police and NCSC guidance. This page is about business numbers and payment processes in an SME.

Security awareness training practises vishing scenarios with your roles: reception, finance, and IT in one session, remote or on site in Switzerland.

vishing phone awareness switzerland
AA

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.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.