MalwareTechnologyInformationRansomwareData EncryptedCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDFinancial accountMediumContained

Ampex Data Systems

bd_5a80584f7d8fe5e9 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 21, 2026

Filed

May 27, 2026

To disclose

10 weeks

Affected

Not disclosed

Linked

7 filings

Confidence

65%

Full breach record for Ampex Data Systems →

Ampex Data Systems Corporation experienced a ransomware incident on March 21, 2026, where a threat actor accessed and encrypted the network at one office location. The incident affected current and former contractors, employees, and dependents, potentially exposing names, addresses, social security numbers, dates of birth, and in limited cases, driver's license or banking information. The company contained the incident on March 23, 2026, and is offering 12 months of credit monitoring and fraud assistance.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d10 weeks discovery → filing

Incident timeline

discovery → filing · 10 weeks / 67 days

Mar 21, 2026

Begins

Mar 21, 2026

Discovered

May 27, 2026

Filed

vs. sector median

9 wks faster

This filing is one of 7 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (2)

Leak Siteplaybd_571e436d5a1335c12026-03-30 · +57dVerified
Leak Siteplaybd_cde8e1e1cbada45f2026-01-12 · +135dVerified by operator

Regulatory filings (4) · sorted by filing gap

Nebraska State AGbd_f61a1973de4b25352026-05-26 · +1dVerified
Massachusetts State AGbd_68635f5ae613817a2026-05-19 · +8dVerified by operator
Maine State AGbd_6c8fa41d68c176072026-05-18 · +9dVerified by operator
Indiana State AGbd_56ff4da0557796012026-03-26 · +62dVerified by operator

Name: Ampex Data Systems
norm: ampex data
Domain: ampex.com

Name: Ampex Data Systems
norm: ampex data
Domain: ampex.com
Industry: Technologyllm

Discovered: Mar 21, 2026
Breach occurred: Mar 21, 2026
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security numberDate of birth
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Notified the FBI’s Internet Crime Complaint Center (IC3)Notified the Department of Defense Cyber Crime Center (DC3)

During the incident: Shut down our servers
Engaged with a specialized Forensic IT firm and Cyber Counsel to investigate and remediate the situation
Notified the FBI’s Internet Crime Complaint Center (IC3) and the Department of Defense Cyber Crime Center (DC3)
Worked with an incident response service to negotiate with the threat actors to prevent the release of any information
Engaged an IT Security firm to assist us in restoring our servers and improving our IT Security posture going forward
Reviewing our IT policies and procedures to ensure all security measures are in place to improve the security of our information network and related systems and to prevent such an incident from occurring again
Continuing to work with the FBI to assist in its investigation and have updated our IC3 and DC3 reports
Providing access to Single Bureau Credit Monitoring/Single Bureau Credit Report/Single Bureau Credit Score services at no charge for twelve (12) months
Providing proactive fraud assistance through Cyberscout through Identity Force
Changes made: Improving our IT Security posture going forward
Reviewing our IT policies and procedures to ensure all security measures are in place to improve the security of our information network and related systems and to prevent such an incident from occurring again
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 10 weeks(67 days from discovery to filing)
Compliance flags: Leak >90d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Indiana State AGMar 26 · first

Maine State AG+53d

Massachusetts State AG+54d

Nebraska State AG+61d

California State AG+62d · this page

Pattern: first filing Mar 26 (IN), last May 27 (CA) — a 62-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-623996
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 27, 2026
Raw hash: 2e163bca235bec3eed97d0601cfa4a54ff57ccf1e7c8ec0dd37557e4471d2e7f

Linked disclosures

Ransomware claims (2)

Regulatory filings (4) · sorted by filing gap

Reporting entityAmpex Data Systems

Victim entityAmpex Data Systems

Incidentdiscovered Mar 21, 2026

Stated responseShut down our servers

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov