The short version
- The campaign. FortiBleed targets internet-facing FortiGate firewalls and SSL VPN portals, taking them over with reused or leaked credentials and offline cracking of stored password hashes. It has been running since June 2026.
- The scale. SOCRadar says roughly 86,644 devices in 194 countries are confirmed compromised, a count of breached devices rather than an exposure estimate. The FBI and US Secret Service issued a joint advisory on the activity in early October.
- The lockouts. Attackers create new administrative accounts on the appliances and in some cases delete or change the passwords of existing accounts, which the agencies say may leave victims unable to reach their own devices.
- The advice. CISA tells Fortinet customers to reset VPN and administrative passwords, end active sessions and enable phishing-resistant authentication, while the FBI and US Secret Service recommend resetting passwords, enabling phishing-resistant multifactor authentication, restricting management access and reviewing logs and account lists.
Timeline
| Date | Event |
|---|---|
| June | FortiBleed is first documented; the campaign has been running since June 2026 against FortiGate firewalls and SSL VPN appliances. |
| 19 June | The operation is estimated to hold more than 86,644 working device credentials across 194 countries as of this date. |
| 7 Oct | The Hacker News reports a joint FBI and US Secret Service warning that the campaign is still active and still scanning internet-exposed Fortinet firewalls. |
| 8 Oct | SecurityWeek reports that the attackers are locking organisations out of their Fortinet devices by changing passwords and deleting accounts. |
How the campaign works
The Hacker News describes a five-stage operation. Attackers scan for exposed Fortinet portals, then use credential stuffing and password spraying with credentials taken from earlier leak dumps and infostealer logs.
On the device they deploy a Go-based tool called FortigateSniffer, which passively intercepts authentication traffic across 24 protocols to collect credentials and password hashes. Those hashes go to a GPU-accelerated cracking cluster running Hashmat and Hashtopolis. The agencies say legacy SHA-256 password storage on the appliances makes the cracking easier.
Cracked credentials are enriched, sorted and validated, with scripts that filter out honeypots and prioritise high-value targets. They are then used for lateral movement, Active Directory enumeration, Kerberos validation and SMB authentication. The agencies note that "New administrative accounts were created on the firewall to maintain persistence." Data is taken from network shares while stolen session cookies keep the attackers authenticated.
Scale and impact on victims
SOCRadar, which first documented the campaign, says about 86,644 devices in 194 countries are confirmed compromised. It says devices breached months ago remain in the actors' validated inventory. The Hacker News reports the same figure as working device credentials as of 19 June.
SecurityWeek gives a slightly different early figure: within a week the attacks hit over 86,000 Fortinet devices in 190 countries. Neither source translates the device count into a number of affected organisations.
The lockouts are the most visible effect. The joint advisory says some victims may lose access if the actor deletes or changes the password for original accounts, and that accounts are removed in some cases to keep the organisation out while the intruders move further into the environment.
Attribution and ransomware links
The Hacker News describes a Russian-speaking operation and reports that the adversary is suspected to be an initial access broker — an intermediary that sells stolen access rather than using it — citing overlaps with the INC and Lynx ransomware operations. SecurityWeek says a Russian initial access broker was blamed and that working VPN configurations and target lists are sold to other threat actors.
Neither source names the group, identifies a country of origin beyond the Russian-speaking description, or states that ransomware has actually been deployed using this access. The connection to ransomware is presented as operator overlap and likely downstream use, not as an established fact.
The Hacker News also recalls earlier CISA guidance to FortiGate customers: move to phishing-resistant authentication, end active SSL VPN and administrative sessions, reset passwords, store administrator credentials with PBKDF2 and review logs for suspicious activity.
What is not known yet
- Which group or individual runs the campaign; the sources describe a Russian-speaking operation or broker but name no actor.
- How many distinct organisations are affected, since the 86,644 figure counts devices rather than customers.
- Whether ransomware has been deployed through the access sold on, beyond the reported overlaps with INC and Lynx.
- How much data was taken from network shares in the exfiltration stage, and from how many victims.
- Whether devices recorded as compromised in June have since been remediated or are still under attacker control.
What to do
If you run FortiGate firewalls or Fortinet SSL VPN
- Reset every Fortinet VPN and administrative password and terminate active SSL VPN and administrative sessions.
- Enable phishing-resistant multifactor authentication, restrict management access to the appliances and validate API keys.
- Check for accounts you did not create, including names such as forticloud-sync, support_fortinet, adminsslvpn and itadmin, and for original accounts that have been deleted or had passwords changed.
- Store administrator credentials with PBKDF2 rather than SHA-256, and review firewall and VPN user lists, configurations and logs for suspicious activity.
If you find signs of compromise
- Isolate the affected device and collect logs and other artefacts before making changes.
- Scope the intrusion, evict the attacker and report the incident to the FBI and US Secret Service as the joint advisory asks.
For everyone else
- Treat credentials that appear in infostealer logs as already compromised, and remove internet-facing management interfaces that do not need to be reachable from outside.
- Where an appliance still hashes passwords with a fast legacy algorithm, plan to replace it, because harvested hashes of that kind fall quickly to offline cracking.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.