UnknownHigh

Jambav

bd_99023fc861bdb767 · schema v1 · pii pii-v1

Jambav Inc reported a data breach to the Oregon Attorney General. The breach was reported on 2019-12-17. The breach occurred during 11/11/2019. The breach was discovered on 11/11/2019. 6,100,000 individuals were affected. Notice was sent on 12/16/2019.

Oregon clock✓ OR AG ≤45d5 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

bd_eb98c9ae707ab162California State AGfiled 2019-12-19(2d gap)Candidate
bd_d7544e14d61d83d6Montana State AGfiled 2019-12-22(5d gap)Verified
bd_aea6f12827799fb7South Carolina State AGfiled 2019-12-23(6d gap)Verified
bd_863c7a6b7b60266eCalifornia State AGfiled 2020-01-10(24d gap)Verified

Source provenance

Source URL: https://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Dec 17, 2019
Raw hash: 0131187ff305728bc076307af649553b378bedf8bcea76041bd06527a5a67646

Reporting entity

Name: Jambav
norm: jambav
Domain: jambav.com

Victim entity

Name: Jambav
norm: jambav
Domain: jambav.com

Incident

Discovered: Nov 11, 2019
Materiality determined: —
Notification sent: Dec 16, 2019
Affected individuals: 6,100,000
Data types: —
Attack vector: Unknown
Threat actor: External

Compliance

Time to disclose: 5 weeks(36 days from discovery to filing)
Compliance flags: OR AG ≤45d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Extraction provenance

Status: No extraction artifact recorded for this disclosure.