Most edge-device warnings end with "apply the update". This one cannot, and that is the whole point.
What the agencies said
In a notice dated 6 October, the FBI and US Secret Service warned that the FortiBleed campaign is still running. Citing SOCRadar's count, Infosecurity Magazine reports 86,644 compromised devices across 194 countries. eSecurity Planet and The Hacker News carry the same core findings, and Fortinet's position is that this is reused credentials and brute force, not a new software flaw.
The reported method is dull and effective. Scripts scan for exposed FortiGate SSL VPN portals, try passwords from earlier leaks and infostealer logs, and rank victims by revenue and network layout. Password hashes taken from devices are cracked offline on GPU clusters, partly because of legacy hash storage. Once in, intruders add their own administrator accounts, keep session cookies, and push on into Active Directory with enumeration and spraying. The newest twist in the notice is lockout: changed passwords and disabled accounts so the owner cannot get back in. The agencies tie the access to INC, Lynx and Payload ransomware affiliates.
Why firmware alone does nothing
A fixed build removes a bug. It does not remove an administrator named something forgettable, a cracked VPN password that is still valid or a session cookie somebody copied last month. If your device was reachable and your credentials were ever in a dump, "we are on the latest version" tells you nothing about whether it is clean.
What we would do this week
- Pull the list of local administrators and VPN users from each FortiGate and compare against HR and your directory. Anyone unexplained is a finding, not a tidy-up.
- Move management interfaces off the internet. If they must stay reachable, restrict them to named source addresses.
- End all active admin and VPN sessions, reset every credential, and enforce phishing-resistant multi-factor authentication for VPN and admin logins.
- Export and read the configuration history and audit log for changes since June, particularly new accounts, new local users, and altered trusted hosts.
- Hunt downstream: failed and successful logins from the firewall's address range to domain controllers, and bursts of directory queries.
- Rehearse the lockout case. Know who holds console access and how you would rebuild a device from a known-good configuration without trusting the old one.
- If you find compromise, report it to your national cyber centre or law enforcement and use CISA's Eviction Strategies Tool as the agencies suggest.
We run edge-device credential reviews and recovery exercises for UK organisations. Contact sales@halfteck.com.