Ransomware Tracker by ExposureDrift
Dashboard / Victims / El Cajon, CA

El Cajon, CA was listed on 04 November 2026 by the rhysida ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). rhysida listed 15 organizations that month and 328 in total.

  • Listed 15 days ago.
  • 983 organizations were listed by all groups in November 2026, see the month.
  • 163 in Healthcare that month.
  • 431 in US that month.

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

El Cajon, CA corporate emblem
Listed by rhysida Disclosed: 2026-11-04 16:55 UTC

El Cajon, CA

Healthcare US

Threat Group Post & Evidence

Listed by
Rhysida 328 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.

El Cajon, CA LOT DESCRIPTION (brief) - U.S. municipal dump: police + 911 + production SQLWhat is for sale. Municipal government of a U.S. city (California): police department, 911 dispatch center (joint authority), fire/EMS, all city services, ~1,100+ employees. ~7.8M files / ~7.8 TB. Content current through late September 2026 - SQL backups, payroll runs and 911 logs up to the final days. Live dump, not an archive. Full snapshot: entire file server, restricted police shares, the 911 center, production databases, workstation backups and terminal-server profiles.Contents. Employee home profiles �195 (~800 GB) � department shares - HR/city attorney/finance/council (~1.3 TB) � public works + utility billing for ~250K accounts (~1.3 TB) � citywide share with W-2s for all employees (~2.4 TB) � restricted police archive (~1.7 TB) � 911 center: ~6.3M call recordings over ~3 years + caller phone…
Show the full post (3782 characters)

El Cajon, CA LOT DESCRIPTION (brief) - U.S. municipal dump: police + 911 + production SQLWhat is for sale. Municipal government of a U.S. city (California): police department, 911 dispatch center (joint authority), fire/EMS, all city services, ~1,100+ employees. ~7.8M files / ~7.8 TB. Content current through late September 2026 - SQL backups, payroll runs and 911 logs up to the final days. Live dump, not an archive. Full snapshot: entire file server, restricted police shares, the 911 center, production databases, workstation backups and terminal-server profiles.Contents. Employee home profiles �195 (~800 GB) � department shares - HR/city attorney/finance/council (~1.3 TB) � public works + utility billing for ~250K accounts (~1.3 TB) � citywide share with W-2s for all employees (~2.4 TB) � restricted police archive (~1.7 TB) � 911 center: ~6.3M call recordings over ~3 years + caller phone/address/GPS metadata (~380 GB) � SQL backups (~440 GB: dispatch CAD 17+ GB, evidence vault, crime lab, RMS, access control, MFA server).Credentials and access (sells first). Bank ACH private key + passphrase, state treasury pool PINs, corporate cards with PAN+CVV+PIN � root/enable on the network core (incl. traffic lights) � government accounts (FBI, DEA, state DOJ, CJIS, LiveScan) + 111 officer passcodes to the narcotics system � DMV certificate + password � MFA server dump (TOTP secrets, hardware-token seeds, VPN) � password templates/defaults, vendor ERP backdoor � cameras on public IPs � 13� .pfx signing certs, OAuth secrets, door/access control, map of 401 cameras, gate codes.Personal data. W-2s for all ~1,100 employees (SSN+salary+address) � applicant SSN sets � thousands of EMS patient records with SSN � 337 DMV records � credit dossiers with IRS transcripts � home addresses of the mayor and council � 911 caller GPS metadata (above) � production CAD: ~89K incidents, ~3.9K arrests, 941 warrants, 8.3K SSNs.Police kompromat. Internal Affairs master tracker (1,016 rows / ~10 years, named: use of force �239, pursuits �172, claims �223) + 25-year legacy archive (force �998, complaints �2,612) � DA 'untruthful officers' list � registry of 691 destroyed discipline files + litigation hold list � officer DUI/DV (arrests; victim of an untaken DV call later killed) � fresh 2025�26 cases (negligent discharge + lies � 58-min discipline audio included; fabricated pursuit; theft during arrest) � undercover unit rosters, named + informants (names/DLs/phones) � cold cases (suspects/witnesses) � SWAT callout sheets with personal cell phones � 81 real warrant templates with witnesses � CI/surveillance playbooks � 911 data fed to federal immigration agencies + active court fight with the state AG over surveillance data sharing � county election-office correspondence, PRA packages, protest recordings with caller numbers.Finance/mail. ~77 GB of email archives (HR investigations ~37 GB) � 13 years of payroll � grants � 4 layoff waves � asset forfeiture case files � GIS/document-system credentials.Buyers. Extortion crews (headline-ready topics already in the news cycle) � fraud (W-2/SSN/medical) � IABs (live access to a city 911/CAD is a rare lot) � plaintiffs' attorneys (new suits, case reviews) � media (ready stories) � intelligence services (undercover rosters, informants, LE-systems access) � criminals (sources and witnesses).Deal formats. Full lot exclusive � credentials package (<1 GB, samples before deal) � PII packs by class � police package for media/negotiation � first-publication rights. Freshness: A=2026 (live data), B=2024�25 (active cases), C=25+ year legacy (pattern proof).Limitations. Some containers are encrypted (passwords not recovered), video archives unreviewed; the data contains live police sources - handle with care. More

Amounts as written

  • 1,100+ employees
  • 7.8M files
  • 7.8 TB
  • 800 GB
  • 1.3 TB
  • 250K accounts
  • 2.4 TB
  • 1.7 TB

Kinds of data mentioned

  • Tax records

    “…EMS patient records with SSN � 337 DMV records � credit dossiers with IRS transcripts � home addresses of the mayor and council � 911 caller GPS metadata (above) �…”

  • Payroll and salaries

    “…/ ~7.8 TB. Content current through late September 2026 - SQL backups, payroll runs and 911 logs up to the final days. Live dump, not an archive. Full snapshot: entire file…”

  • Identity documents

    “…401 cameras, gate codes.Personal data. W-2s for all ~1,100 employees (SSN+salary+address) � applicant SSN sets � thousands of EMS patient records with SSN � 337 DMV…”

  • Passwords and credentials

    “…CAD 17+ GB, evidence vault, crime lab, RMS, access control, MFA server).Credentials and access (sells first). Bank ACH private key + passphrase, state treasury pool PINs, corporate…”

  • Email and communications

    “…packages, protest recordings with caller numbers.Finance/mail. ~77 GB of email archives (HR investigations ~37 GB) � 13 years of payroll � grants � 4 layoff waves � asset…”

  • Medical or patient records

    “…employees (SSN+salary+address) � applicant SSN sets � thousands of EMS patient records with SSN � 337 DMV records � credit dossiers with IRS transcripts � home addresses…”

  • Employee and HR records

    “…dispatch center (joint authority), fire/EMS, all city services, ~1,100+ employees. ~7.8M files / ~7.8 TB. Content current through late September 2026 - SQL backups, payroll…”

  • Contracts and legal files

    “…'untruthful officers' list � registry of 691 destroyed discipline files + litigation hold list � officer DUI/DV (arrests; victim of an untaken DV call later killed) � fresh 2025�26…”

  • Source code and designs

    “…phone/address/GPS metadata (~380 GB) � SQL backups (~440 GB: dispatch CAD 17+ GB, evidence vault, crime lab, RMS, access control, MFA server).Credentials and access…”

  • Databases and backups

    “municipal dump: police + 911 + production SQLWhat is for sale. Municipal government of a U.S. city (California):…”

Plain-English summary AI-written

The group says it holds a live dump of a California city’s systems, including police and 911 records, SQL backups, payroll runs, employee profiles, department files, production databases, workstation backups and terminal-server profiles.

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 El Cajon, CA (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 El Cajon, CA 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 El Cajon, CA 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: email and communications, passwords and credentials, identity documents, employee and hr records.
  • 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.
  • 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: source code and designs, databases and backups.
  • 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 El Cajon, CA 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 El Cajon, CA

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: passwords and credentials, identity documents, email and communications, 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.
  • 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: employee and hr records, identity documents.
  • Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
  • 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.
  • Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • 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: 1,100+ employees, 7.8M files, 7.8 TB. 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.
  • Check the ways rhysida is reported to get in Check these first; they are how the group is reported to work in general.
    • Actors typically log in to VPN access points with stolen valid credentials, which the advisory ties to organizations without multi-factor authentication. (update of Apr 2025)
    Source: #StopRansomware: Rhysida Ransomware (AA23-319A) Why: From the public advisory below. It describes the group, not how El Cajon, CA was entered.

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.
  • Check shared suppliers and software List the suppliers and software you share with other Healthcare organizations and ask them whether they were affected. Why: rhysida listed 7 other Healthcare organization(s) in the last 90 days.
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 Not stated
Industry Vertical Healthcare
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
Healthcare and life sciences
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

No scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.

Launch Attack Surface Recon →
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 Not Disclosed / Unresolved
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Missing
DMARC Policy Missing
Public DNS records only • no port scanning

More Claims by rhysida

All →
Rudolph F. Jass, Jr., PLLC
Professional Services 2026-11-19 22:18 UTC
Rober & Phillips
Financial Services 2026-11-19 14:22 UTC
Smith & Green, Attorneys at Law PLLC
Legal Services 2026-11-19 06:44 UTC
WILLIAMS, BRODERSEN, PRITCHETT & RUIZ LLP
Professional Services 2026-11-18 14:22 UTC
SteelTech Inc.
Manufacturing 2026-11-18 10:22 UTC
Van der Spek Vianen B.V.
Manufacturing 2026-11-17 16:09 UTC