Introduction
Voice-based fraud now accounts for billions in annual losses, and the FBI has flagged AI-assisted voice fraud as one of the fastest-growing financial crime vectors in the country. Your email security didn’t catch it. Your DMARC configuration didn’t fire. Neither did your anti-phishing stack. That’s not a gap in your tools. It’s a gap in your threat model.
How does vishing work? Attackers use spoofed caller ID, AI-cloned voices, and pre-built fake branded portals to steal credentials in real time. The phone call manufactures urgency. The fake portal is where the fraud actually happens.
This guide covers the full attack anatomy, the industries most at risk, why MFA isn’t enough, and what a credible defense actually looks like in 2026.
Introduction: The Call Is Not the Crime
A customer gets a call from their bank’s fraud department. The caller ID matches the bank’s number. The agent knows their name, their last transaction, their account type. There’s suspicious activity, they’re told. Verify your identity at this secure link.
Within minutes, their account is empty.
The bank’s email security didn’t fire. DMARC didn’t fire. The anti-phishing stack sat silent. Because the attack never touched email.
This is how vishing works in 2026, and the industry is still misreading it.
According to recent threat intelligence, voice phishing attacks surged 442% between the first and second halves of 2024. That number isn’t a story about phone calls getting more sophisticated. It’s a story about attackers building convincing fake brand portals, then using phone calls to drive victims straight to them.
Think of a vishing operation as an octopus. The phone call is one arm. The tentacles that actually grip the victim are the spoofed websites, cloned login pages, and fake brand portals waiting at the other end of that URL. Security teams fighting only the call are wrestling one arm while the rest of the creature operates freely.
This guide covers the full anatomy of a vishing attack from an enterprise brand perspective: why traditional security tools miss the most dangerous step, and what security and fraud leaders need to do differently.
What Is a Vishing Attack? (Enterprise Definition)
Most security teams still think of vishing as a consumer problem. A scam call. Someone’s elderly relative getting tricked into buying gift cards. That framing is dangerously wrong.
A vishing attack (voice phishing) is a multi-stage social engineering operation in which threat actors use phone calls, VoIP, or AI-generated audio to impersonate a trusted brand or authority figure, manipulate a target into a specific action, and harvest credentials, authorize fraudulent transactions, or trigger account takeover. The call is just the opening move.
Here’s what makes it a brand problem, not just a fraud problem: when attackers impersonate your bank, your fintech platform, or your telco and direct victims to a spoofed version of your portal, your brand is the weapon. Your customers absorb the loss. Your organization absorbs the regulatory and reputational fallout.
The scale has accelerated sharply. Cisco Talos reported that vishing accounted for over 60% of all phishing-related incident response engagements in Q1 2025. These aren’t edge cases. Vishing is now the dominant initial access vector in enterprise attacks.
AI voice cloning has removed the last remaining friction. Microsoft’s VALL-E research demonstrated that voice cloning requires as little as three seconds of audio, enough to replicate a CFO, a bank agent, or a government official with convincing accuracy. In May 2025, the FBI issued PSA250515 warning that malicious actors were actively using AI-generated voice messages to impersonate senior U.S. officials. The Deloitte Center for Financial Services projects that gen AI-enabled fraud losses will reach $40 billion in the United States by 2027, up from $12.3 billion in 2023.
Vishing doesn’t just bypass your users’ judgment. It bypasses your entire security stack.
| Phishing | Vishing | Smishing | |
| Channel | Voice call / VoIP | SMS / messaging app | |
| Common lure | Malicious link or attachment | Urgent call-to-action, brand impersonation | Fake alert with link |
| Tools that catch it | Email gateway, DMARC/DKIM/SPF, URL scanner | None – voice is unmonitored | SMS filters, mobile threat defense |
| Critical blind spot | Sophisticated spoofed domains | Fake portal redirect after the call | Link-based credential harvest |
The critical column is the third row for vishing: none. Email gateways don’t see phone calls. DMARC/DKIM/SPF records are irrelevant when the attack travels over voice. URL scanners can’t intercept a URL that a victim types manually after being told to visit it by a convincing caller.
That unmonitored gap, between the call and the fake portal, is exactly where the fraud completes.
The AI Voice Cloning Acceleration
Vishing used to require a skilled social engineer, a phone, and hours of manual effort per target. That constraint is gone.
Microsoft’s VALL-E model demonstrated that three seconds of audio is enough to produce a convincing voice replica, complete with emotional tone and acoustic environment. That’s a LinkedIn earnings call clip. A conference panel recording. A customer service interaction. Attackers don’t need a studio session; they need a search bar.
The result: deepfake-enabled vishing attacks surged 1,633% in Q1 2025 compared to Q4 2024, according to Right-Hand AI. That’s not a trend line. That’s a cliff edge.
Here’s what’s driving the scale:
- AI voice agents built on platforms like Bland AI run dynamic, LLM-powered conversations that adapt in real time to what a victim says. No script breaks, no awkward pauses, thousands of calls running simultaneously.
- LLM-powered reconnaissance scrapes LinkedIn profiles, company directories, and breached databases to build hyper-personalized target dossiers before a single call is placed.
- Robocall infrastructure means one attacker can run campaigns that previously required an entire call center.
This isn’t theoretical. In 2025, the ShinyHunters and Scattered Spider alliance used AI-assisted vishing as the primary initial access vector to breach 100+ enterprise organizations, targeting SSO credentials across retail, airline, and telecom sectors, according to EclecticIQ. Stolen datasets sold for over $1M per company.
This is enterprise-grade attack infrastructure. The call is just the ignition.
Who Gets Targeted – and Who Gets Blamed
When a vishing attack succeeds, two victims walk away damaged. One loses money. The other loses something harder to rebuild: trust.
The industries attackers choose aren’t random. Financial services, fintech, e-commerce, and telco brands are disproportionately targeted because they combine large customer bases, high-value credentials, and brand names customers interact with digitally every week. According to APWG’s Q1 2026 Phishing Activity Trends Report, financial services accounts for 23.5% of all phishing attacks, the single most targeted sector. StationX’s 2026 Phishing Statistics put it more starkly: financial services face 300x more phishing-related attacks than the average industry.
Your brand recognition is the weapon.
When a customer loses money because a criminal impersonated your bank, your fintech platform, or your telco, they don’t blame the criminal. They blame you. The call sounded like you. The website looked like you. As far as the customer is concerned, you failed them.
The downstream consequences are measurable. Customer trust scores drop. Fraud-related support tickets spike. Churn accelerates. According to PYMNTS Intelligence research, scam victims who don’t recover their funds often leave their financial institution altogether, making fraud-driven churn a direct revenue problem, not just a reputational one.
The scale is no longer abstract. The FTC reported $3.5 billion in imposter scam losses in 2025, with business impersonators, primarily bank impersonators, accounting for $1 billion of that total. That’s up from $866 million in 2024.
Regulatory exposure compounds the reputational hit. Enterprises in financial services operate under CFPB oversight, PCI-DSS requirements, and a growing body of state-level consumer protection frameworks. Even when your organization is technically the victim of brand impersonation, regulators and customers hold you accountable. The question regulators ask isn’t whether you were impersonated. It’s whether you had controls in place to detect it and protect customers when it happened.
This is not an employee awareness problem. It’s a brand infrastructure risk that sits squarely on the desk of security and fraud leadership, and it demands an infrastructure-level response.
The Full Anatomy of a Vishing Attack – Step by Step
Most security teams picture vishing as a phone call. That’s like describing a bank robbery as a conversation with the teller. The call is one moment in a carefully staged operation, and it’s not where the damage happens.
Here’s how a vishing attack actually unfolds.
- Step 1: Reconnaissance
Before any call is made, attackers build a detailed target profile. LinkedIn, company directories, social media, breached credential databases, and dark web forums all feed the picture. Attackers map account types, recent transaction patterns, and support ticket behavior, enough to make the eventual call feel eerily specific. AI tools automate this profiling at scale, letting a single threat actor work thousands of potential victims simultaneously.
- Step 2: Infrastructure setup
This is the most critical step, and the most overlooked. Attackers register lookalike domains (think secure-bankname-verify.com), clone the brand’s website with pixel-perfect accuracy, install SSL certificates to display the trusted padlock icon, and configure credential-harvesting backends. According to Zscaler ThreatLabz research via Breachsense, free SSL certificates from Let’s Encrypt appear on 48.4% of all phishing domains. VoIP infrastructure is provisioned for caller ID spoofing. The fake portal is live and waiting before the victim ever picks up the phone.
- Step 3: The call
Using a spoofed caller ID that displays the brand’s legitimate number, the attacker contacts the target. They reference specific personal details from reconnaissance to establish credibility fast. Urgency is manufactured: “We’ve detected suspicious activity on your account” or “Your account will be locked in 15 minutes.” AI voice cloning may impersonate a known executive or trusted contact, making the call nearly impossible to question.
- Step 4: The redirect
The attacker directs the victim to the pre-built fake portal: “Please visit [spoofed URL] to verify your identity and secure your account.” The URL arrives verbally, or simultaneously via SMS or email. The victim, already primed by urgency and apparent legitimacy, navigates to what looks exactly like the brand’s real site. This is the moment the brand’s own identity is weaponized against its customer.
- Step 5: Credential harvest
On the fake portal, the victim enters their username, password, MFA code, account number, or payment details. Many modern vishing operations use adversary-in-the-middle (AiTM) techniques. A reverse proxy relays credentials to the real site in real time, capturing the post-authentication session cookie. MFA doesn’t stop this. Obsidian Security found that 84% of accounts compromised via AiTM techniques already had MFA enabled. The victim sees a convincing “verification complete” message and believes the issue is resolved.
- Step 6: Exfiltration and account takeover
With harvested credentials or a stolen session token, the attacker accesses the real account, transfers funds, changes authentication details, or sells the credentials on dark web markets. The brand’s fraud team typically discovers the breach hours or days later, long after the damage is done. The FBI’s 2025 IC3 Report recorded $20.9 billion in cybercrime losses, with cyber-enabled fraud accounting for nearly 85% of all reported losses.
- Where the security gap actually lives
Most enterprise security tools are built to intercept Steps 1 and 3, reconnaissance signals and call-based indicators. Almost none are positioned to detect or disrupt Steps 2, 4, and 5: the fake portal layer where the actual fraud executes. That’s not a minor gap. It’s the entire attack payload, running undetected.
Real-World Vishing Attack Examples
These aren’t hypothetical scenarios. Three attacks show exactly how vishing evolved from nuisance calls into full-scale brand infrastructure fraud.
- Example 1: The $25 million deepfake CFO call (Hong Kong, 2024)
A finance employee at multinational engineering firm Arup joined what appeared to be a routine video call. Every other participant, including the CFO, was a deepfake AI construct. The employee authorized $25 million in wire transfers before anyone realized the call was fabricated.
This wasn’t a phone scam. It was a full multimedia brand impersonation operation, where the attacker’s “infrastructure” was a convincing replica of the company’s own leadership.
- What this means for your brand: If attackers can clone your executives on video, your internal brand trust is the attack surface.
- —
- Example 2: Scattered Spider / ShinyHunters enterprise vishing campaign (2025)
According to EclecticIQ’s threat intelligence analysis, ShinyHunters recruited Scattered Spider affiliates to run AI-powered vishing calls at scale against enterprise IT help desks. Attackers impersonated employees, bypassed MFA, and accessed SSO platforms, including Salesforce CRM data, across retail, airline, and telecom organizations. Stolen datasets sold for over $1 million per company.
The vishing call was just the door. The real damage happened inside enterprise cloud systems.
- What this means for your brand: Your help desk is a vishing target. Internal brand trust is as exploitable as customer-facing portals.
- —
- Example 3: FakeCall malware, the fake portal made invisible (2024)
Zimperium’s zLabs team documented FakeCall, an Android malware that intercepts outgoing calls to banks and reroutes them to attacker-controlled infrastructure, while displaying the real bank’s UI on the victim’s screen. The victim sees your brand. They hear what sounds like your agent. Their credentials go straight to the attacker.
This is the fake portal concept at its most dangerous: invisible, real-time, and wearing your brand’s face.
- What this means for your brand: When your customers think they’re on your platform but aren’t, the fraud happens in your name, and the reputational damage lands on you.
Why Traditional Security Tools Miss the Most Dangerous Step
Your security stack is defending the wrong perimeter.
Most enterprise security tools were built to protect the inbox and the internal network. Vishing attacks neither. The call happens outside your perimeter. The fake portal lives on infrastructure you don’t own. The credential theft occurs in a browser session your tools never see. Here’s exactly where each layer of your stack goes blind.
- Email security gateways and DMARC/DKIM/SPF
DMARC is a legitimate and necessary control. It authenticates your email domain and blocks spoofed messages from reaching inboxes. But a vishing attack doesn’t use email. The attacker registers a lookalike domain, clones your web portal, and delivers the URL verbally over a phone call. DMARC has no jurisdiction over any of that. Perfect DMARC implementation does nothing to stop an attacker from standing up a pixel-perfect replica of your login page and directing a victim there by voice. It protects your email domain. It doesn’t protect your brand’s visual identity on the open web.
- Anti-phishing and URL filtering tools
These tools scan URLs in emails and web traffic, comparing them against threat intelligence feeds and domain reputation databases. The problem is timing. A freshly registered lookalike domain has no reputation history. No threat feed has seen it. No blocklist has flagged it. According to BlackBerry’s 2025 threat intelligence research, cited by StationX, the average phishing site lives just 12 hours before takedown. By the time a domain surfaces on a threat feed, the attack is already over.
Here’s the kicker: these tools only scan URLs that arrive via email or web traffic. When a victim types a URL they heard on a phone call directly into their browser, there’s no link to scan. The tool sees nothing.
- SIEM and SOC monitoring
SIEM platforms aggregate logs from internal systems. They’re powerful for correlating internal events, but they have zero visibility into external infrastructure an attacker controls. A SIEM can’t see a victim navigating to a spoofed portal. It can’t detect credential harvesting happening on a server your team has never heard of. The first signal your SIEM receives is a suspicious login attempt, after the credentials are already stolen. You’re reading the autopsy report, not preventing the death.
- Behavioral analytics and anti-fraud tools
Behavioral biometrics platforms like BioCatch and fraud scoring tools like ThreatMetrix are valuable inside the authenticated session. They monitor how users interact with your real platform after login, flagging anomalies that suggest ATO or social engineering. But by definition, they activate after the victim has already been deceived. They see the downstream effect of the vishing attack, not the attack itself.
- The exposure control gap
Map these four tool categories against the six-step vishing attack chain and a pattern emerges. Steps 1 and 3, reconnaissance and the call itself, are outside any tool’s scope. Steps 2, 4, and 5, infrastructure setup, the redirect to the fake portal, and credential harvesting, fall into a gap no traditional security tool monitors.
This is the exposure control gap. The fake portal is where your brand is actively weaponized, where credentials are stolen, and where your entire security stack has no line of sight. Fighting vishing by hardening your inbox is like installing a deadbolt on the front door while the attacker walks in through a window you didn’t know existed.
The Exposure Control Gap: Why the Fake Portal Is the Real Attack Payload
Here’s the math that should keep fraud leaders up at night: the industry average for dismantling a malicious domain is 58 days. The average vishing campaign’s active credential-harvesting window is measured in hours. That gap is where your customers get robbed and your brand takes the hit.
This is the Exposure Control Gap: the critical window between the moment a victim lands on a fake branded portal and the moment your security team can respond. During that window, fraud is live. Credentials are being harvested. Accounts are being taken over. Your infrastructure has no idea.
The gap exists for five structural reasons:
- Attacker-controlled infrastructure. Fake sites live entirely outside your network perimeter. Your monitoring tools can’t see what they can’t reach.
- No link to scan. Vishing victims navigate to fake sites via verbal instructions. There’s no URL in an email, no click to intercept, no link-scanning tool in the chain.
- Valid SSL certificates. The padlock is green. Browser warnings stay silent. The victim sees nothing alarming.
- Fresh lookalike domains. Each campaign uses a newly registered domain with zero reputation history, so reputation-based detection returns a clean score.
- Short attack windows. Research published in 2025 found the median phishing site lifespan is just 5.46 hours. Manual takedown processes can’t move that fast.
The result: by the time your team gets an alert, the attacker has moved on. The fake site is dark. The credentials are sold. The accounts are compromised.
Traditional detection operates on a timeline attackers deliberately exploit. Closing the Exposure Control Gap requires a fundamentally different approach: one that operates at the fake site layer, in real time, the moment a victim arrives.
The Smarter Defense — Neutralizing the Scam Infrastructure
You can’t intercept every vishing call. Caller ID spoofing, AI voice cloning, and cheap VoIP infrastructure mean attackers can place thousands of calls at near-zero cost. Trying to stop vishing at the phone layer is like trying to catch every arm of an octopus: the moment you grab one, three more are already moving.
Here’s the reframe that changes the strategy: the call is just one arm. The fake branded portal is the arm that grips the victim and extracts value. That’s where credentials are stolen. That’s where the fraud completes. And that’s the arm you can make fail.
- The octopus doesn’t need every arm to work. It only needs one to grip.
When a vishing victim lands on a spoofed portal, convinced by a caller posing as your bank, your telco, or your payment platform, they’re already past your perimeter controls. Your DMARC records didn’t stop the call. Your email filters weren’t in the picture. Your fraud scoring system hasn’t fired yet because the victim hasn’t attempted to log in.
This is the gap. And it’s exactly where Memcyco operates.
- Detecting the infrastructure before victims arrive
Memcyco continuously monitors for fake branded portals, lookalike domains, and cloned websites from the moment they’re deployed, not after victims have already been directed to them. That early detection window matters. It’s what allows takedown requests to be initiated before exposure accumulates, rather than days after a campaign has already run.
Real-world attacks confirm why timing is critical. Dark Reading reported in February 2026 that ShinyHunters threat clusters used vishing calls to direct victims to company-branded credential-harvesting sites mimicking legitimate SSO portals, capturing both login credentials and MFA codes before any downstream fraud system had visibility into the attack.
- Intervening while the attack is live
When a victim navigates to a fake site, Memcyco identifies that individual user in real time, not in a post-incident report. Its Proof of Source Authenticity (PoSA) technology infiltrates the live attack, delivering an immediate, unmistakable warning to the victim that the site is not legitimate.
On top of that, Memcyco can replace genuine credential submissions with marked decoy data, a “poison pill” the attacker unknowingly receives instead of real credentials. This disrupts the attacker’s workflow without alerting them that the attack has been neutralized.
- Feeding the systems that act on risk
Memcyco doesn’t operate in isolation. Real-time attack data flows directly into anti-fraud tools, authentication systems, and SIEM platforms. Fraud teams can block compromised accounts, flag suspicious login sessions, and halt fraudulent transactions before they complete, all triggered by signals generated upstream of the login event.
This is the key differentiator: Memcyco operates in the scam phase, before the victim attempts to authenticate on the real site. It’s upstream of behavioral analytics, upstream of fraud scoring, and upstream of authentication controls.
The outcomes reflect it. Memcyco customers report a 50% reduction in ATO incidents, up to 90% reduction in investigation time, and 10x ROI within the first year.
You can’t stop every call. But you can make the grip fail, every time a victim reaches the fake portal.
What Security and Fraud Teams Should Do Now
Four recommendations. No consumer tips. No awareness training. Just the strategic moves that actually change your exposure profile.
- 1. Audit your brand’s external attack surface
Most enterprises don’t know how many fake sites are impersonating them right now. Commission an external brand impersonation audit that goes beyond domain monitoring to include active web scanning for visual clones, fake login pages, and spoofed mobile apps. You need a current inventory of your exposure before your customers stumble into it. If you don’t know what’s out there, you can’t protect against it.
- 2. Shift detection upstream: from post-login to pre-authentication
If your fraud stack only fires after a user attempts to log in, you’re detecting the downstream effect of a vishing attack, not the attack itself. By the time a stolen credential hits your authentication layer, the damage is done. Evaluate solutions that give you visibility into the external scam path: fake sites, compromised credentials in circulation, and at-risk users before they reach your login page. The goal is to know a user is at risk before they authenticate with harvested credentials.
- 3. Establish real-time victim identification capability
Traditional brand protection tools tell you a fake site exists. They don’t tell you which of your customers is on it right now. That distinction is the difference between detecting an attack and stopping one. Real-time victim identification gives fraud teams the ability to take immediate protective action: blocking compromised accounts, resetting credentials, and flagging suspicious transactions before they clear. Without this capability, you’re always reacting to yesterday’s breach.
- 4. Integrate scam infrastructure intelligence into your fraud stack
Vishing attack data, fake site detections, victim exposure events, and attacker infrastructure signatures should flow directly into your anti-fraud tools, authentication systems, and SIEM. This enriches fraud scoring with context that behavioral analytics alone can’t provide. A user attempting to log in whose credentials were harvested on a fake site 20 minutes ago carries a fundamentally different risk profile than a standard login attempt. APIs that bridge scam infrastructure intelligence into existing fraud stacks close the data silo that currently lets vishing attacks succeed undetected.
- The trajectory is clear
Vishing is not a trend that will reverse. Mandiant’s M-Trends 2026 found voice phishing is now the second most common initial infection vector, appearing in 11% of all investigated breaches. Deloitte projects generative AI fraud losses could reach $40 billion annually by 2027. AI voice cloning, industrialized phishing-as-a-service infrastructure, and the inherent difficulty of securing the voice channel mean attack volumes will keep climbing. The enterprises that contain their exposure will be those that stop trying to fight the call and start neutralizing the infrastructure that makes the call profitable.
Vishing vs. Phishing vs. Smishing: Key Differences for Enterprise Defenders
Security teams often treat vishing, phishing, and smishing as three separate problems. They’re not. They’re three delivery channels feeding the same attack infrastructure, and that distinction changes how you defend against them.
- The channel determines what your tools can see.
Email phishing leaves digital artifacts: headers, sender domains, payload URLs. Email gateways and DMARC/DKIM/SPF controls can analyze those artifacts and flag suspicious messages before they reach the inbox. Smishing is partially addressed by mobile threat defense tools, though SentinelOne’s 2026 data shows it still accounts for 35% of all phishing attacks. Vishing leaves almost nothing. A phone call generates no URL, no header, no scannable payload. There’s no defensive layer at the call level, which is exactly why attackers prefer it.
- The voice call is uniquely dangerous because it coaches the victim in real time.
A phishing email asks someone to click a link. A vishing call walks them through every step: what to type, what to ignore, what to say if they’re suspicious. That live, or AI-generated, voice dramatically increases conversion rates. It’s the difference between a self-serve checkout and a guided sales call.
- The fake portal is the common thread across all three.
Whether the lure arrives by email, SMS, or phone, the fraud almost always terminates at a spoofed branded portal. That’s where credentials are harvested, accounts are compromised, and the real damage is done. Vishing is the most dangerous path to that endpoint because the victim arrives already primed, already trusting, and already following instructions.
Modern campaigns don’t pick one channel. They combine all three: an email establishes context, an SMS delivers the URL, and a phone call applies the social engineering pressure to complete the action. IBM’s phishing research confirms that hybrid vishing attacks combine voice phishing with other methods specifically to evade spam filters and build victim trust.
| Attack Type | Channel | Primary Lure | Security Tool Coverage | Enterprise Blind Spot |
| Phishing | Malicious link or attachment | Email gateways, DMARC/DKIM/SPF | Lookalike domains, zero-day links | |
| Smishing | SMS/messaging | URL to fake site | Mobile threat defense (partial) | Personal devices, BYOD environments |
| Vishing | Voice call | Verbal instruction + redirect | None at call level | The fake portal the victim is coached to visit |
| Hybrid (TOAD) | All three | Multi-stage social engineering | Fragmented, no unified layer | The spoofed portal remains unmonitored |
The table makes the gap visible. Email and SMS have imperfect but real defensive tooling. Voice has none. Across all three vectors, the fake branded portal sits unmonitored: the one place where every attack converges, and the only viable intervention point.
Vishing Attack Glossary: Key Terms for Security and Fraud Leaders
- Vishing (voice phishing): A social engineering attack that uses phone calls to impersonate trusted organizations and extract credentials, financial data, or account access. Unlike email phishing, vishing exploits the perceived authority of a live human voice.
- Caller ID spoofing: The manipulation of VoIP infrastructure to display a falsified phone number on the recipient’s caller ID. As the FCC confirms, attackers use this to impersonate banks, government agencies, or enterprise IT helpdesks.
- Lookalike domain: A domain registered to visually mimic a legitimate brand’s URL, using typosquatting, homoglyph substitution, or subdomain tricks. These domains host the fake portals victims are directed to during a vishing call.
- Brand portal cloning: Pixel-perfect replication of a brand’s web interface, including logos, fonts, and UX flows, built to harvest credentials from victims who believe they’re on the real site.
- AiTM (adversary-in-the-middle): A technique where an attacker-controlled proxy sits between the victim and a legitimate service, relaying credentials and session tokens in real time. AiTM bypasses MFA because it captures live session cookies, not just passwords.
- AI voice cloning: Generative AI synthesis of a specific person’s voice from minimal audio samples, sometimes as few as three seconds. Attackers use cloned voices to impersonate executives or bank representatives with convincing accuracy.
- Pretexting: The fabrication of a believable scenario, such as a fraud alert, account suspension, or IT security check, to establish call credibility before directing victims to a fake portal.
- Credential harvesting: Systematic collection of usernames, passwords, and MFA codes via deceptive interfaces. In vishing attacks, this happens on the fake branded portal, not during the call itself.
- Account takeover (ATO): Unauthorized access to a user account using stolen credentials. ATO is the primary financial outcome of a successful vishing-to-portal attack chain.
- Exposure control gap: The window between the moment a victim lands on a fake site and the moment the brand’s security team becomes aware. This gap, often hours or days, is where fraud losses accumulate.
- PoSA (Proof of Source Authenticity): Memcyco’s technology for real-time authentication of legitimate brand portals. It signals to users whether the site they’ve reached is genuinely operated by the brand, at the exact moment of exposure.
- Scam infrastructure: The full technical ecosystem attackers build to run a vishing campaign: registered lookalike domains, cloned portals, VoIP spoofing tools, and hosting services. Dismantling this infrastructure, not blocking individual calls, is where enterprise defense must focus.
Conclusion: Stop Fighting the Call. Neutralize the Infrastructure.
The 2025 Global Threat Report documented a 442% surge in vishing attacks, revealing the industrialization of fake portal infrastructure. Threat actors aren’t just making more calls. They’re building more weapons.
The call is the trigger. The fake portal is where the fraud actually happens.
Enterprises that invest exclusively in call-level defenses, such as employee training, VoIP monitoring, and caller ID verification, are defending against the least dangerous part of the attack chain. Credentials aren’t stolen on the phone. Account takeovers don’t happen during the call. Brand damage doesn’t come from the voice. It comes from the spoofed site the victim lands on, convinced they’re in safe hands.
As AI voice cloning becomes indistinguishable from real voices and vishing campaigns become fully automated, the attack surface shifts further toward infrastructure. The only reliable intervention point is the fake portal layer: detecting spoofed sites before victims arrive, warning them in real time when they do, and feeding that intelligence into fraud systems that can act immediately.
Stop fighting the arm. Neutralize the infrastructure.
See how Memcyco activates at the exact moment a vishing victim reaches a fake portal.
Conclusion
Vishing isn’t a phone problem. It’s an infrastructure problem. Attackers build fake branded portals before they dial a single number, and your customers walk straight into them. Employee training won’t stop a pixel-perfect clone of your login page. Neither will DMARC. The only viable intervention point is the fake portal itself, detected and neutralized before credentials are stolen.
See Where Your Brand Is Exposed Right Now
Memcyco activates at the exact moment a vishing victim reaches your spoofed portal, delivering real-time warnings, attacker identification, and victim-level visibility before credentials are stolen. See how it works.
Frequently asked questions
How does a vishing attack work step by step?
A vishing attack follows six stages: (1) Reconnaissance — attackers gather target data from LinkedIn, company directories, and breached databases; (2) Infrastructure Setup — a fake branded portal is built and deployed before any call is made; (3) The Call — using spoofed caller ID and AI voice cloning, the attacker contacts the target and manufactures urgency; (4) The Redirect — the victim is directed to the pre-built fake portal to ‘verify their identity’; (5) Credential Harvest — the victim enters credentials on the fake site, which are captured in real time; (6) Exfiltration — stolen credentials are used for account takeover, fund transfer, or sold on dark web markets. The phone call is the trigger; the fake portal is where the actual fraud occurs.
What is the difference between vishing and phishing?
Phishing uses email to deliver malicious links or attachments, and is partially addressed by email security gateways and DMARC/DKIM/SPF authentication. Vishing uses voice calls — phone, VoIP, or AI-generated audio — to manipulate victims, bypassing all email-based security controls entirely. Both attacks increasingly converge on the same endpoint: a spoofed branded portal where credentials are harvested. The critical difference for enterprise defenders is that vishing leaves no email artifact for security tools to scan, making the fake portal the only viable intervention point.
Why can’t DMARC and email security tools stop vishing attacks?
DMARC, DKIM, and SPF are email authentication protocols — they verify that an email was sent from an authorized mail server for a given domain. They have no relevance to voice calls, VoIP infrastructure, or fake websites. A vishing attacker can register a lookalike domain, clone your brand’s website with pixel-perfect accuracy, and direct victims there verbally without ever sending a single email. Your DMARC configuration will never fire an alert because no email was involved. This is why vishing requires a fundamentally different defensive layer — one that monitors the external web for fake brand portals, not the email channel.
Which industries are most targeted by vishing attacks?
Financial services, fintech, e-commerce, and telecommunications brands are disproportionately targeted because they combine three factors attackers look for: large customer bases with high-value account credentials, strong brand recognition that makes impersonation convincing, and frequent legitimate customer contact that makes a ‘fraud alert’ call plausible. According to StationX 2026 Phishing Statistics, financial services face 300 times more phishing-related attacks than average industries. The FTC reported $3.5 billion in imposter scam losses in 2025, with financial institution impersonation representing a significant share.
How does AI voice cloning make vishing attacks more dangerous?
AI voice cloning technology — exemplified by Microsoft’s VALL-E research — can now produce a convincing voice replica from as little as 3 seconds of audio. This means attackers can clone the voice of a bank’s known customer service representative, a company executive, or even a personal contact using publicly available audio from earnings calls, YouTube videos, or social media. Fortune’s 2026 deepfake outlook noted that AI-generated voice has crossed the ‘indistinguishable threshold’ — the average listener cannot reliably tell a cloned voice from a real one. The FBI issued a formal warning (PSA250515, May 2025) about AI-generated voice impersonation targeting senior officials. Deepfake-enabled fraud losses are projected to reach $40 billion by 2027 (Deloitte).
What is the ‘exposure control gap’ in vishing defense?
The exposure control gap is the critical window between the moment a customer first interacts with a fake branded portal and the moment a security team becomes aware of the attack and can respond. During this window — which can last hours or days with traditional monitoring approaches — victims are actively being defrauded, credentials are being harvested in real time, and accounts are being taken over. The gap exists because fake sites are built on attacker-controlled infrastructure outside the enterprise perimeter, victims navigate to them via verbal instructions that bypass link-scanning tools, and freshly registered lookalike domains have no reputation history to trigger threat intelligence alerts.
Can multi-factor authentication (MFA) stop vishing attacks?
MFA significantly raises the bar for attackers but does not stop sophisticated vishing attacks. Adversary-in-the-Middle (AiTM) techniques used in fake portal attacks relay credentials and MFA codes in real time — the victim enters their OTP on the fake site, the attacker immediately uses it on the real site before it expires. The Scattered Spider / ShinyHunters campaign of 2025 demonstrated this at enterprise scale, bypassing MFA across hundreds of organizations. Memcyco detects AiTM attacks by identifying device mismatches, timing anomalies between user action and OTP usage, and behavioral deviations — operating upstream of the authentication layer where MFA controls apply.
