whogothacked

F5, Inc. cybersecurity incident record

What is on record for F5, Inc.?

There is one cybersecurity incident disclosed under Item 1.05 of Form 8-K on record for F5, Inc., disclosed to the SEC on October 15, 2025.

Disclosed to the SEC on Form 8-K.

How many
No source on record gives a number.
Data listed
Not itemized. The description quoted below may name the data involved.
Source record
Open this record at sec.gov
What to do
If you received a notice letter, start with the letter: keep it, use any free monitoring it offers, and check that the letter is real.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Also filed as
F5, INC.
Sector
Computer Communications Equipment
State
Washington
Ticker
FFIV as of its latest SEC filing on record (shown to identify the company; nothing on this page is investment advice)

Was F5, Inc. hacked?

F5, Inc. disclosed a cybersecurity incident in a Form 8-K under Item 1.05, first filed on October 15, 2025.

The company's Form 8-K filing describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The incident on record

Form 8-K Item 1.05 filed with the SEC

Official record

1 source record

F5, Inc. filed a Form 8-K under Item 1.05 (Material Cybersecurity Incidents) disclosing a cybersecurity incident to the US Securities and Exchange Commission on October 15, 2025.

The record behind this entry

  1. First record

    Form 8-K Item 1.05 filed with the SEC under the name F5, INC.

    In the company's own words, from its Form 8-K under Item 1.05 (Material Cybersecurity Incidents)

    On August 9, 2025, F5, Inc. (the “Company”, “F5”, “we”, or “our”) learned that a highly sophisticated nation-state threat actor had gained unauthorized access to certain Company systems. The Company promptly activated its incident response processes, and has taken extensive actions to contain the threat actor. To support these activities, the Company engaged leading external cybersecurity experts.

    Show the rest of this text (361 more words)Hide the rest of this text

    The Company believes its containment actions have been successful and, since the initiation of its containment efforts, has not observed any evidence of new unauthorized activity. The investigation, monitoring, and related activities are ongoing. The Company is actively engaged with federal law enforcement and government partners in connection with this incident. Additionally, the Company is implementing further measures to strengthen its security environment and protect its customers.

    During the course of its investigation, the Company determined 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. Through this access, certain files were exfiltrated, some of which contained certain portions of the Company’s BIG-IP source code and information about undisclosed vulnerabilities that it was working on in BIG-IP. We are not aware of any undisclosed critical or remote code vulnerabilities, and we are not aware of active exploitation of any undisclosed F5 vulnerabilities. We have no evidence of modification to our software supply chain, including our source code and our build and release pipelines. This assessment has been validated through independent reviews by leading cybersecurity research firms.

    We have no evidence of access to, or exfiltration of, data from our CRM, financial, support case management, or iHealth systems. However, some of the exfiltrated files from our knowledge management platform contained configuration or implementation information for a small percentage of customers. The Company is currently reviewing the contents of these files and will communicate with affected customers directly as appropriate.

    We have no evidence that the threat actor accessed or modified the NGINX source code or product development environment, nor do we have evidence they accessed or modified our F5 Distributed Cloud Services or Silverline systems.

    On September 12, 2025, the U.S. Department of Justice determined that a delay in public disclosure was warranted pursuant to Item 1.05(c) of Form 8-K. F5 is now filing this report in a timely manner.

    As of the date of this disclosure, this incident has not had a material impact on the Company’s operations, and the Company is evaluating the impact this incident may reasonably have on its financial condition or results of operations.

What to do if this involved you

This entry has no itemized list of the kinds of data involved. The description quoted above may name them, and a notice letter, if you received one, is the place to look. What to do with a notice letter

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that F5, Inc. did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/f5-inc