Ransomware Tracker by ExposureDrift
Dashboard / Victims / Rheem Global

Rheem Global was listed on 17 October 2026 by the Helix ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Helix listed 9 organizations that month and 20 in total.

  • Listed 33 days ago.
  • 1147 organizations were listed by all groups in October 2026, see the month.
  • 191 in Manufacturing that month.
  • 409 in US that month.

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

Rheem Global corporate emblem
Listed by Helix Disclosed: 2026-10-17 18:22 UTC

Rheem Global

Manufacturing US

Threat Group Post & Evidence

Listed by
Helix 20 listings in total

The listing states no data size and no ransom demand.

Dark Web Leak Proof Screenshot

Original Source (Safe Tor Stream)
Full Resolution
Capture of the group's own page about Rheem Global
© Ransomware Tracker by ExposureDrift • Watermarked copy of the group's own page. The unmodified capture is available on request.
Window Viewport (1280x962) | Capture of the group's own page | Zero Local Tooling Execution • Pure Text-Stream Ingestion

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.

Rheem Global customer records. Yearly revenue ~$6 billion. GoFile links and passwords unlock in 12 hours.

Kinds of data mentioned

  • Passwords and credentials

    “…Global customer records. Yearly revenue ~$6 billion. GoFile links and passwords unlock in 12 hours.”

  • Customer or client data

    “Rheem Global customer records. Yearly revenue ~$6 billion. GoFile links and passwords unlock in 12 hours.”

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 Rheem Global (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 Rheem Global 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 Rheem Global 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, passwords and credentials.

Within 30 days

  • Keep watching Rheem Global 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 Rheem Global

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, customer or client data.

Within 3 days

  • 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.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: Helix listed 6 other Manufacturing 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 Manufacturing
Country US
Enrichment Status ENRICHED

Listing severity score (heuristic)

50/100 • GUARDED

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
Industrial manufacturing
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 10/25 pts
Baseline: no size or sensitive 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.

More Claims by Helix

All →
Mnfhs
Unknown 2026-11-18 02:51 UTC
Veritiv
Manufacturing 2026-11-18 00:51 UTC
Sonoco
Manufacturing 2026-11-17 19:22 UTC
Westrock Coffee
Retail & E-Commerce 2026-10-21 17:52 UTC
Hypertherm
Manufacturing 2026-10-21 13:52 UTC
American Campus
Education 2026-10-19 02:23 UTC