Skip to main content

Ransomware victim disclosure

All victims

Raimore Construction

listed as raimore.com · Claimed by Projectrelic · listed 10 months ago

9m
Age
since listed · data leaked

Status timeline

  1. ListedSep 29, 2025
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Country
Japan
Listed on leak site
Sep 29, 2025

About the victim

AI dossier — public-source company profile

Raimore Construction is a licensed, bonded, and insured general contractor located in the N/NE Portland, Oregon community. The company has been minority-owned and operated since its founding in 1999 and holds federal and State of Oregon MBE & ESB certifications. Over 80% of staff, including supervisory and management personnel, are minorities.

Industry
General Contracting & Construction
Address
Portland, Oregon, USA (N/NE Portland community)
Founded
1999

Attack summary

Severity: medium — Data is listed as published, indicating confirmed exfiltration and release; however, no details on the nature or scale of the data are provided, and the victim is a small regional contractor, limiting assessed severity to medium.

The group Projectrelic claims to have attacked Raimore Construction and the disclosure status is listed as data_published, indicating data has been released. No specific details about encryption, exfiltration methods, or data categories are provided in the leak post.

medium

Original description

AI-summarised, not from the leak post

N/A

Sources

Source

Indexed 10 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 Projectrelic

Projectrelic is a ransomware group that emerged in November 2022, operating with apparent financial motivations based on their targeting patterns and victim extortion activities. The group has been documented attacking 46 organizations primarily across the United States, United Kingdom, India, Germany, and France, with a focus on technology, manufacturing, construction, and education sectors, though many victims' sector classifications remain undocumented. Limited public intelligence exists regarding Projectrelic's country of origin, organizational structure, or potential affiliations with other cybercriminal groups, and it remains unclear whether they operate as an independent entity or utilize a ransomware-as-a-service model. Similarly, detailed information about their specific attack methodologies, initial access vectors, encryption techniques, or use of double extortion tactics has not been extensively documented by major threat intelligence firms or law enforcement agencies. The group has not been associated with any particularly high-profile attacks or record ransom demands that have garnered significant public attention from security researchers or government agencies. Based on available reporting, Projectrelic appears to maintain some level of operational activity, though comprehensive assessments of their current operational status are limited due to the relatively sparse public documentation surrounding this particular threat actor. The group has been linked to 46 public disclosures across our corpus. First observed on a leak site on November 11, 2022; most recent post November 9, 2025. The operation is currently inactive.

Timeline of this disclosure

  • September 29, 2025raimore.com listed by Projectrelicon the group's public leak site

Sector and geography

Geographically, raimore.com is reported in Japan, a country with 220 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Projectrelic means raimore.com 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, JPCERT/CC (Japan), as required for your jurisdiction.
  • Monitor for the data appearing on Projectrelic'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.