Ransomware Tracker by ExposureDrift
Dashboard / Victims / URG OEM

URG OEM was listed on 17 May 2026 by the nova ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). nova listed 25 organizations that month and 177 in total.

  • Listed 186 days ago.
  • 783 organizations were listed by all groups in May 2026, see the month.
  • 135 in Manufacturing that month.
  • 4 in KR that month.

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

URG OEM corporate emblem
Listed by nova Disclosed: 2026-05-17 12:23 UTC

URG OEM

urg.co.kr Manufacturing KR

Threat Group Post & Evidence

Listed by
Nova 177 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.

urg.co.kr - URG was founded with a sincere desire to provide solutions for customers facing skin concerns. Starting in 1990 with the launch of Shangpree Spa, the company not only delivered high-quality products to customers but also set a new standard for luxury service in the skincare industry—establishing itself as a leading premium spa brand. Building on over 30 years of tradition and expertise, URG has since launched a variety of skincare brands, gaining recognition both domestically and internationally.

Plain-English summary AI-written

The group says nothing about holding data; the text describes URG and its skincare brands.

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 URG OEM (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 URG OEM 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 URG OEM 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 URG OEM 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 URG OEM

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 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 urg.co.kr
Industry Vertical Manufacturing
Country KR
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
61/100 • HIGH
Last Audited: 2026-11-14 16:38 UTC Passive Recon
Total Network Assets 7
4 hosts • 3 unique IPs
0 cloud-hosted • 1 SaaS
Subdomain Assets 4
Critical Panels 0 (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 Custom Mail Gateway (kr)
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 nova

All →
SistNet
Technology 2026-07-25 09:27 UTC
Digital Edge
Technology 2026-07-24 01:30 UTC
VNSO
Technology 2026-07-22 19:30 UTC
Marpatech
Technology 2026-07-22 00:15 UTC
Canal 9 Litoral
Technology 2026-07-22 00:14 UTC