OmniVision Technologies, Inc.
bd_b73041d4d6f73f25 · schema v1 · pii pii-v1
Full breach record for OmniVision Technologies, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cactus 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
Since being founded in 1995 OMNIVISION has been at the leading-edge of technology, developing and delivering advanced digital imaging, analog, and touch & display solutions for multiple applications across several industries. As a global fabless semiconductor organization, our award-winning innovative technologies have enabled smoother human/machine interfacing solutions within the automotive, medical, security & surveillance, computing, mobile phone, and emerging technology spaces.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 26, 2023
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 (5) · sorted by filing gap
- California State AGbd_4eaa4454379dadad2024-05-17 · +234dCandidate
- New Hampshire State AGbd_737e9d94a4f6d6ad2024-05-17 · +234dVerified
- Indiana State AGbd_c782ece14f15fac02024-05-17 · +234dVerified
- Massachusetts State AGbd_cb9631e9e1713a292024-05-17 · +234dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 235d gap
- Vermont State AGbd_5585086e39bebe112024-05-18 · +235dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Sep 26, last May 18 (VT) — a 235-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.
cactus
According to ransomware.live, The CACTUS ransomware is said to have emerged around March 2023. The group became known for exploiting vulnerabilities to gain initial access and maintain a presence within the organization's infrastructure. There is little known information about the ransomware group, except that it emerged on the mentioned date and, following encryption, a text file named 'cAcTuS.readme.txt' would be created. Additionally, encrypted files were altered to the '.cts1' extension, and data exfiltration and victim extortion were conducted through the use of the service known as Tox. Source: https://github.com/crocodyli/ThreatActors-TTPs