Weyhro is an emerging ransomware group that was first observed in March 2025, appearing to be primarily financially motivated based on their targeting patterns and operational behavior. The group's origin and affiliations remain unclear due to their recent emergence, with insufficient public documentation from major threat intelligence sources to confirm their country of origin, potential links to established ransomware families, or whether they operate under a Ransomware-as-a-Service model. With only 14 documented victims since their March 2025 debut, specific details about their attack methodology, initial access vectors, encryption techniques, and data exfiltration practices have not been comprehensively documented by CISA, FBI, Mandiant, or other reputable security researchers. The group has demonstrated a geographically diverse targeting approach, primarily focusing on victims in the United States, Germany, Canada, Barbados, and Italy, with a sector preference for manufacturing, financial services, business services, and technology organizations. Given the group's recent emergence and limited victim count, no major high-profile campaigns, record ransom demands, or law enforcement actions have been publicly reported. Weyhro appears to remain active as of current reporting, though their operational tempo and long-term sustainability remain to be determined given the limited intelligence available on this nascent threat actor. The group has been linked to 14 public disclosures across our corpus. First observed on a leak site on March 6, 2025; most recent post August 11, 2025. The operation is currently inactive.
Sector and geography
Geographically, 101 Arch Street is reported in United States, a country with 11,033 ransomware disclosures in our corpus.
If your organisation is affected
A listing by weyhro means 101 Arch Street 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 weyhro'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.
