Imagine a burglar who, instead of breaking into your house, steals the lock maker's blueprints and its list of known weaknesses. That is roughly what happened to F5, a company whose BIG-IP devices manage and protect traffic at the edge of many large organisations' and governments' networks.
What F5 disclosed
In a filing to the US Securities and Exchange Commission on 15 October 2025, F5 said that on 9 August 2025 it "learned that a highly sophisticated nation-state threat actor had gained unauthorized access to certain Company systems."
It added that "the threat actor maintained long-term, persistent access to certain F5 systems, including the BIG-IP product development environment and engineering knowledge management platform", and that stolen files included "certain portions of the Company's BIG-IP source code and information about undisclosed vulnerabilities that it was working on in BIG-IP."
Some files from its knowledge platform also "contained configuration or implementation information for a small percentage of customers".
The disclosure was delayed: "On September 12, 2025, the U.S. Department of Justice determined that a delay in public disclosure was warranted".
What F5 said was not affected
F5 said it was "not aware of any undisclosed critical or remote code vulnerabilities", nor of "active exploitation of any undisclosed F5 vulnerabilities", and had "no evidence of modification to our software supply chain, including our source code and our build and release pipelines."
F5 did not name the attacker. SecurityWeek reported that the incident was linked to China and to BRICKSTORM malware associated with the group Google tracks as UNC5221.
Governments respond
- CISA issued Emergency Directive 26-01, requiring US federal agencies to inventory F5 devices, check whether management interfaces were exposed to the internet, apply updates by 22 October (others by 31 October) and disconnect public-facing end-of-support devices. CISA warned the attacker's access to source code "could provide that threat actor with a technical advantage".
- The UK NCSC said "There is currently no indication that any customer networks have been impacted via the compromise of the F5 network", and advised "organisations to follow the guidance issued by F5 and to install the latest security updates."
Why it matters
Source code and private bug details are a roadmap for finding new vulnerabilities. With them, attackers can look for flaws faster than defenders can fix them. And because edge devices sit at the boundary of networks, a single flaw can open the door to everything behind them.
What it means for you
At home: no direct action — but this is why the routers and devices at the edge of any network need prompt updates.
If you run a small business: if you use F5 or other enterprise network appliances (often through an IT provider), confirm they are updated and that their management pages are not reachable from the internet.
If you work in IT or at an MSP:
- Inventory every edge appliance across clients, including make, model, software version and support status.
- Never expose management interfaces to the internet.
- Replace end-of-support appliances; they will not get fixes for newly found flaws.
- Watch vendor advisories closely after any vendor breach: more patches may follow.
The bottom line
The F5 breach was a supply-chain warning from the very top of the security stack. When a vendor's secrets are stolen, the customers' best defence is speed: know what you run, update it quickly and keep management interfaces off the internet.
This article summarises and comments on the sources listed below. It is general information, not legal or professional advice.