how it happened
- whoa nation-state actorF5's words; any country named comes from press reports
- the gapF5's engineering systemsthe BIG-IP development environment and the engineering knowledge platform
- thencode, open flaws, configssource code, undisclosed vulnerabilities, some customers' setup details
- the resultthe work moves to customersinventory, patch within days, close admin pages, hunt
what everyone assumed
F5’s customers have not said what they believed beforehand, so this belief is an inference from the response that followed. It is the ordinary way to think about a supplier. A firewall, load balancer or remote-access gateway is a product. The vendor writes the code, finds the bugs, and ships fixes. The customer’s job is to install them. If the vendor itself is breached, that sounds like the vendor’s incident, with the vendor’s lawyers and the vendor’s investigators.
That holds when the attacker takes something that belongs only to the vendor. It fails when what the attacker takes is a map of the box sitting at the edge of every customer’s network.
what happened
Everything in this section comes from F5’s filings unless another source is named.
On 9 August 2025, F5 says in its Form 8-K of 15 October 2025, it learned that a “highly sophisticated nation-state threat actor” had gained unauthorized access to certain company systems. The actor had long-term, persistent access to two places: the BIG-IP product development environment and the engineering knowledge management platform. BIG-IP is F5’s family of appliances and software that sit in front of applications and handle traffic, remote access and web protection at the edge of customer networks.
The attacker copied files out of both. F5 lists three kinds of material in them:
- Source code. Portions of the BIG-IP source code.
- Undisclosed flaws. Information about undisclosed vulnerabilities F5 was working on in BIG-IP, which means flaws known inside F5 and not yet disclosed to customers. F5 added that it was not aware of any undisclosed critical or remote code execution flaws, or of active exploitation of any undisclosed F5 flaw.
- Customer details. Some files from the knowledge platform contained configuration or implementation information for “a small percentage of customers”. F5 said it would contact those customers directly. No filing opened for this page gives a number.
F5 also lists what it found no evidence of. It says it has no evidence of modification to its software supply chain, including its source code and its build and release pipelines, and that independent reviews validated this; its disclosure statement names NCC Group and IOActive. It found no evidence of access to its CRM, financial, support case management or iHealth systems, or to NGINX source code, its Distributed Cloud Services or Silverline. On 12 September 2025 the US Department of Justice decided a delay in public disclosure was warranted. None of the sources opened for this page says how the attacker got in.
Who did it rests on press reports. F5 says only “nation-state” and has named no country. Bloomberg reported on 17 October 2025, citing people familiar with the matter, that the attackers were state-backed hackers from China, that F5 told customers they had been inside for at least 12 months, and that F5 sent customers a threat hunting guide for malware called BRICKSTORM. China’s foreign ministry rejected the accusation. Google’s research on BRICKSTORM of 24 September 2025, which is vendor research, describes a suspected China-nexus cluster aimed at software and technology companies, and says such targeting offers a chance to steal intellectual property to develop zero-day exploits. That research does not mention F5.
This differs from SolarWinds and 3CX, where customers installed builds an attacker had tampered with. F5 says nothing it shipped was altered. The risk to customers came from knowledge: what the code does, where it is weak, and in some cases how a given customer had set it up.
step by step
- the box at the edge runs the vendor's codeCustomers patch when the vendor publishes, and the vendor's own engineering systems sit outside their view.
- 9 August 2025F5 learns an attacker is insideThe 8-K says a nation-state actor had long-term, persistent access to the BIG-IP development environment and the engineering knowledge management platform.the assumption breaks here
- 12 September 2025disclosure is held backThe US Department of Justice decides a delay in public disclosure is warranted.
- 15 October 2025updates, directive and alerts on one dayF5 files its 8-K and ships updates; CISA issues ED 26-01 with patch deadlines of 22 and 31 October; the NCSC tells UK organisations to act.
- March 2026a flaw from the October batch is exploitedF5 recategorises CVE-2025-53521 as remote code execution and reports active exploitation; no source links it to the stolen files.
how it surfaced
F5 disclosed on 15 October 2025, with updates for BIG-IP, F5OS, BIG-IP Next for Kubernetes, BIG-IQ and its APM clients released the same day. Its disclosure statement told customers to install them as soon as possible, to apply its hardening guidance, and to stream BIG-IP events into their monitoring. BleepingComputer reported the same day that F5 had also rotated the certificates and keys it uses to sign its products.
Governments treated the stolen material as a threat to every installed box. CISA’s Emergency Directive 26-01, issued on 15 October 2025, says the code could let the actor search for logical flaws and zero-day vulnerabilities and build targeted exploits, and that exploitation could expose embedded credentials and API keys and lead to lateral movement and persistent access. It ordered US federal civilian agencies to:
- inventory every BIG-IP device and F5 software instance;
- check whether each device’s management interface is reachable from the internet;
- install the latest updates for F5OS, BIG-IP TMOS, BIG-IQ and BNK/CNF by 22 October 2025, checking F5’s published checksums first, and update everything else by 31 October 2025;
- apply every later F5 update within one week of release;
- disconnect public-facing F5 devices past end of support;
- report a summary by 29 October and a full inventory by 3 December 2025.
The directive binds only those agencies. CISA’s news release quotes its acting director saying the same risks extend to any organisation using the technology. The NCSC’s notice of the same day said there was “no indication that any customer networks have been impacted”, and still told UK organisations to find every F5 product, keep management interfaces off the internet, assess any exposed one for compromise, patch, replace end-of-support products and hunt for intruders.
The record kept moving. CVE-2025-53521, a BIG-IP APM flaw whose CVE record was published on 15 October 2025, was recategorised by F5 as an unauthenticated remote code execution flaw. The NCSC wrote on 30 March 2026 that F5 was aware of active exploitation and advised checking for compromise on affected systems regardless of when they were updated. CISA added it to its Known Exploited Vulnerabilities catalog on 27 March 2026. No source opened for this page says the exploitation used anything stolen from F5.
For F5, the cost is on the record. Its 10-K of 25 November 2025 expected near-term disruption to sales cycles. Its 10-Q of 6 August 2026 reports $26.5 million of costs in response to the incident for the nine months to 30 June 2026, $5.3 million of insurance recoveries, and a small number of inquiries from governmental authorities. The cost for customers, in staff time spent patching and checking boxes, appears in no filing.
The same pattern shows up on the customer side in the SonicWall cloud backup case, where customers’ firewall settings sat in the vendor’s systems, and in CitrixBleed 2, where patching did not undo what an attacker had already taken.
The vendor’s engineering systems are part of your edge, and you hear about a break-in there only when the vendor tells you.
When your firewall vendor next announces a breach, would you know within a day which boxes you own, who can log in to them and what the vendor holds about your setup?
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersSomeone breaks into the vendor's engineering systems, studies the code your box runs and reads the notes about flaws that are not fixed yet.what it costs youWhen the vendor finally tells customers, your company has days to find, patch and check its boxes, and nobody knows who holds the login.
- or it goes like thisit happenedSolarWinds / Sunburst, 2020howA genuine, signed update from a certified vendor carries a backdoor.what leavesa quiet way into your networkwho ends up with ita state intelligence service
- or it goes like thisit happenedtj-actions/changed-files, 2025howA build helper everyone uses is hijacked and its versions repointed.what leavessecret keys, printed into build logswho ends up with itanyone reading public logs
sources
- F5, Inc.: Form 8-K, 15 October 2025, Item 1.05 Material Cybersecurity Incidents (SEC filing)
- F5, Inc.: Exhibit 99.1 to Form 8-K, F5 Security Incident: Disclosure Statement, posted on MyF5 15 October 2025 (SEC filing)
- F5, Inc.: Form 10-K for the fiscal year ended 30 September 2025, filed 25 November 2025 (SEC filing)
- F5, Inc.: Form 10-Q for the quarter ended 30 June 2026, filed 6 August 2026 (SEC filing)
- CISA: ED 26-01, Mitigate Vulnerabilities in F5 Devices, 15 October 2025
- CISA: CISA Issues Emergency Directive to Address Critical Vulnerabilities in F5 Devices, 15 October 2025
- CISA: CISA Directs Federal Agencies to Mitigate Vulnerabilities in F5 Devices, 15 October 2025
- NCSC-UK: Confirmed compromise of F5 network, 15 October 2025
- NCSC-UK: Vulnerability affecting F5 BIG-IP APM, 30 March 2026
- Canadian Centre for Cyber Security: F5 security advisory (AV25-669), 15 October 2025, Update 1 27 March 2026
- CVE record CVE-2025-53521 (F5 as CNA), published 15 October 2025, updated 31 March 2026
- CISA: Known Exploited Vulnerabilities Catalog (JSON feed, catalogVersion 2026.11.10)
- Bloomberg, republished by The Philadelphia Inquirer: Potentially 'catastrophic' cyber firm breach blamed on China, 17 October 2025
- SecurityWeek: F5 Hack: Attack Linked to China, BIG-IP Flaws Patched, Governments Issue Alerts, 16 October 2025
- BleepingComputer: Hackers breach F5 to steal undisclosed BIG-IP flaws, source code, 15 October 2025
- Google Threat Intelligence: Another BRICKSTORM: Stealthy Backdoor Enabling Espionage into Tech and Legal Sectors, 24 September 2025 (vendor research)
your turn
what you can do about it
this week
List every configuration or support file your company has sent to a network vendor, and change the passwords and keys inside any that held them.
F5 said some files taken from its engineering platform held configuration or implementation information for a small share of customers. Support cases, diagnostic uploads and cloud backups put the same kind of detail into a vendor's systems. Ask your IT provider or vendor contact what has been sent and when, then treat any secret in those files as known to someone else. [The guide on the box at the edge](/read/edge-devices) covers the rest of the list: who owns each box, whether its admin page answers from the internet and who reads the vendor's notices. [The IT provider guide](/read/it-provider-admin) covers what to ask the firm that runs it, and [the engineer's laptop guide](/read/engineer-laptop) explains why the laptops engineers stay signed in on reach further than anyone planned.
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
