About J
The J ransomware group is a newly emerged threat actor first observed in May 2025, operating with apparent financial motivations based on their targeting patterns across multiple countries and sectors. With limited public documentation available from established security research organizations, the group has demonstrated rapid operational capability by compromising 41 known victims within their initial months of activity. Their targeting strategy appears opportunistic, focusing primarily on organizations in the United States, United Kingdom, France, Argentina, and Germany, with a particular emphasis on technology companies, manufacturing firms, construction businesses, and business services providers. The diversity of their geographic and sectoral targeting suggests either a broad-spectrum approach to victim selection or potential use of automated tools for initial compromise identification. Given the recent emergence of this group and limited reporting from major cybersecurity firms and law enforcement agencies, specific details regarding their technical methodologies, ransom demands, data exfiltration practices, or organizational structure remain undocumented in publicly available threat intelligence. The group remains active as of current reporting periods, though their relative obscurity in established threat intelligence databases suggests they may be operating at a smaller scale compared to more prominent ransomware-as-a-service operations. The group has been linked to 41 public disclosures across our corpus. First observed on a leak site on May 2, 2025; most recent post November 9, 2025. The operation is currently inactive.
Sector and geography
This disclosure adds to ransomware activity in the Education sector, which has 1,082 disclosures indexed across all operators we track. Geographically, uva.edu.br is reported in Brazil, a country with 404 ransomware disclosures in our corpus.
If your organisation is affected
A listing by J means uva.edu.br 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, CERT.br (Brazil), as required for your jurisdiction.
- Monitor for the data appearing on J'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.
