norm: netgalley homeUSno LEI · no CIKMax severity: Low

Canonical registry

NetGalley Home

ent_8efe32b419848750efc99ca8

Compliance scorecard →🔔 Follow entity

Disclosures

1

State AG · 1 jurisdiction

Incidents

—

no linked incident in sample

Max affected reported

—

no filed count in sample

Leak-site claims

0

none in sample

Identity resolution

Canonical name: NetGalley Home
Normalized: netgalley home— dedupe via name-norm; Microsoft / MSFT collapse to one row
GLEIF LEI: No match
SEC EDGAR CIK: None — not an SEC registrant
Domain: netgalley.com

Disclosure history (1)newest first

🐻California State AGas victim2020-12-23
On December 21, 2020, NetGalley experienced a data security incident where a hacker accessed a backup file of the NetGalley database stored in Amazon Cloud. The breach occurred because a testing server was left unsecured, making credentials easily attainable. Exposed information included login names, passwords, first/last names, email addresses, countries, and optionally bios, mailing addresses, phone numbers, birthdays, company names, and Kindle email addresses. No financial information was involved. NetGalley re-secured testing sites, revised backup procedures, changed legacy passwords, added security features, and required password resets. The FBI was notified.