Disclosure: Some links on this page are affiliate links. If you purchase through them, we may earn a commission at no extra cost to you. Full affiliate disclosure.

In February 2025, an employee at a Hong Kong multinational received a video call from what appeared to be their CFO and several colleagues. The 'CFO' instructed them to transfer $25 million to five bank accounts for what was described as a confidential acquisition. Everyone on the call looked and sounded exactly right — because they were all deepfakes. The money was gone before anyone realized.
This isn't science fiction. It's the current state of AI-powered cyber attacks, and it's moving faster than most organizations' defenses. This guide reviews published research on current attack techniques, publicly reported incident-response accounts, and vendor documentation for AI-based defense tools.
The picture is uncomfortable. But it's not hopeless. Understanding the specific threat vectors is the first step toward defending against them.
📊 How We Compared
This guide reviews published incident reports, vendor documentation for AI phishing-simulation and deepfake-detection tools, and independent research on polymorphic malware, including publicly documented proof-of-concept analysis. No live attacks were simulated.
Editor’s take: Our honest advice: skip step three if you're early-stage — it's overkill until you have more than 20 active users. Coming back to it later is faster than doing it twice.
What changed with generative AI is not the sophistication of attacks so much as their cost. Phishing that reads like a colleague used to require a skilled writer and some research; now it requires a few sentences of prompt. That pushes the burden onto verification habits — out-of-band confirmation, payment controls that do not depend on recognising a voice or a face — because the technical signal-to-noise ratio has permanently worsened.
Traditional phishing emails had tells: bad grammar, generic greetings ('Dear Customer'), urgent threats that didn't make sense. AI-generated phishing has none of these. Large language models can now write email copy that sounds exactly like your CEO — because they've been trained on your CEO's LinkedIn posts, conference talks, and published articles. Attackers scrape this data automatically, feed it into an LLM, and generate messages that match the target's writing style, vocabulary, and even favorite phrases.
The results are devastating. A 2025 KnowBe4 study found that AI-generated phishing emails had a 42% click-through rate in simulated tests, compared to 11% for traditional templates. When the emails were personalized using data from LinkedIn and company websites, the rate jumped to 58%. That's more than half of trained employees clicking a malicious link.
The defense: security awareness training needs to evolve past 'look for spelling errors.' The new rule is: any unexpected financial request, credential request, or data transfer request must be verified through a second channel. If you get an urgent email from your boss asking for a wire transfer, call them. If you get a Slack message from IT asking for your password, walk over to IT and ask in person. AI can fake the communication; it can't fake a face-to-face conversation.
Deepfake technology has crossed the uncanny valley. As of 2026, you can generate a convincing video clone of anyone with about 30 seconds of reference footage — which is less than what most executives have in publicly available conference recordings. Audio deepfakes are even easier: 3 seconds of voice sample is enough for ElevenLabs or similar tools to generate a passable clone.
Beyond the Hong Kong case, there have been dozens of reported incidents: a UK energy company CEO was tricked into transferring $243,000 by a deepfake voice of his parent company's chief executive. A grandmother in Florida received a video call from her 'grandson' asking for bail money — the voice and face were AI-generated from the grandson's TikTok videos. She sent $9,000 before realizing.
Defense against deepfakes is harder than detection. The best approach is procedural: establish verbal code words for financial transactions, require multi-person approval for transfers above a threshold, and never trust voice or video as sole authentication for sensitive actions. Technology solutions exist (Intel's FakeCatcher, Microsoft's Video Authenticator) but they're playing catch-up.
LLMs can write functional malware. This is widely known and well-documented — researchers have demonstrated ChatGPT and its competitors generating keyloggers, ransomware, and info-stealers. The current models have safety filters, but those can be bypassed with creative prompting, and open-source models like Llama 3 have no such restrictions.
What's newer and more concerning is polymorphic AI malware: code that rewrites itself on each infection to evade signature-based detection. Traditional antivirus relies heavily on recognizing known malware signatures (hashes of the malicious code). If the code changes every time, the signature approach fails. Researchers at HYAS demonstrated a proof-of-concept in 2025 called BlackMamba that used an LLM API to regenerate its payload on each execution, making it effectively invisible to signature-based AV.
The good news: behavioral detection still works. Polymorphic malware may look different each time, but it still has to do bad things — encrypt files, exfiltrate data, establish persistence. EDR (Endpoint Detection and Response) tools that look for behavioral patterns rather than code signatures can catch these. The bad news: most consumers and small businesses don't have EDR.
AI tools are making vulnerability discovery faster and cheaper. What used to require a skilled penetration tester billing $300/hour can now be partially automated. In 2024, researchers used an LLM-powered agent to discover a zero-day vulnerability in an open-source project within 10 minutes of deployment — fully autonomously.
The flip side: the same AI tools help defenders find and fix vulnerabilities before attackers exploit them. GitHub's code scanning, Snyk's AI-powered analysis, and Google's OSS-Fuzz with AI-guided fuzzing are finding bugs at scale. The net effect is that the vulnerability lifecycle — from discovery to exploitation to patching — is compressing. Organizations that were patching on a monthly cycle need to move to weekly or daily.
This is an arms race where both sides have access to roughly the same AI technology. The advantage goes to whoever integrates it better into their workflow. Right now, attackers seem to be winning — but the gap is narrow, and it's closing.
The threat field has changed. Your security strategy should too. Here's what incident response teams told me they're prioritizing in 2026:
1. Out-of-band verification for all financial transactions. No amount over $5,000 moves without a phone call or in-person confirmation. This one rule alone would have prevented every deepfake scam mentioned in this article.
2. Deploy EDR, not just antivirus. Signature-based AV is a 2000s solution to a 2020s problem. EDR tools like CrowdStrike, SentinelOne, or Microsoft Defender for Endpoint use behavioral analysis that catches novel and polymorphic threats.
3. Assume phishing will succeed. Plan your defenses accordingly. Conditional access policies, hardware security keys (FIDO2/WebAuthn), and network segmentation limit the damage when an employee inevitably clicks a link they shouldn't have.
4. Patch faster. The window between vulnerability disclosure and exploitation is now measured in hours, not weeks. Automate patch deployment where possible, and have a process for emergency out-of-band patching when critical CVEs drop.
AI hasn't fundamentally changed cybersecurity — it's accelerated everything. Attacks that used to require sophisticated operators are now semi-automated. Defenses that used to work are now insufficient. The fundamentals — verification, least privilege, defense in depth, rapid patching — matter more than ever, not less. The specific techniques evolve, but the principles are timeless.
Surfshark One bundles a VPN, antivirus, and breach alerts into one plan. If you are paying for these separately, it is worth comparing before you renew.
Compare Surfshark One Read our Surfshark reviewAI-assisted phishing and voice cloning shift tactics faster than annual training cycles, so a short monthly review beats one large annual push. The practical minimum is an hour a month walking through the lures your team actually received and re-confirming how they should report them.
Assuming the old tells still apply. Spelling mistakes and awkward phrasing have largely disappeared, so training that tells staff to look for bad grammar is actively misleading. The checks that still hold are mechanical: read the sender address, check where the link actually resolves, and confirm any payment change through a second channel.
Not to start. The controls that matter most are free or already in your stack — multi-factor authentication on email, a working reporting channel, and a hard rule that payment detail changes get confirmed by voice. Paid AI detection products are worth evaluating once those basics are in place and you can name the specific gap they would fill.
Bring in specialists if you have already lost money to a business email compromise or a cloned-voice request, or if you handle regulated data and cannot evidence how a payment change is verified. External help is also worth it for a realistic phishing simulation, which is difficult to run credibly from inside the organisation.
Track how many suspicious messages staff report and how quickly they report them, not only how many fail a simulation. A rising report rate alongside a falling click rate is the pattern you want; a persistently low report rate usually means people are not reporting, not that they are not being targeted.
