Ransomware Tracker by ExposureDrift
Dashboard / Victims / wexfordcounty.org

wexfordcounty.org was listed on 05 November 2024 by the embargo ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). embargo listed 5 organizations that month and 41 in total.

  • Listed 744 days ago.
  • 691 organizations were listed by all groups in November 2024, see the month.
  • 25 in Government & Defense that month.
  • 3 in JO that month.

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

wexfordcounty.org corporate emblem
Listed by embargo Disclosed: 2024-11-05 21:51 UTC

wexfordcounty.org

wexfordcounty.org Government & Defense JO

Threat Group Post & Evidence

Listed by
Embargo 41 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.

Located in Northern Lower Michigan, Wexford County boasts a population of approximately 35,000, with a combination of an industrial/recreational demographic base. - 1 TB Data Network Admins: Joe Porterfield ([email protected]) Jami Bigger ([email protected]) 231-779-9452 Passwords: ["August24!", "September24!", "October24!"] MSSP: Sophia Masotti-Jordan ([email protected]) 616-856-5678

Amounts as written

  • 1 TB

Kinds of data mentioned

Plain-English summary AI-written

The group says it holds Wexford County information, including network administrators’ contact details and passwords.

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 wexfordcounty.org (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 wexfordcounty.org 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 wexfordcounty.org 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: passwords and credentials.

Within 30 days

  • Keep watching wexfordcounty.org 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 wexfordcounty.org

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.

Within 3 days

  • 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 TB. Treat group figures as unverified.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
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 wexfordcounty.org
Industry Vertical Government & Defense
Country JO
Enrichment Status ENRICHED

Listing severity score (heuristic)

81/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 10/25 pts
Tier 3: all other groups
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
76/100 • CRITICAL
Last Audited: 2026-11-14 18:36 UTC Passive Recon
Total Network Assets 13
6 hosts • 7 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 6
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 1 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 Microsoft 365 / Exchange Online
DNS Authority Cloudflare Managed DNS
Edge CDN / Shield Cloudflare CDN / DDoS Shield
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by embargo

All →
www.maytrucking.com
Transportation 2026-06-30 04:54 UTC
Auburn Electrical Construction Company
Energy & Utilities 2026-06-09 18:21 UTC
https://www.lagoonpark.com
Hospitality 2026-03-31 12:15 UTC
ludlums.com
Technology 2026-03-26 20:16 UTC
westport.com
Technology 2026-03-14 20:00 UTC