GLOBAL CROSSING AIRLINES GROUP INC.
One linked filing — more sources may join as they report · filed May 9, 2025. View entity profile → Other incidents for this victim →
incident inc_ff7ec21b5c3046ff · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Not recorded for this incident
Discovery variance · Leak precedence · Filing span — no leak-site claim in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAY 9SEC 8-KSEC 8-K noticeonly filing · no count statedday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- —
- Discovered
- May 5, 2025 SEC 8-K
- Attack vector
- Unauthorized Access SEC 8-K
- Response
- Activated its incident response protocols · Engaged third-party cybersecurity experts to assist with containment and mitigation activities and to investigate the nature and scope of the incident · Took actions to contain and isolate the affected servers and prevent further intrusion SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
No regulator filing linked yet.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.