OSI SYSTEMS, INC.
bd_0fe82859b7e74031 · schema v1 · pii pii-v1
Full breach record for OSI SYSTEMS, INC. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
OSI Systems, Inc. Total data in the leak: 250GB Leaked data: - Clients: US Government, US Secret Service, IDSS, GLOBAL AEROSPACE INC, Governments of many countries, Casco Automotive Singapore Pte Ltd, Medtronic, Opengear Inc, Sick Sdn Bhd, ST JOSEPH HOSPITAL, SSM HEALTH CARE CORPORATION, UPMC HEALTH SYSTEM and many other large clients all over the world! - Data Classification: Secret - Projects: Raven, Canopy, SPARK, Lighthouse and many other projects. All project information: development, laboratory testing, drawings, subcontractors, suppliers. - Financial data: Company structure. Company income and expenses, shareholders information, such as BlackRock, Inc. and many other investors. Nasdaq data. Contracts with customers and suppliers, NDA contracts. And a lot of other VERY IMPORTANT information!
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 30, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Vermont State AGbd_c9de4de82a0958042026-03-10 · +70dVerified by operator
- Nebraska State AGbd_03b6bd32acad77302026-03-11 · +71dVerified
- New Hampshire State AGbd_0a97f13a9774839c2026-03-11 · +71dVerified by operator
- Maine State AGbd_1be6cf685a8a18642026-03-11 · +71dVerified
Show 5 more filings ↓Show fewer ↑up to 72d gap
- Washington State AGbd_5de9a0ae9cba56792026-03-11 · +71dVerified by operator
- Indiana State AGbd_70c902ae9bbbfa9f2026-03-11 · +71dVerified
- Massachusetts State AGbd_7bfa9894135dbf542026-03-11 · +71dVerified by operator
- California State AGbd_f9015384334e14fd2026-03-11 · +71dVerified
- Texas State AGbd_a5c9fc36c25a18cd2026-03-12 · +72dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗Pattern: first filing Dec 30, last Mar 12 (TX) — a 72-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.