Ransomware Tracker by ExposureDrift
Dashboard / Victims / HIZE Aero

HIZE Aero was listed on 09 June 2026 by the ULose ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). ULose listed 5 organizations that month and 8 in total.

  • Listed 162 days ago.
  • 708 organizations were listed by all groups in June 2026, see the month.
  • 118 in Manufacturing that month.
  • 12 in KR that month.

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

HIZE Aero corporate emblem
Listed by ULose Disclosed: 2026-06-09 00:00 UTC

HIZE Aero

hizeaero.com Manufacturing KR

Threat Group Post & Evidence

Listed by
ULose 8 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.

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.

We have all PDM Server`s data of HIZEAERO Company, partner Boeing. 1TB country: South Korea status: private

Amounts as written

  • 1TB

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.

Status shown by the group: private

This is the group's label when we last recorded it; the group can change it at any time, for example from countdown to published.

If you work with HIZE Aero (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 HIZE Aero 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 HIZE Aero 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 HIZE Aero 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 HIZE Aero

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: 1TB. Treat group figures as unverified.
  • Check regulatory and stakeholder notification duties South Korea: PIPA requires notifying affected people and, above thresholds, the regulator, promptly (generally within 72 hours). This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: South Korea.
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 hizeaero.com
Industry Vertical Manufacturing
Country KR
Enrichment Status ENRICHED

Listing severity score (heuristic)

69/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 20/30 pts
Industrial manufacturing
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
65/100 • HIGH
Last Audited: 2026-11-14 16:33 UTC Passive Recon
Total Network Assets 2
1 hosts • 1 unique IPs
0 cloud-hosted • 0 SaaS
Subdomain Assets 1
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 0 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade B (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 Custom Mail Gateway (com)
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by ULose

All →
zzq-test
Unknown 2026-10-27 01:08 UTC
probe-011637cabbf94076
Unknown 2026-10-27 01:08 UTC
www.newyjh.com
Unknown 2026-09-30 07:51 UTC
HanDok
Healthcare 2026-06-09 00:00 UTC
MSICapital
Financial Services 2026-06-09 00:00 UTC
NRCapital
Financial Services 2026-06-09 00:00 UTC