HackingTechnologyInformationVulnerability ExploitCustomer Data InvolvedData ExfiltratedIdentity (basic)Government IDMediumContained

National Public Data

bd_d0812cb0df624f1f · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Aug 17, 2024

To disclose

—

Affected

Not disclosed

Linked

5 filings

Confidence

65%

Full breach record for National Public Data →2 incidents on file

National Public Data reported a data security incident involving a third-party bad actor attempting to hack into data in late December 2023, with potential leaks in April and summer 2024. Affected data included names, email addresses, phone numbers, social security numbers, and mailing addresses. The company cooperated with law enforcement and implemented additional security measures.

J jump to incidentP pin to compareR raw source

Incident timeline

Dec 29, 2023

Begins

Aug 17, 2024

Filed

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Maine State AGbd_c1e9acb323a8323b2024-08-17Candidate
Wisconsin State AGbd_cf46d176243265892024-08-12 · +5dVerified
Delaware State AGbd_62daaa80f5351e9a2024-08-10 · +7dVerified
Indiana State AGbd_99a67ea02eeb8bf02024-08-10 · +7dVerified

Name: National Public Data
norm: national public data
Domain: nationalpublicdata.com

Name: National Public Data
norm: national public data
Domain: nationalpublicdata.com
Industry: Technologyllm

Discovered: —
Breach occurred: Dec 29, 2023 – Jul 31, 2024
Materiality determined: —
Notification sent: Aug 10, 2024
Affected individuals: Not disclosed
Data types: Identity (basic)Government ID
Data elements: Social Security number
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Cooperated with law enforcement and governmental investigators
Initial access: exploit_public_facing

During the incident: Cooperated with law enforcement and governmental investigators
Conducted a review of the potentially affected records
Implemented additional security measures in efforts to prevent the reoccurrence of such a breach and to protect our systems
Changes made: Implemented additional security measures in efforts to prevent the reoccurrence of such a breach and to protect our systems
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Delaware State AGAug 10 · first

Indiana State AGAug 10 · first

Wisconsin State AG+2d

Maine State AG+7d

California State AG+7d · this page

Pattern: first filing Aug 10 (DE), last Aug 17 (CA) — a 7-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-590388
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 17, 2024
Raw hash: 914d82450dfa5f2957b27c4cdcc6b51f2d90c167b050f37c91a3fbd88918320f

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityNational Public Data

Victim entityNational Public Data

IncidentUnauthorized Access

Stated responseCooperated with law enforcement and governmental investigators

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov