Based on the limited available information, teamxxx is a recently emerged ransomware group first observed in June 2025, appearing to be financially motivated based on their targeting patterns and operational characteristics. The group's origin and potential affiliations remain unclear due to their recent emergence and limited public documentation by major threat intelligence organizations. Their attack methodology and specific tools have not been extensively documented, though their diverse geographic targeting across the United States, Czech Republic, Hong Kong, Sweden, and Germany, combined with their focus on high-value sectors including healthcare, financial services, and hospitality suggests a financially-driven operation seeking maximum impact and payment potential. With only 12 known victims documented since their emergence, the group has not yet conducted any widely-publicized major campaigns that have drawn significant attention from law enforcement or security researchers. Given their recent first observation in June 2025, teamxxx appears to still be active, though their limited victim count and lack of extensive public reporting suggests they remain a relatively minor player in the current ransomware landscape. The group has been linked to 12 public disclosures across our corpus. First observed on a leak site on June 10, 2025; most recent post August 4, 2025. The operation is currently inactive.
Also tracked as: TEAM XXX.
Sector and geography
Geographically, peterpauper is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by teamxxx means peterpauper 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 teamxxx'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.
