HackingFinancial ServicesFinanceStolen CredentialsSupply Chain (3P Vendor)Customer Data InvolvedFinancial accountFinancial credentialsLowContained

RBC Royal Bank

bd_8e9a4a1049020d19 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 5, 2018

Filed

Jan 26, 2018

To disclose

21 days

Affected

1state residents only

Linked

2 filings

Confidence

66%

Full breach record for RBC Royal Bank →

RBC Royal Bank notified the NH Attorney General of a data breach affecting its travel rewards platform operated by third-party vendor Travelocity. Unauthorized access occurred between Oct 3 and Dec 22, 2017, exposing payment card numbers and CVVs. One NH resident was affected. RBC and Travelocity notified individuals on Jan 26, 2018, offering credit monitoring and enhanced fraud protection.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 94 days

discovery → filing · 21 days

Oct 3, 2017

Begins

Jan 5, 2018

Discovered

Jan 26, 2018

Filed

vs. sector median

5 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

Massachusetts State AGbd_fb7166bd6b0fb7272018-01-31 · +5dVerified

Name: RBC Royal Bank
norm: rbc royal bank

Name: RBC Royal Bank
norm: rbc royal bank
Industry: Financial Servicesllm

Discovered: Jan 5, 2018
Breach occurred: Oct 3, 2017 – Dec 22, 2017
Undetected for: 94 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 26, 2018
Affected individuals: 1state-resident count only
Data types: Financial accountFinancial credentials
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Notified New Hampshire Office of the Attorney General
Third party: via Travelocity
Initial access: supply_chain

During the incident: Notified law enforcement
Implemented enhanced fraud monitoring
Offered complimentary credit monitoring
Established a call center to provide updated information
Changes made: Blocking attacker access to the affected environment
Remediating impacted systems and accounts
Implementing additional measures to enhance the general security of this environment
Improving visibility of potentially unauthorized activity within the environment
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 21 days(21 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 ↗

New Hampshire State AGJan 26 · first · this page

Massachusetts State AG+5d

Pattern: first filing Jan 26 (NH), last Jan 31 (MA) — a 5-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://mm.nh.gov/files/uploads/doj/remote-docs/rbc-royal-bank-20180126.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 26, 2018
Raw hash: 5558ba605f21204a8b68caead00e1864f259ad34a7a0c5dcb9bb1592f3827ac5

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityRBC Royal Bank

Victim entityRBC Royal Bank

Incidentdiscovered Jan 5, 2018

Stated responseNotified law enforcement

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov