Ransomware Tracker by ExposureDrift
Dashboard / Victims / Coos Bay

Coos Bay was listed on 23 May 2023 by the royal ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). royal listed 29 organizations that month and 211 in total.

  • Listed 1275 days ago.
  • 392 organizations were listed by all groups in May 2023, see the month.
  • 14 in Government & Defense that month.
  • 30 in US that month.

Updated 2026-11-14 15:53 UTC. Data: public leak-site listings. How we work.

Coos Bay corporate emblem
Listed by royal Disclosed: 2023-05-23 14:57 UTC

Coos Bay

co.coos.or.us Government & Defense US

Threat Group Post & Evidence

Listed by
Royal 211 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.

The group's leak-site address is on paid plans

Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.

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.

Coos Bay is a city located in Coos County, Oregon, where the Coos River enters Coos Bay on the Pacific Ocean. 248GB of confidential documents, contracts, workers salaries, medical information, forensic examinations, insurance and tax information and much more. Everything flew away from this city government to our blog. Soon you will be able to catch something!

Amounts as written

  • 248GB

Kinds of data mentioned

  • Tax records

    “…workers salaries, medical information, forensic examinations, insurance and tax information and much more. Everything flew away from this city government to our blog. Soon…”

  • Payroll and salaries

    “248GB of confidential documents, contracts, workers salaries, medical information, forensic examinations, insurance and tax information and much more.…”

  • Medical or patient records

    “248GB of confidential documents, contracts, workers salaries, medical information, forensic examinations, insurance and tax information and much more. Everything…”

  • Contracts and legal files

    “248GB of confidential documents, contracts, workers salaries, medical information, forensic examinations, insurance and tax information…”

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 Coos Bay (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 Coos Bay 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 Coos Bay 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.
  • Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: payroll and salaries, tax records.
  • If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.

Within 30 days

  • Keep watching Coos Bay 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 Coos Bay

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: payroll and salaries.
  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: payroll and salaries.

Within 3 days

  • Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
  • 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: 248GB. 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. Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.

Within 30 days

  • Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
  • Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
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 co.coos.or.us
Industry Vertical Government & Defense
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

91/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 30/30 pts
Government, public safety and defense
2. Group tier 18/25 pts
Tier 2: a group with a large number of listings
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
62/100 • HIGH
Last Audited: 2026-11-14 19:39 UTC Passive Recon
Total Network Assets 3
1 hosts • 2 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 1
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (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 Mimecast Secure Gateway
DNS Authority Authoritative DNS (us)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by royal

All →
Braintree Public Schools
Education 2023-07-19 14:46 UTC
Tachi-S Engineering USA
Manufacturing 2023-06-11 11:03 UTC
PENNCREST School District
Education 2023-06-09 11:58 UTC
Groupe Sovitrat Interim and Recrutement
Professional Services 2023-05-26 13:03 UTC
BM Precision
Manufacturing 2023-05-26 13:03 UTC
DirectViz Solutions
Technology 2023-05-26 13:02 UTC