By CalMax Systems Security Research · Published February 27, 2026 · Updated November 16, 2026
A VPN brute force attack is an automated attempt to gain unauthorized access to a VPN portal by submitting large numbers of username and password guesses. The three main variants are credential stuffing (using leaked credentials from data breaches), password spraying (trying common passwords against many usernames), and classic brute force (exhaustively guessing passwords). Automated botnets scan the entire IPv4 address space looking for GlobalProtect, SSL-VPN, AnyConnect, and other VPN login pages, then launch sustained campaigns that can last for weeks.
This guide breaks down exactly how these attacks work, what damage they cause, and—most importantly—the controls that stop them.
Where a source-IP block fits: for VPN login abuse, a source-IP block rejects traffic from listed addresses before it reaches the login page. ThreatListPro supplies a hosted IPv4 blocklist for that layer, built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US. It does not replace MFA, lockout tuning, gateway patching or log monitoring, which cover new sources and stolen passwords.
What Is a VPN Brute Force Attack?
A VPN brute force attack is an automated assault on a VPN authentication portal in which bots submit large numbers of username and password guesses, hoping to find a valid credential. There are three common variants:
- Classic brute force: The bot tries every possible password for a given username. This is slow and largely obsolete against modern systems with lockout policies, but it still occurs.
- Credential stuffing: The bot uses username/password pairs leaked from previous data breaches. Because users reuse passwords across services, a share of leaked credentials still works, which is why attackers automate it.
- Password spraying: The bot tries a small number of common passwords (e.g., “Summer2025!”, “Welcome1”, “Company123”) against a large list of usernames. This is designed to stay just under account lockout thresholds, making it harder to detect.
Modern attacks combine all three techniques. A sophisticated campaign might start with password spraying to find easy wins, then shift to credential stuffing using breach data purchased on dark web marketplaces, and fall back to brute force only for high-value targets like admin accounts.
Why Attackers Target VPN Portals
VPN portals are among the highest-value targets on the internet, and for good reason. A single compromised VPN credential gives an attacker direct access to the internal corporate network, bypassing every perimeter defense the organization has built. Here is why VPN portals are disproportionately targeted:
- Internet-facing by design: Unlike internal applications hidden behind firewalls, VPN portals must be publicly accessible so remote employees can connect. This makes them trivially easy to discover through port scanning.
- High-value access: VPN access is typically full tunnel or split tunnel into the corporate LAN. A compromised account can reach file servers, databases, Active Directory, and other internal systems.
- Single-factor authentication: Any portal that still accepts a username and password alone can be taken over with one guessed or leaked password.
- Username enumeration: Some VPN portals return different error messages for “invalid username” versus “invalid password,” allowing attackers to confirm which usernames exist before launching password attacks.
- Easy to fingerprint: GlobalProtect, FortiGate SSL VPN and Cisco AnyConnect login pages are easy to identify from their URLs and responses, so scanners find them quickly. Internet-facing VPN portals see automated login attempts every day.
Signs Your VPN Is Under Brute Force Attack
Look for patterns rather than one failed password. Common signs include:
- Many failed logins: a sudden spike, repeated failures from one source, or low-and-slow attempts spread across many addresses. Use the platform-specific details in the FortiGate SSL VPN log guide.
- Random or nonexistent usernames: automated tools often submit names that do not belong to your organization. A broad username pattern can indicate password spraying.
- Active Directory lockouts: repeated VPN failures can cross the directory's threshold and prevent legitimate users from signing in. See account lockout prevention.
- Logins from unexpected countries: investigate successful or failed attempts from places where users do not normally work, while remembering that mobile networks and VPN services can make geolocation imprecise.
A failed login does not prove that an account was breached. Prioritize successful logins from unfamiliar sources, correct-password attempts stopped by MFA, unexpected MFA prompts, new devices, and unexplained activity after authentication.
The Real Damage: Beyond Security Risk
When most security teams think about brute force attacks, they focus on the risk of credential compromise. But the operational damage is often far worse, even when the attacker never guesses a correct password:
Account Lockouts at Scale
Lockouts are often the first sign of a campaign. Many organizations set an Active Directory lockout threshold, for example locking an account after a handful of failed attempts within 30 minutes. When a brute force bot tries passwords against hundreds of usernames, it locks out each user whose account takes more failed attempts than the threshold allows.
Helpdesk Overload
Every locked account translates to a helpdesk call or ticket. During a sustained campaign, helpdesk staff can spend much of the day unlocking accounts. This is time not spent on actual IT work, and it creates frustration for both support staff and affected users.
Log Noise and Alert Fatigue
A campaign that generates thousands of failed logins a day fills your authentication logs, and a SIEM can raise alert after alert. Security analysts burn hours investigating what is ultimately automated bot traffic, developing alert fatigue that makes them less likely to notice a genuine compromise hidden in the noise.
Authentication Infrastructure Strain
Each failed VPN login attempt hits your RADIUS or LDAP server, your Active Directory domain controllers, and possibly your MFA provider. At high volume this adds load to authentication servers that other services also depend on, not just VPN.
Solutions: How to Stop VPN Brute Force Attacks
There is no single silver bullet. A defense-in-depth approach combines multiple countermeasures. Start with the checklist and per-firewall table below, then see the five main solutions, ranked by how quickly you can deploy them.
Stop It Now: Ordered Checklist
- Enforce MFA on every remote-access account where it is already available, plan the rollout for the rest, and disable unused accounts. Review the GlobalProtect hardening and FortiGate SSL VPN hardening guides.
- Restrict where logins can come from. Allow known networks where practical, or block countries that have no legitimate users. Keep an exception process for travel and mobile networks.
- Block active sources at the firewall. Follow the vendor-neutral steps to block an IP address on a firewall, and place the deny rule before the VPN allow rule.
- Tune failed-login controls. Use source-IP blocking, account lockout, or the vendor's brute-force signature without making a denial-of-service attack against user accounts easier. See how to block an IP after failed logins.
- Patch the VPN gateway to a vendor-supported release and review vendor advisories. FortiGate IPsec deployments should also follow the FortiGate IPsec VPN brute-force guide.
- Investigate successful sign-ins. Revoke suspicious sessions, reset exposed credentials, verify MFA, and review identity, VPN, endpoint, and data-access logs.
Built-In Controls by Firewall
| Firewall | Verified built-in control | ThreatListPro setup guide |
|---|---|---|
| FortiGate | SSL VPN login-attempt limits and a configurable login block time (FortiOS 7.6.3 and later replace SSL VPN tunnel mode with IPsec VPN; see the IPsec guide above); Fortinet also documents MFA and source or geography restrictions. | FortiGate setup |
| Palo Alto GlobalProtect | Vulnerability Protection signatures 40017 and 40169 can be tuned; Palo Alto documents setting the parent signature action to Block IP. | GlobalProtect setup |
| SonicWall | SonicWall recommends Geo-IP filtering on the SSL VPN WAN rule, a Botnet Filter custom list, and the login lockout setting, set to block the attacking IP rather than the account. | SonicWall setup |
| Cisco ASA / AnyConnect | ASA VPN threat detection can automatically shun an IPv4 source after consecutive remote-access authentication failures on supported releases. | Cisco setup |
| Sophos Firewall | Block login denies a source IP after a configured number of failures, including access to the VPN portal. | Sophos setup |
| WatchGuard | Block IP Addresses with Consecutive Failed Logins temporarily blocks sources hitting Mobile VPN with SSL and other Firebox login pages. | WatchGuard setup |
| Check Point | — | Check Point setup |
| pfSense / OPNsense | — | pfSense setup / OPNsense setup |
| MikroTik | — | MikroTik setup |
| UniFi | — | UniFi setup |
For a broader comparison of layered approaches, see the best VPN brute-force protection options for 2026.
1. IP Blocklist (Minutes to Set Up)
An IP blocklist is usually the quickest control to deploy. Configured as an External Dynamic List (EDL) on your firewall, it blocks known attacker IPs at the network layer, before traffic ever reaches your VPN portal. Traffic from a listed IP is dropped at the firewall, so your authentication server never processes that attempt.
ThreatListPro is built from real attacks on live production Palo Alto GlobalProtect VPN portals in the US and protects any firewall that can load a URL list. Paste the URL into your firewall’s dynamic block list (EDL) or equivalent configuration, apply it to a deny rule before the VPN allow rule, and use the recommended hourly polling schedule. The list is checked for new attackers every 6 hours.
2. Rate Limiting (Hours to Configure)
Most next-generation firewalls can rate-limit connections to your VPN portal by source IP—for example, allowing no more than 10 connection attempts per minute per IP. This slows down brute force bots significantly but requires careful tuning. Set the threshold too low and you block legitimate users on shared networks; set it too high and the attacker still gets through.
3. Geo-Blocking (Hours to Configure)
If your users only connect from specific countries, you can block VPN access from all other regions using GeoIP policies on your firewall. This removes attack traffic from blocked regions but does not help against attackers using VPS or residential proxy infrastructure in your home country. It also creates issues for traveling employees.
4. Multi-Factor Authentication (Weeks to Months)
MFA is the gold standard for VPN security. Even if an attacker guesses a correct password, they cannot complete authentication without the second factor. However, MFA rollout is a significant project: you need to select a provider, integrate it with your VPN platform, enroll every user, handle exceptions, and provide support during the transition. For organizations with hundreds or thousands of users, plan for weeks rather than days.
5. Certificate-Based Authentication (Months)
The most robust solution: require a client certificate in addition to (or instead of) username/password. When the portal requires a client certificate, a bot without one cannot complete authentication, so password guessing alone no longer works. However, deploying client certificates requires an internal PKI, an MDM solution to push certificates to devices, and a process for certificate lifecycle management. Expect a longer project than MFA.
Where an IP Blocklist Fits
Every solution above has its place in a mature security program. When lockout tickets are piling up now, a blocklist is a change you can make today while the longer projects run:
- Deployment time: minutes, not weeks
- User impact: no software to install and nothing for users to change
- Fewer lockouts: attempts from listed IPs are dropped at the firewall, so they never reach the login page or count toward a lockout. Attempts from IPs not yet on the list still do.
- Complements every other solution: Blocklists work alongside MFA, rate limiting, and geo-blocking. There is no conflict.
- Less log noise: blocked attempts no longer appear as authentication failures in your VPN and SIEM logs
An IP blocklist is not a replacement for MFA. You should absolutely deploy MFA as a long-term solution. A blocklist reduces the load while you plan and roll out that larger project. Related: how to detect password spraying, GlobalProtect hardening and FortiGate SSL VPN hardening.
Sources
- Fortinet: SSL VPN security best practices
- Palo Alto Networks: Protect GlobalProtect from brute-force attacks
- SonicWall: SSL VPN connection protections
- Fortinet: SSL VPN tunnel mode replaced with IPsec VPN (FortiOS 7.6.3)
- Cisco: ASA threat detection
- Sophos: sign-in security settings
- WatchGuard: block consecutive failed logins
- Microsoft: password-spray investigation
Frequently Asked Questions
What is a VPN brute force attack?
A VPN brute force attack is an automated attempt to gain access to a VPN portal by rapidly trying many username and password combinations. Attackers use botnets, often spread across many source IPs, against portals like GlobalProtect, SSL-VPN, and AnyConnect. Variants include credential stuffing (using leaked credentials from data breaches) and password spraying (trying common passwords against many usernames).
How many login attempts do VPN brute force attacks typically generate?
It varies widely. Some campaigns send bursts of attempts from a few IPs. Password spraying sends only a few attempts per account, spread across many IPs over days or weeks, to stay under lockout thresholds. Count failed logins in your own VPN authentication logs by source IP and by username to see your volume. ThreatListPro's list covers 5.4M+ IPv4 addresses seen in real attacks on live production Palo Alto GlobalProtect VPN portals in the US.
What is the fastest way to stop VPN brute force attacks?
No single control is enough. The quickest change is usually an IP blocklist configured as an External Dynamic List (EDL) on your firewall: it takes minutes to set up and drops traffic from known attacker IPs before it reaches your VPN portal. It does not block attackers that are not on the list yet, so pair it with MFA or certificate authentication, failed-login limits and log monitoring. MFA is what stops a guessed password from logging in.
Why do attackers specifically target VPN portals?
Because a single compromised VPN credential gives direct access to the internal corporate network, bypassing all perimeter security. VPN portals are internet-facing by design, many still lack MFA, and they are easy to discover through automated scanning.
Do VPN brute force attacks cause account lockouts?
Yes. When Active Directory lockout policies are in place, brute force attacks can lock out any user whose account takes more failed attempts than the threshold allows. Our own portals saw 50 or more accounts locked out per day during sustained campaigns.
How do I stop brute force attacks on my VPN?
Use layers: require MFA, tune lockout for password spraying, restrict login sources by network or country, block known attacker IPs at the firewall, monitor failed and successful sign-ins, and patch the gateway. A dynamic block list (EDL) reduces known-source traffic, but it cannot stop attackers that are not listed yet.
Is my VPN being hacked?
Failed VPN logins alone do not prove a compromise, but a successful login from an unexpected country, device, or IP address deserves immediate investigation. Check VPN and identity-provider logs, revoke suspicious sessions, reset affected credentials, verify MFA, and patch the gateway. Treat unexplained account changes or data access as stronger evidence.