Ransomware Tracker by ExposureDrift
Dashboard / Victims / National Association for Stock Car Auto Racing

National Association for Stock Car Auto Racing was listed on 08 April 2025 by the medusa ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). medusa listed 14 organizations that month and 513 in total.

  • Listed 590 days ago.
  • 536 organizations were listed by all groups in April 2025, see the month.
  • 20 in Hospitality that month.
  • 228 in US that month.

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

National Association for Stock Car Auto Racing corporate emblem
Listed by medusa Disclosed: 2025-04-13 20:13 UTC

National Association for Stock Car Auto Racing

nascar.com Hospitality US

Threat Group Post & Evidence

Listed by
Medusa 513 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.

National Association for Stock Car Auto Racing (NASCAR) is the sanctioning body for the No. 1 form of motorsports in the United States and owner of 16 of the nation's major motorsports entertainment facilities. NASCAR corporate office is located in 1 Daytona Blvd, Daytona Beach, Florida, 32114, United States and has 8,734 employees. The total amount of data leakage is 1038.70 GB

Amounts as written

  • 8,734 employees
  • 1038.70 GB

Plain-English summary AI-written

The group says it holds 1038.70 GB of data related to NASCAR.

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 National Association for Stock Car Auto Racing (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 National Association for Stock Car Auto Racing 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 National Association for Stock Car Auto Racing 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.

Within 30 days

  • Keep watching National Association for Stock Car Auto Racing 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 National Association for Stock Car Auto Racing

Within 3 days

  • Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
  • 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: 8,734 employees, 1038.70 GB. 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 5 critical panel(s) reachable from the internet.
  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
  • 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 nascar.com
Industry Vertical Hospitality
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
100/100 • CRITICAL
Last Audited: 2026-11-14 17:55 UTC Passive Recon
Total Network Assets 40
13 hosts • 27 unique IPs
3 cloud-hosted • 5 SaaS
Subdomain Assets 13
Critical Panels 5 (VPN/Admin/SSO)
Non-Prod / UAT 1 Staging/Dev
SaaS Ecosystem 5 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 Amazon Route 53
Edge CDN / Shield AWS CloudFront / Edge
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by medusa

All →
Balloons Everywhere
Retail & E-Commerce 2026-02-14 11:27 UTC
South Hays Fire Department
Government & Defense 2026-02-14 11:27 UTC
Comune di Battipaglia
Government & Defense 2026-02-14 11:27 UTC
Grandview Family Medicine
Healthcare 2026-02-14 11:27 UTC
MESA Products
Manufacturing 2026-02-14 11:26 UTC
Resource Corporation of America
Healthcare 2026-01-04 19:22 UTC