HackingTechnologyInformationDelayed DiscoveryIdentity (basic)PIIMediumActive

Capp, Inc.

bd_00caa5107aa9d015 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 19, 2025

Filed

Mar 4, 2025

To disclose

13 days

Affected

33,538state residents only

Confidence

68%

Full breach record for Capp, Inc. →

Capp, Inc. d/b/a Airbuds notified Washington AG of a cyberattack discovered on Feb 19, 2025, potentially affecting 33,538 Washington residents. Access may have occurred prior to Oct 22, 2024. Exposed data includes usernames, names, phone numbers, and birth dates. Investigation ongoing.

J jump to incidentP pin to compareR raw source

Washington clock✓ WA AG ≤30d13 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 120 days

discovery → filing · 13 days

Oct 22, 2024

Begins

Feb 19, 2025

Discovered

Mar 4, 2025

Filed

vs. sector median

17 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed33,538 affectedView incident

Name: Capp, Inc.
norm: capp
Domain: airbuds.fm

Name: Capp, Inc.
norm: capp
Domain: airbuds.fm
Also named: Capp, Inc.dba oflegal entity
Airbudsdba oftrade name
Industry: Technologyllm

Discovered: Feb 19, 2025
Breach occurred: Oct 22, 2024
Undetected for: 120 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 33,538state-resident count only
Data types: Identity (basic)PII
Data elements: NameDate of birth
WA-stated cause: Cyberattack
WA-stated duration: lifecycle Unknowndexposure Unknownd
WA-stated discovery: Found after the fact
Attack vector: Unknown
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External
Regulator citations: reported this incident to law enforcement and other relevant authorities
Initial access: valid_credentials

During the incident: Launched an investigation with the assistance of security experts
Reported this incident to law enforcement and other relevant authorities
Changes made: Contain any exposure
Apply further protections to your information
Working closely with security experts to further enhance our defenses against future threats
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 days(13 days from discovery to filing)
Compliance flags: WA AG ≤30d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

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/BreachA32592.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 4, 2025
Raw hash: bb58a33e4cdc55bf9c315927be59ab5325bf890007d40468f29ebde16edabc3a

Reporting entityCapp, Inc.

Victim entityCapp, Inc.

Incidentdiscovered Feb 19, 2025

Stated responseLaunched an investigation with the assistance of security experts

ComplianceWA AG ≤30d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com