MalwareHealthcareHealthcareRansomwareData EncryptedPHIHealth (basic)Identity (basic)Government IDMediumContained

Airway Oxygen, Inc.

bd_17de9b603eb33b94 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 18, 2017

Filed

Jun 6, 2017

To disclose

7 weeks

Affected

78state residents only

Linked

6 filings

Confidence

66%

Full breach record for Airway Oxygen, Inc. →

Airway Oxygen, Inc. notified Washington AG of a ransomware attack on April 18, 2017, affecting 78 Washington residents. The attack encrypted data but there was no indication PHI was accessed or acquired. Affected data included names, addresses, SSNs, diagnoses, and insurance info. The company engaged forensic investigators and notified the FBI.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 7 weeks / 49 days

Apr 18, 2017

Begins

Apr 18, 2017

Discovered

Jun 6, 2017

Filed

vs. sector median

4 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Montana State AGbd_386bb6623dfb67752017-06-06Candidate
New Hampshire State AGbd_49cc002e9eab484b2017-06-02 · +4dVerified
New Hampshire State AGbd_ffaed1b2280f27b82017-05-30 · +7dVerified
HHS OCRbd_cd17130fccdccf362017-06-16 · +10dVerified

Show 1 more filing ↓up to 10d gap

Oregon State AGbd_e743f63b3ec415602017-06-16 · +10dVerified

Name: Varnum LLP
norm: varnum

Name: Airway Oxygen, Inc.
norm: airway oxygen
Industry: Healthcarellm

Discovered: Apr 18, 2017
Breach occurred: Apr 18, 2017 – Apr 18, 2017
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 1, 2017
Affected individuals: 78state-resident count only
Data types: PHIHealth (basic)Identity (basic)Government ID
Data elements: Social Security numberDate of birthMedical information
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Notified Washington Attorney General Consumer Protection Divisionreported the incident to the FBI

During the incident: Scanning the entire internal system
Changing passwords for users, vendor accounts and applications
Conducting a firewall review
Updating and deploying security tools
Installing software to monitor and issue alerts as to suspicious firewall log activity
Reported the incident to the FBI
Hired a cyber-security firm to assist in conducting an investigation
Changes made: Identifying further actions to reduce the risk of this situation recurring
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 7 weeks(49 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

New Hampshire State AGMay 30 · first

New Hampshire State AG+3d

Montana State AG+7d

Washington State AG+7d · this page

HHS OCR+17d

Oregon State AG+17d

Pattern: first filing May 30 (NH), last Jun 16 (OR) — a 17-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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9711.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 6, 2017
Raw hash: 3fb84b481c6a8a5730562e3f59b0676d9509c73e35db0aa908da96619b9fc6b6

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityVarnum LLP

Victim entityAirway Oxygen, Inc.

Incidentdiscovered Apr 18, 2017

Stated responseScanning the entire internal system

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com