Ransomware Tracker by ExposureDrift
Dashboard / Victims / Oahu Transit Services

Oahu Transit Services was listed on 15 June 2024 by the dragonforce ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). dragonforce listed 7 organizations that month and 666 in total.

  • Listed 887 days ago.
  • 396 organizations were listed by all groups in June 2024, see the month.
  • 33 in Transportation that month.
  • 168 in US that month.

Updated 2026-11-19 06:30 UTC. Data: public leak-site listings. How we work.

Oahu Transit Services corporate emblem
Listed by dragonforce Disclosed: 2024-06-15 14:47 UTC

Oahu Transit Services

thebus.org Transportation US

Threat Group Post & Evidence

Listed by
Dragonforce 666 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

Founded in 1991, The Oahu Transit Services Group (OTS) owns and operates a fleet of buses for Honolulu, Hawaii, referred to collectively as TheBus.They recently began a new commuter ferry service, called The Boat. Another major leak, about 800,000 records that include personal data of customers, you can get acquainted with the columns of the database, [RecNum] [RefNo] [Reason] [IDType] [IDNumber] [PassType] [Fee] [FName] [LName] [Addr1] [Addr2] [City] [State] [ZipCode] [Phone] [SSN] [Sex] [DOB] [Resident_Status] [ExpDate] [NewExpDate] [ADAFlag] [PCAFlag] [Desc1] [Desc2] [Dept] [Comments] [Duration] [Months] [Login] [EXCLUDE] [LOCATION] [IDTYPE_CODE] [REASON_CODE] [ModDate] [ModBy] [SAFLAG] [BUSEXPDATE] [IDTYPE_CODE2] [DISABILITY_STATUS] [NEWBUSEXPDATE] we give this company 7 days to get in touch, otherwise their customers will suffer due to their negligence.

Amounts as written

  • 800,000 records

Kinds of data mentioned

  • Identity documents

    “…[Fee] [FName] [LName] [Addr1] [Addr2] [City] [State] [ZipCode] [Phone] [SSN] [Sex] [DOB] [Resident_Status] [ExpDate] [NewExpDate] [ADAFlag] [PCAFlag] [Desc1] [Desc2]…”

  • Customer or client data

    “Another major leak, about 800,000 records that include personal data of customers, you can get acquainted with the columns of the database, [RecNum] [RefNo] [Reason] [IDType]…”

  • Databases and backups

    “…personal data of customers, you can get acquainted with the columns of the database, [RecNum] [RefNo] [Reason] [IDType] [IDNumber] [PassType] [Fee] [FName] [LName] [Addr1] [Addr2]…”

Plain-English summary AI-written

The group says it has about 800,000 records containing personal customer data, including contact details, identification information, and other account records.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with Oahu Transit Services (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask Oahu Transit Services directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what Oahu Transit Services can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, identity documents.
  • Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.

Within 30 days

  • Keep watching Oahu Transit Services A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Oahu Transit Services

First 24 hours

  • Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: identity documents, customer or client data.

Within 3 days

  • Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: identity documents.
  • Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 800,000 records. Treat group figures as unverified.
  • Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain thebus.org
Industry Vertical Transportation
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

88/100 • CRITICAL

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Transportation and logistics
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
70/100 • HIGH
Last Audited: 2026-11-14 18:53 UTC Passive Recon
Total Network Assets 4
2 hosts • 2 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 2
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 1 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade C (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Custom Mail Gateway (com)
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by dragonforce

All →
lyserp.com
Technology 2026-10-30 10:43 UTC
Zhito Technology
Technology 2026-10-27 00:14 UTC
Inside Passage Electric Cooperative, Inc
Energy & Utilities 2026-10-26 06:59 UTC
oakgrovetech
Technology 2026-10-17 21:04 UTC
Lane Equipment
Manufacturing 2026-10-14 00:30 UTC
Canadian Mennonite University (CMU)
Education 2026-10-12 11:03 UTC