Was Hamilton Park hit by ransomware?

Hamilton Park was listed by the pear ransomware operation (United States), and stolen data was published on the group's leak site. Darkfield tracks this disclosure with the original leak post, screenshot and group context.

Who is the pear ransomware group?

pear is a ransomware operator tracked by Darkfield. See the full operator dossier for its known victims, sectors targeted, IOCs and leak-site infrastructure.

What data was leaked in the Hamilton Park breach?

pear published data attributed to Hamilton Park. Darkfield captured the leak post and a screenshot of the listing.

Ransomware victim disclosure

← All victims

Hamilton Park Interiors

listed as Hamilton Park · Claimed by Pear · listed 11 months ago

11m

Age

since listed · data leaked

Status timeline

ListedAug 5, 2025
Data leakeddate unknown

At a glance

Group: Pear
Status: Data leaked
Country: United States
Listed on leak site: Aug 5, 2025

About the victim

AI dossier — public-source company profile

Hamilton Park Interiors is a luxury furniture and interior design retailer located in Murray, Utah (Salt Lake City area). Operating for over 25 years, they offer personalized design services, curated home furnishings, and a trade program for designers. The company operates a physical showroom and provides in-home, in-store, and virtual design consultations.

Industry: Luxury Home Furnishings & Interior Design
Address: 6336 S State St, Murray, UT 84107, United States

Attack summary

Severity: low — The disclosure contains only a listing/announcement with no proof files, screenshots, or details about what data was accessed. No operational impact or specific data types are documented in the available post.

The ransomware group 'pear' claims to have compromised Hamilton Park Interiors and published data. No specific details are provided in the available leak post excerpt regarding what data was exfiltrated or encrypted.

low

What the group claims

Hamilton Park Interiors offers thoughtfully designed and quality home furnishings that reflect your style and your life

Sources

Source

Indexed 11 months ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About pear

The Pear ransomware group is a relatively new threat actor that emerged in August 2025, operating with primarily financial motivations and targeting victims across multiple countries and sectors. Based on their recent emergence and limited public documentation, specific details about their country of origin and organizational structure remain unclear, though their targeting patterns suggest a financially-driven operation that may operate independently or as part of a smaller ransomware-as-a-service model. With 65 documented victims since their August 2025 debut, the group has demonstrated a preference for targeting organizations in the United States, New Zealand, Australia, Egypt, and Switzerland, with particular focus on healthcare, business services, manufacturing, and technology sectors. Their attack methodology and specific technical details have not been extensively documented by major threat intelligence firms or law enforcement agencies, though their rapid victim acquisition suggests they have established effective initial access and encryption capabilities. Notable campaigns and high-profile attacks have not been publicly detailed by CISA, FBI, or major security research organizations, likely due to the group's recent emergence and relatively small scale compared to established ransomware operations. As of late 2025, Pear appears to remain active given their recent emergence and ongoing victim targeting across multiple geographic regions and industry verticals. The group has been linked to 103 public disclosures across our corpus. First observed on a leak site on August 5, 2025; most recent post July 13, 2026. The operation is currently active.

Timeline of this disclosure

August 5, 2025Hamilton Park listed by pearon the group's public leak site

Other recent disclosures by pear

pear has been linked to 103 public victims on Darkfield. A sample of the most recent:

See the full pear dossier →

Sector and geography

Geographically, Hamilton Park is reported in United States, a country with 11,033 ransomware disclosures in our corpus.

If your organisation is affected

A listing by pear means Hamilton Park appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
Report the incident to your national CERT, CISA (United States), as required for your jurisdiction.
Monitor for the data appearing on pear's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.