Your firewall is supposed to be the one thing standing between your company and the internet’s worst people. This week we learned how badly that assumption can fail: the Fortinet Palo Alto firewall breach has exposed more than 70,000 credentials stolen from FortiGate, FortiWeb and GlobalProtect systems around the world — and the campaign behind it ran quietly for months before anyone published the details. Here is what actually happened, who is behind it, and what to check today.
What Happened: The k0t Campaign, Explained
The Fortinet Palo Alto firewall breach is not one hack but a whole campaign. On October 21, 2026, researchers at Group-IB and NyxLab published a joint investigation into an operator known as k0t, who has spent months breaking into internet-facing firewalls and VPN gateways — specifically Fortinet FortiGate and FortiWeb appliances, and Palo Alto Networks GlobalProtect portals. The haul the researchers uncovered: more than 70,000 exposed credentials and related records, including network-device logins and LDAP directory data pulled from real organizations.
One honest caveat before we go further: 70,000 records does not automatically mean 70,000 successful break-ins. The researchers themselves say not every credential was necessarily valid or used. But they also found hard evidence — stolen passwords, signs of persistent remote access, and cases of data being copied out — at organizations on multiple continents. This was not a smash-and-grab. It was a business.
How the Attackers Got In
The attack chain reads like a checklist of everything security teams warn about. First, recon: the operators used public scanning engines like FOFA and ZoomEye to enumerate internet-facing VPN and firewall appliances at scale, filtering targets by product. No careful victim selection — they built lists of every exposed FortiGate, FortiWeb and GlobalProtect box they could find, then worked through them.
From there, they mixed three methods: exploiting known software flaws, guessing weak passwords, and reusing credentials leaked from earlier breaches. Two techniques stand out. On FortiWeb, a flaw reportedly let unauthenticated attackers run administrative commands through crafted web requests — then simply create fresh administrator accounts for themselves. On FortiGate, the operators downloaded device configuration files and decrypted the passwords stored inside them using a known default key. Read that again: the firewall guarding the network was holding reusable passwords, protected by a key everyone in the industry knows.
Once inside an edge device, an attacker sits at the perfect vantage point — every remote worker’s VPN session, every branch connection, passes through it. From there, persistent access and data exfiltration are a matter of patience.
Who Is k0t?
According to the Group-IB and NyxLab investigation, the operator known as k0t (aliases include CryptoFeel, Member19 and QazWsxShop) was first seen in the wild on October 22, 2025 — almost exactly a year before this report dropped. The actor is assessed to have connections with ransomware groups such as Qilin and The Gentlemen, and likely works as an initial access broker: the person who breaks in first and sells that access to the crews who deploy ransomware and do the extorting. His dark-web activity shows a keen interest in buying fresh exploit code and premium accounts for search engines like FOFA and ZoomEye — in other words, he invests in better ways to find the next exposed firewall.
That broker model is exactly why a credential dump matters even when nobody’s files have been encrypted yet. Access gets sold. The breach you ignore today becomes somebody else’s ransomware incident next quarter.
Who Got Hit — and When
The victims are global and, frankly, indiscriminate: any organization with an exposed, poorly protected edge device was a candidate. Roughly 38% of victims are in Asia-Pacific, followed by 31.9% in Latin America, 15.8% in Europe and 12.7% in the Middle East and North Africa. A significant chunk of the compromises happened between February and June 2026 — overlapping with another credential-harvesting campaign researchers called FortiBleed. What you’re seeing this week is not a new attack so much as the bill arriving for months of quiet intrusions.
Why Firewalls Keep Being the Front Door
Here’s the uncomfortable pattern I keep coming back to: the device meant to be the guard is now the most attacked object on the network. Edge devices are attractive for boring, rational reasons. They are internet-facing by design, so anyone can knock. They are appliances, so they often patch slower than regular servers — nobody wants to reboot the firewall during business hours. Their config files concentrate exactly the secrets an attacker wants. And when an implant or a rogue admin account lives on the firewall itself, much of a company’s normal monitoring simply doesn’t see it. We saw the same logic in the separate PEERSTITCH case this month, where an implant lived inside a FortiGate at a telecom provider for roughly 25 months. The edge is the new endpoint.
What To Do If You Run Fortinet or Palo Alto Gear
If your organization runs FortiGate, FortiWeb or GlobalProtect, treat this as a checklist for today, not next month:
- Patch now. Bring FortiOS, FortiWeb and PAN-OS/GlobalProtect fully up to date — the intruders are exploiting known flaws, not magic zero-days.
- Rotate every credential the device knows. Anything stored in a FortiGate config should be considered exposed: admin passwords, LDAP bind accounts, VPN credentials, API keys. When your team sets the new ones, generate them properly — our free Password Generator creates strong random passwords that are actually worth rotating to.
- Hunt for rogue admin accounts. Attackers created their own administrators. Audit every local account on every edge device and delete anything you can’t explain.
- Get management interfaces off the internet. If the admin portal doesn’t need to face the world, it shouldn’t. Restrict it to a jump host or management network, and enforce MFA on GlobalProtect and admin access.
- Review logs for config exports. A downloaded configuration file is the tell. If you find one you didn’t make, assume the passwords in it are public and rotate them everywhere they were reused.
The Bottom Line
The Fortinet Palo Alto firewall breach is a story about housekeeping, not genius hacking. An access broker scanned for exposed boxes, used known flaws, weak passwords and a default encryption key, and walked away with 70,000+ credentials from organizations that mostly never noticed. The fixes are equally unglamorous: patch, rotate, audit, and stop leaving the keys inside the guard dog’s collar. If your company touches any of this hardware, today is a good day to check.

[…] security product. We have covered the same lesson before with the 9.8-rated Linux kernel flaw, the Fortinet and Palo Alto firewall breach, and the Sourcenext breach that exposed 22.5 million records: a flaw is disclosed, a patch ships, […]