Social EngineeringTechnologyInformationPhishingStolen CredentialsBECMulti-Stage ChainEmployee Data InvolvedTargetedIdentity (basic)Government IDFinancial accountEmploymentHighContained

Gannett Company, Inc.

bd_b7d86566afd376bf · schema v1 · pii pii-v1

Severity

High

Discovered

Mar 30, 2017

Filed

Apr 28, 2017

To disclose

29 days

Affected · nationwide

18,1003 in this filing

Linked

4 filings

Confidence

65%

Full breach record for Gannett Company, Inc. →3 incidents on file

Gannett Company, Inc. notified the NH AG of a phishing attack on March 30, 2017, compromising HR Office 365 credentials. Perpetrators sent further phishing emails and attempted a fraudulent wire transfer (unsuccessful). 18,100 individuals affected, including 3 NH residents. Data potentially exposed: names, SSNs, DOB, bank/routing numbers, salary info. Gannett locked accounts, conducted forensic investigation, notified FBI, and provided 12 months of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 29 days

Mar 30, 2017

Discovered

Apr 28, 2017

Filed

vs. sector median

15 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

Montana State AGbd_2f5e4908de2fddea2017-04-28Candidate
Massachusetts State AGbd_61e7bc23c2170e6b2017-04-28Verified
California State AGbd_7f12b327f14904e72017-04-28Verified

Name: Gannett Company, Inc.
norm: gannett

Name: Gannett Company, Inc.
norm: gannett
Industry: Technologyllm

Discovered: Mar 30, 2017
Materiality determined: —
Notification sent: Apr 28, 2017
Affected individuals: 18,100state + nationwide
Data types: Identity (basic)Government IDFinancial accountEmployment
Data elements: Social Security numberDate of birth
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid AccountsT1114 Email Collection
Threat actor: ExternalFinancial
Regulator citations: Reported the incident to the Federal Bureau of Investigation
Initial access: phishing_link

During the incident: Locked down the affected accounts
Alerted other Gannett employees about the phishing email
Disabled and isolated the impacted accounts
Changed the credentials for each impacted employee
Conducted a forensic investigation
Reported the incident to the Federal Bureau of Investigation
Changes made: Providing regular reminders and training for employees on how to spot and avoid being victimized by phishing emails
Taken security measures to strengthen our network against similar incidents in the future
Providing one year of credit monitoring and identity theft protection services to potentially affected individuals through AllClear ID
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Montana State AGApr 28 · first

Massachusetts State AGApr 28 · first

California State AGApr 28 · first

New Hampshire State AGApr 28 · first · this page

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://mm.nh.gov/files/uploads/doj/remote-docs/gannett-20170428.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 28, 2017
Raw hash: c28296ba81a1d0d7f20921cf2e9c93c704452f457dbee448f08b151e0a4c7c25

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityGannett Company, Inc.

Victim entityGannett Company, Inc.

Incidentdiscovered Mar 30, 2017

Stated responseLocked down the affected accounts

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov