What do hackers already know about your business? Get Your Free Report
Alleged

khanehsazii.ir Data Breach

Published: Nov 17, 2026 Black X

Threat Level

High

Confidence: High

Quick Summary

Company
khanehsazii.ir Data Breach
Industry
Construction
Threat Actor
Black X
Date of Incident
Nov 17, 2026

Executive Summary

Black X listed khanehsazii[.]ir on its ransomware leak site on 2026-11-17, an observation identified through the SOCRadar CTI platform and reported as part of SOCRadar’s daily ransomware coverage. The domain belongs to an Iranian real estate and housing services firm operating in the construction and property services sector. The leak-site posting currently represents an alleged compromise rather than an independently confirmed breach, and Black X has not disclosed the nature or volume of any data involved. The listing nevertheless places a Middle Eastern property-sector organization inside an active extortion campaign, underscoring that commercial firms across the region’s construction and professional services landscape remain within the targeting scope of ransomware and extortion operations. Black X presents as a limited-profile ransomware operation. Its prior leak-site listings have concentrated on Middle Eastern commercial and professional services targets, and the group is described as operating selectively, favoring mid-size commercial organizations in markets with limited ransomware response infrastructure. The khanehsazii.ir listing fits this pattern closely: the victim is an Iranian commercial entity operating in a sector adjacent to the professional services targets the group has historically listed, in a market where ransomware response capabilities are comparatively constrained. This alignment between the victim’s geography and organizational profile and Black X’s established preferences indicates that the listing is consistent with the group’s known victimology rather than an outlier claim.

Technical Analysis

SOCRadar’s stealer-log telemetry returned a result for the khanehsazii.ir domain, but the finding is limited in what it establishes. The domain is present in SOCRadar telemetry; however, no actionable credentials surfaced in the queried stealer-log dataset, and the records associated with the domain lacked sufficient attribution to confirm organizational personnel access or internal authentication data. In practical terms, the presence of the domain alone does not demonstrate that specific employee accounts were compromised or that internal authentication data was exposed. The absence of attributable credential records therefore cannot be read either as evidence of account-level compromise or as confirmation that the organization’s credentials have not circulated elsewhere. The more significant signal is that domain exposure in threat intelligence data streams indicates active credential aggregation scanning tied to khanehsazii.ir. Aggregation of this kind means threat actors or automated collectors are systematically gathering and indexing credential material associated with the domain name, even where individual records cannot yet be tied to confirmed personnel. The null stealer-log result is not an all-clear: the current finding reflects only the data available at the time of the query, and unattributed or fragmented records may still hold relevance for the organization. If valid credential material tied to the domain were to surface, or already exist outside the indexed set, it could potentially be leveraged against web-facing portals and client-facing systems. Given these limitations, the recommended posture is verification and continued monitoring rather than assumption of safety. Organizations should audit authentication logs for web-facing portals and client-facing systems to detect anomalous or unrecognized access activity that could indicate attempted use of aggregated credentials. Continued monitoring of stealer-log telemetry and dark web sources for the khanehsazii.ir domain is also warranted, as additional records may surface after the current analysis window. Until credential exposure can be ruled out across a broader range of sources, the null stealer-log finding should be treated as an interim observation rather than a clean bill of health.

Disclaimer

This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.

Share

LinkedIn