People search Kofax data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Kofax-linked incident, with headline counts up to 6K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Kofax breach history matters
Kofax operates in Technology (United States). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2025 — corporate IT intrusion; ~5.5k employees/former staff
Cataloged incident. Tungsten Automation Corporation—successor brand to Kofax, Inc.—notified regulators of a cybersecurity incident discovered May 27, 2025, after unauthorized access beginning May 20, 2025, to internal IT systems. Consumer-facing breach summaries and Maine Attorney General filings cite 5,556 affected individuals (current and former employees) with exposure of identifiers spanning SSN, DOB, contact data, driver-license numbers, and financial account details in some notices; the firm stated customer/partner production da Exposed categories include Workforce PII held in HR/payroll systems per notification templates. BreachHistory cites approximately 6K+ affected records in this row. See the kofax-tungsten-it2025 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple Kofax catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Kofax company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/kofax · Latest: kofax-tungsten-it2025.
Sources: BreachHistory catalog (1 row for Kofax), company and regulator disclosures cited in individual breach records.