Ransomware Tracker by ExposureDrift
Dashboard / Victims / Hunter Dickinson Inc.

Hunter Dickinson Inc. was listed on 19 September 2024 by the bianlian ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). bianlian listed 13 organizations that month and 544 in total.

  • Listed 791 days ago.
  • 403 organizations were listed by all groups in September 2024, see the month.
  • 8 in Energy & Utilities that month.
  • 29 in CA that month.

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

Hunter Dickinson Inc. corporate emblem
Listed by bianlian Disclosed: 2024-09-19 15:02 UTC

Hunter Dickinson Inc.

Energy & Utilities CA

Threat Group Post & Evidence

Listed by
BianLian 544 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.

HDI is a diversified, global mining group with more than 25 years of mineral development success.

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 Hunter Dickinson (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 Hunter Dickinson 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 Hunter Dickinson 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 Hunter Dickinson 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 Hunter Dickinson

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.
  • Check regulatory and stakeholder notification duties Canada: PIPEDA requires reporting breaches that pose a real risk of significant harm, as soon as feasible. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Canada.
  • Check the ways bianlian is reported to get in Check these first; they are how the group is reported to work in general.
    • Typical access is through compromised RDP credentials, often bought from initial access brokers, or phishing; data is exfiltrated with FTP, Rclone or Mega. (update of 20 Nov 2024)
    Source: #StopRansomware: BianLian Ransomware Group (AA23-136A) Why: From the public advisory below. It describes the group, not how Hunter Dickinson was entered.
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 Energy & Utilities
Country CA
Enrichment Status ENRICHED

Listing severity score (heuristic)

72/100 • ELEVATED

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
Energy and utilities
2. Group tier 18/25 pts
Tier 2: a group with a large number of listings
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 bianlian

All →
CMC Technology Group
Technology 2025-03-31 15:58 UTC
Meridian Senior
Healthcare 2025-03-31 15:57 UTC
Saunders and Saunders
Professional Services 2025-03-31 15:56 UTC
Sonrisas Dental Health
Healthcare 2025-03-31 15:55 UTC
Goshen Medical Center
Healthcare 2025-03-22 22:24 UTC
Allworx
Technology 2025-03-07 23:47 UTC