Skip to main content
Darkfield

Ransomware victim disclosure

← All victims

Amzur

listed as amzur.com · Claimed by Unsafe · listed 3 days ago

2d
Age
since listed · data leaked

Status timeline

  1. ListedAug 28, 2026
  2. Data leakeddate unknown

At a glance

Group
Unsafe
Status
Data leaked
Country
Brazil
Listed on leak site
Aug 28, 2026

About the victim

AI dossier — public-source company profile

Amzur is a digital transformation and product engineering consulting firm offering services across cloud, AI/ML, ERP, custom application development, and managed services. They serve clients in the USA, UAE, and Africa across sectors including energy, government, healthcare, insurance, manufacturing, and retail.

Industry
IT Consulting & Digital Transformation Services

Attack summary

Severity: low — Post contains only a listing announcement with no proof files, screenshots, or detailed description of data exfiltrated. Revenue figure ($73.4 million) is listed but no ransom demand or specific data inventory is stated. Lacks evidence of actual data access or breach.

The unsafe group claims to have published data from Amzur. No specific details are provided in the leak post regarding what data was exfiltrated, encrypted, or the nature of the operational impact.

low

What the group claims

Revenue: $73.4 million

Sources

Source

Indexed 3 days 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 unsafe

The "unsafe" ransomware group is a relatively new threat actor that emerged in December 2022, operating with primarily financial motivations through ransomware deployment and extortion schemes. Based on limited public documentation, the group's origin and specific affiliations remain unclear, though their operational patterns suggest they function as an independent ransomware operation rather than a established Ransomware-as-a-Service model. With 14 documented victims since their emergence, the group has demonstrated a focused targeting approach, primarily concentrating their attacks on manufacturing organizations, transportation and logistics companies, and government entities across the United States, Switzerland, and France. Their attack methodology and specific technical capabilities have not been extensively documented by major security research organizations such as CISA, FBI, or Mandiant, limiting detailed analysis of their initial access vectors, encryption methods, or data exfiltration practices. No major high-profile campaigns or significant law enforcement actions have been publicly reported against this group, likely due to their relatively recent emergence and smaller scale of operations compared to more established ransomware families. Current intelligence suggests the group remains active as of available reporting, though their limited public footprint makes definitive status assessment challenging without additional threat intelligence sources. The group has been linked to 22 public disclosures across our corpus. First observed on a leak site on December 21, 2022; most recent post August 28, 2026. The operation is currently inactive.

Timeline of this disclosure

  • August 28, 2026amzur.com listed by unsafeon the group's public leak site

Other recent disclosures by unsafe

unsafe has been linked to 22 public victims on Darkfield. A sample of the most recent:

See the full unsafe dossier →

Sector and geography

Geographically, amzur.com is reported in Brazil, a country with 208 ransomware disclosures in our corpus.

If your organisation is affected

A listing by unsafe means amzur.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, CERT.br (Brazil), as required for your jurisdiction.
  • Monitor for the data appearing on unsafe'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.