How AI Is Changing Hacking: From Deepfake Calls to Autonomous Intrusions

AI · 2026-11-09 · By H.A

How AI Is Changing Hacking: From Deepfake Calls to Autonomous Intrusions

AI now speeds up every stage of an attack, from reconnaissance and phishing to bug hunting and agent-run intrusions, and defenders need to move just as fast.

Hacking Has a New Co-Pilot

For decades, hacking was limited by people: how many skilled operators a group had, how many hours they could spend on reconnaissance, and how quickly they could turn a bug into a working exploit. AI is removing those limits one by one. The techniques are mostly familiar. What has changed is speed, scale and who can now pull them off. Here is how AI is reshaping each stage of an attack, and what it means for the people defending against it.

Reconnaissance at Machine Speed

Mapping a target used to mean days of manual work: scanning hosts, reading documentation, trawling LinkedIn for staff names and email formats. AI agents can now do much of that in a loop. They run scanners, read the output, decide what to probe next and summarise the attack surface in plain language. Open-source intelligence that once took an analyst a week can be compiled in an afternoon, complete with suggested phishing targets and likely weak points.

Social Engineering Without the Tells

Phishing used to give itself away through clumsy grammar and generic wording. Language models now write fluent, localised, personalised messages at scale, in any tone and any language. Voice cloning and video deepfakes take this further. In early 2024, an employee at the Hong Kong office of engineering firm Arup joined a video call where the CFO and several colleagues were all AI-generated fakes. The employee made 15 transfers totalling about HK$200 million (roughly US$25 million) before the fraud was discovered. The lesson is that seeing and hearing someone on a call is no longer proof of who they are.

Finding Vulnerabilities Faster Than Ever

AI is becoming genuinely good at bug hunting, and this cuts both ways. In mid-2025, Google said its Big Sleep AI agent found a serious SQLite memory corruption flaw (CVE-2025-6965) that it believed only threat actors knew about, and the bug was patched before it could be exploited. Around the same time, XBOW, an autonomous AI penetration tester, reached the top of HackerOne's US leaderboard, submitting over a thousand vulnerability reports in a few months. Every submission was reviewed by a human before going out.

In August 2025, DARPA's AI Cyber Challenge ended with teams' autonomous systems finding and fixing most of the vulnerabilities planted in real open-source code. The same capabilities that help defenders patch faster also help attackers find the next zero-day faster. The window between a patch and a working exploit keeps shrinking.

From Assistant to Autonomous Operator

The biggest shift is AI moving from advising attackers to acting for them. In November 2025, Anthropic reported disrupting what it called the first reported AI-orchestrated cyber-espionage campaign. A group it assessed as Chinese state-sponsored, tracked as GTG-1002, used a custom framework that ran Claude Code instances as autonomous penetration-testing agents against about 30 organisations, including technology firms, financial institutions, chemical manufacturers and government agencies. Anthropic estimated that AI performed 80 to 90 percent of the tactical work, with humans stepping in only at key decision points. Some researchers have questioned how impressive the results really were. Even so, the shape of the attack is clear: one operator directing many AI workers in parallel.

AI is also showing up inside malware itself. Some strains now query a language model at runtime to generate commands or rewrite their own code, so they behave differently each time they run.

Lowering the Bar for Everyone

Perhaps the most important change is who can attack. Uncensored "dark LLMs" sold on Telegram and underground forums, plus jailbroken mainstream models, let people with little technical skill produce phishing kits, scripts and ransomware templates. Skilled groups get faster. Unskilled ones get capable. Both trends increase the overall volume of attacks.

The Same Tools Work for Defence

None of this is one-sided. AI agents are triaging alerts in security operations centres, writing detection rules, reverse-engineering malware samples and finding bugs in code before it ships. Big Sleep and the AI Cyber Challenge systems are defensive tools first. Organisations that adopt AI for defence at the same pace attackers adopt it for offence can keep the balance. Those that don't will fall behind.

What Defenders Should Do Now

Assume attacks are faster. Shrink patch windows for internet-facing systems, and prioritise vulnerabilities known to be exploited over raw CVSS scores.

Verify identity through a second channel. Any request for payment, credential resets or sensitive data should be confirmed by calling a known number, never a contact supplied in the request itself, and that applies even after a convincing video call.

Use phishing-resistant MFA such as passkeys or hardware keys. They hold up no matter how good the lure is.

Detect behaviour, not signatures. AI-generated tooling changes constantly, so watch for what attackers do: unusual logins, privilege escalation, lateral movement and data staging.

Treat AI agents as identities. Give your own AI tools least-privilege access, log their actions, and watch for unexpected outbound connections to AI services from servers.

Put AI to work on your side: code scanning, alert triage and attack simulations against your own environment.

The Bottom Line

AI hasn't invented a new kind of hacking. It has industrialised the old kinds. Reconnaissance, phishing, bug hunting and intrusion now run at machine speed, often with a single human directing the work. The fundamentals of defence still apply. They just need to run faster, and increasingly with AI on the defenders' side too.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Passive OSINT lookups for the recon phase of an engagement, plus offline hash identification and a payload cheatsheet.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.