MalwareEducationEducationRansomwareData ExfiltratedData EncryptedCustomer Data InvolvedSupply Chain (3P Vendor)Identity (basic)Government IDPIIMediumContained

Colorado Technical University

bd_df747b9fff4032e8 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Nov 12, 2024

To disclose

—

Affected

567state residents only

Linked

2 filings

Confidence

70%

Full breach record for Colorado Technical University →

Colorado Technical University reported a ransomware incident involving its debt collection vendor, FBCS. Unauthorized access occurred Feb 14-26, 2024, discovered Feb 26, 2024. PII of current/former students was exfiltrated. 567 Washington residents affected. Credit monitoring offered.

J jump to incidentP pin to compareR raw source

Incident timeline

Feb 14, 2024

Begins

Nov 12, 2024

Filed

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Oregon State AGbd_ec408b4349760a6a2024-12-03 · +21dVerified

Name: Colorado Technical University
norm: colorado technical university

Name: Colorado Technical University
norm: colorado technical university
Industry: Educationllm

Discovered: —
Breach occurred: Feb 14, 2024 – Feb 26, 2024
Materiality determined: —
Notification sent: —
Affected individuals: 567state-resident count only
Data types: PIIIdentity (basic)
Data elements: NameSocial Security numberDriver's licence numberDate of birth
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 1-99dexposure 1-99d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial

During the incident: Took steps to secure the impacted environment
Launched an investigation with the assistance of third-party computer forensics specialists
Offering you access to complimentary credit monitoring and identity restoration services for 12/24 months through CyEx
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 · 2 filings · 2 states

View merged incident ↗

Washington State AGNov 12 · first · this page

Oregon State AG+21d

Pattern: first filing Nov 12 (WA), last Dec 3 (OR) — a 21-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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachA31347.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 12, 2024
Raw hash: a3a393bef026b3b723a1ee0716b2abe281c82b6cfd273d444af678ef2ffd5e3d

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityColorado Technical University

Victim entityColorado Technical University

IncidentRansomware

Stated responseTook steps to secure the impacted environment

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com