Social EngineeringOtherPhishingTargetedIdentity (basic)Government IDFinancialMediumActive

The Travel Corporation (TravelCorp)

bd_d39f32850f856223 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 26, 2018

Filed

Mar 9, 2018

To disclose

11 days

Affected

1state residents only

Linked

2 filings

Confidence

65%

Full breach record for The Travel Corporation (TravelCorp) →

The Travel Corporation notified employees of a phishing incident on Feb 26, 2018, where an attacker impersonated the CEO to obtain W2s and payroll data. Affected data included names, SSNs, and addresses of US employees. The company reported the incident to the FBI and local police.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 11 days

Feb 26, 2018

Begins

Feb 26, 2018

Discovered

Mar 9, 2018

Filed

vs. sector median

7 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

California State AGbd_99257e015d48a9432018-03-01 · +8dCandidate

Name: The Travel Corporation (TravelCorp)
norm: the travel corporation travelcorp
Domain: ttc.com

Name: The Travel Corporation (TravelCorp)
norm: the travel corporation travelcorp
Domain: ttc.com
Industry: Otherllm

Discovered: Feb 26, 2018
Breach occurred: Feb 26, 2018
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 27, 2018
Affected individuals: 1state-resident count only
Data types: Identity (basic)Government IDFinancial
Data elements: Social Security number
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Notified local police department (Anaheim)Notified Federal Bureau of Investigation (FBI)
Initial access: phishing_link

During the incident: Reporting this theft to our local police department (Anaheim) and to the Federal Bureau of Investigation (FBI)
In the process of notifying the three major credit reporting agencies
Actively researching credit monitoring services
Schedule a number of Q&A calls for staff
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

California State AGMar 1 · first

Montana State AG+8d · this page

Pattern: first filing Mar 1 (CA), last Mar 9 (MT) — a 8-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://dojmt.gov/wp-content/uploads/TravelCorp.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 9, 2018
Raw hash: 4743383d1d8233a17a3dfbc5ba377f7be5e630c47b6e2cf923f3c26dca39c957

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityThe Travel Corporation (TravelCorp)

Victim entityThe Travel Corporation (TravelCorp)

Incidentdiscovered Feb 26, 2018

Stated responseReporting this theft to our local police department (Anaheim) and to the Federal Bureau of Investigation (FBI)

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov