Skip to main content

Ransomware victim disclosure

All victims

G*****

Claimed by Payouts King · listed 1 year ago

12m
Age
since listed · data leaked

Status timeline

  1. ListedJul 14, 2025
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Listed on leak site
Jul 14, 2025

About the victim

AI dossier — public-source company profile

Unable to determine. Victim name is redacted (G*****) and no leak post or public site content was captured.

Attack summary

Severity: low — No verifiable evidence, leak post content, or proof materials are available. Cannot confirm exfiltration, encryption, or impact. Listing only.

No leak post or supporting details were captured. The disclosure status indicates data was published, but the nature of the attack (encryption, exfiltration, or both) and data at stake are unknown.

low

Sources

Source

Indexed 1 year 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 Payouts King

Payouts King Group. We are not RaaS. No affiliates are accepted. We use Tox messaging protocol. The group has been linked to 100 public disclosures across our corpus. First observed on a leak site on July 7, 2025; most recent post May 13, 2026. The operation is currently active.

Also tracked as: payoutsking.

Timeline of this disclosure

  • July 14, 2025G***** listed by Payouts Kingon the group's public leak site

Sector and geography

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

If your organisation is affected

A listing by Payouts King means G***** 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 Payouts King'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.