Voice Phishing: When the Attacker Calls Your Staff
The caller knows the receptionist's name, the finance director's diary pattern, and the exact wording the IT team uses when they need a password reset. Nothing in the conversation feels like an attack, because nothing in it is unusual, except for the request at the end.
Why Voice Beats Email for Social Engineering
Email gives the target time. A phone call does not. The conventions of conversation push people toward cooperation: interrupting to verify feels rude, and the caller controls the pace, the framing, and the exit. Add hold music, a transfer, and a second voice claiming to be a manager, and the target is managing a social situation rather than evaluating a security event.
Voice attacks are also cheap to research. Extensions, names, and organisational structure are often published, and a call to reception confirms the rest. The attacker does not need technical access to sound internal; they need thirty seconds of a switchboard.
| Attack pattern | What the target hears | Where it leads |
|---|---|---|
| IT password reset | A courteous engineer who has noticed unusual activity | Credentials, then mailbox access |
| Finance director authorisation | An urgent payment that needs approval before close of business | Bank transfer to a new beneficiary |
| Supplier bank detail change | A known supplier's accounts team confirming new details | Payment redirected permanently |
| Carrier or vendor audit | A technician verifying the phone system configuration | Remote access to the PBX |
| New starter setup | A colleague who cannot log in and needs a quick favour | Initial foothold, then escalation |
Verification That People Will Actually Do
Telling staff to be careful is not a control. Verification has to be a step with a defined method and a low social cost. The pattern that works is a callback to a number held in the directory, never a number provided by the caller, combined with a phrase that makes the pause normal: the agent states that they always call back on a known number before making changes. Framing it as policy rather than suspicion removes the awkwardness that causes people to skip it.
Target the Requests, Not the People
Any request that changes money, credentials, access, or call routing deserves verification regardless of who appears to be asking. Enumerating those request types is more effective than training people to detect deception, because the list is finite and the deception is not.
- Call back on a number from the directory, never one supplied during the call
- Verify any request involving money, credentials, access, or routing
- Make verification a stated policy so refusing feels routine
- Give staff a single, well-publicised route to report a suspicious call
- Log reported attempts and circulate the pattern to other teams
- Review who can authorise changes to call routing and trunks
The System Side of the Problem
Some voice attacks are only possible because the phone system will do what a caller asks. International routing that can be enabled by a helpdesk password is a fraud vector. Voicemail that can be reset by anyone who knows an extension is a mailbox takeover. Administrative interfaces reachable from the internet are the most serious case of all. The technical controls are unglamorous: restrict international destinations, require strong authentication for administrative changes, keep the management interface off the public internet, and alert on changes to routing rather than only on call volume.
Redstone Approach
Redstone IP-PBX deployments support destination class-of-service restrictions, per-role administrative rights, and alerting on configuration change, so a routing change is an event someone can see rather than a discovery made on the next invoice. Where remote administration is required, deployments place the management interface behind a controlled access path rather than exposing it directly.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.

Current Location :

