Administrators of over 86,000 devices
A large-scale credential theft campaign, publicly tracked as FortiBleed, has resulted in the compromise of at least 86,000 Fortinet FortiGate firewalls and SSL VPN gateways across 194 countries. The incident, attributed to a Russian-speaking threat actor, does not leverage a new vulnerability but rather capitalizes on poor credential hygiene and legacy password hashing mechanisms. The threat actor amassed credentials from various sources, including previous data breaches and infostealer malware logs, and successfully cracked them to gain unauthorized access. In response, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent advisory directing organizations to immediately harden their Fortinet appliances by rotating all credentials, enabling MFA, and auditing for lateral movement.
The FortiBleed campaign represents a significant threat to organizations relying on Fortinet security appliances. The core of the attack is a massive credential stuffing and cracking operation. Threat actors collected a large dataset of credentials associated with FortiGate devices and utilized a 45-GPU cluster managed with the Hashtopolis tool to crack password hashes. The success of this campaign is largely attributed to two factors: the use of weak or default passwords by administrators and the exploitation of older, less secure hashing algorithms previously used in FortiGate configuration files.
Once valid credentials were obtained, the attackers gained access to the SSL VPN and administrative interfaces of the firewalls. This initial foothold was then used to deploy post-exploitation tools like Chisel and Neo-reGeorg for tunneling traffic and facilitating lateral movement into the internal corporate networks. The most affected sectors include telecommunications, government, and education, with a high concentration of compromised devices in India, the U.S., Mexico, Colombia, and Thailand.
The attack chain is straightforward but highly effective, relying on operational security failures rather than sophisticated exploits.
Chisel and Neo-reGeorg to establish persistent access and pivot into the internal network. This corresponds to T1572 - Protocol Tunneling. This allows them to bypass perimeter defenses and move laterally, as described in T1021 - Remote Services.The core issue is the historical use of weaker hashing mechanisms for credentials in FortiGate configuration files. While newer versions use PBKDF2, many devices may still have accounts with legacy hashes if they were created on older firmware and never updated.
The business impact of a compromised edge security appliance is severe. Attackers with administrative access to a FortiGate firewall can:
The reputational damage and regulatory fines resulting from a data breach originating from this vector can be substantial. The cost of incident response, forensic analysis, and remediation adds significant financial strain.
No specific file hashes, IP addresses, or domains were provided in the source articles.
Security teams may want to hunt for the following patterns which could indicate related activity:
process_namechiselprocess_nameneoregeorglog_sourceFortiGate Event Logsnetwork_traffic_patternUnusual outbound connections from Firewall Mgmt Interfacecommand_line_patterndiagnose sys session listDetection:
Response:
Immediate Actions:
Strategic Improvements:
show system admin. If any accounts are using the legacy format, they must be reset.International agencies issue joint alert on FortiBleed, reinforcing threat and detailing credential stuffing TTPs.
Enforcing MFA on all administrative and VPN accounts is the most critical defense against credential-based attacks.
Mapped D3FEND Techniques:
Enforce strong, complex passwords and prevent reuse to make cracking and guessing more difficult.
Mapped D3FEND Techniques:
Regularly audit and remove default, unused, or shared privileged accounts.
Restrict management interface access to a dedicated, internal administrative network.
Mapped D3FEND Techniques:
Immediately enforce phishing-resistant Multi-Factor Authentication for all administrative and SSL-VPN user access on FortiGate devices. This is the single most effective countermeasure against the FortiBleed campaign, as it invalidates stolen credentials alone. Prioritize hardware tokens (FIDO2/WebAuthn) or certificate-based authentication over less secure methods like SMS or push notifications, which are susceptible to MFA fatigue attacks. For administrative access, MFA should be required for both GUI and CLI sessions. For SSL-VPN users, ensure that all user groups, including third-party contractors and partners, are enrolled. This action directly hardens the initial access vector used by the threat actors and serves as a powerful compensating control even if password hygiene is poor. The implementation should be coupled with user training to ensure smooth adoption and awareness of MFA-related social engineering tactics.
Implement and enforce a robust password policy for all FortiGate local user accounts. This policy should mandate a minimum length of 15 characters, including a mix of uppercase letters, lowercase letters, numbers, and special characters. Critically, disable or remove all default accounts (e.g., 'admin') and replace them with named administrator accounts. Configure the device to enforce password history to prevent reuse and set a maximum password age of 90 days. Forcing a password change for all users immediately will invalidate any currently compromised credentials. This D3FEND technique directly addresses the root cause of the FortiBleed campaign's success: weak, default, and easily crackable passwords. Use FortiGate's built-in password policy enforcement features to automate this control.
Isolate the FortiGate management interfaces (both HTTPS and SSH) from the public internet and general corporate user networks. Create a dedicated, segmented management VLAN or subnet accessible only from a limited set of hardened administrative workstations or a bastion host. Use firewall rules on the FortiGate itself ('Local-in Policy') to strictly control which source IPs can connect to the management ports. This practice of network isolation drastically reduces the attack surface, making it impossible for external attackers to even attempt to log in, regardless of whether they have valid credentials. This directly counters the initial access phase of the FortiBleed attack and is a foundational security best practice for all network infrastructure.
CISA issues an urgent advisory regarding the FortiBleed campaign.
Multiple security news outlets report on the scale of the compromise, with figures ranging from 74,000 to over 86,000 devices.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.