iam.ma Listed by apt73 Ransomware Group: Ransomware Claim — What’s Alleged & What To Do
iam.ma was listed by the apt73 ransomware group on April 27, 2026, with internal files reported as exfiltrated. Anyone connected to the organisation should check for any signs of exposure and take appropriate protective steps.
On April 27, 2026, the domain iam.ma appeared on a listing published by the group apt73. The entry states that internal files were exfiltrated during a ransomware incident. No figure has been released for the number of individuals affected, and the organization has not issued a public statement confirming or detailing the event.
The listing provides the only public indication that data from iam.ma has been removed from its systems. Beyond the claim of exfiltrated internal files, no additional technical details, such as the volume of data or the method of access, have been disclosed.
Inside the incident
The reported incident centers on iam.ma and consists of a single public claim by apt73 that files were taken. The date the listing appeared is April 27, 2026. No information has been made available about when the underlying activity occurred, how long systems were accessed, or whether any data was later published or sold. The number of records involved remains unknown.
Who is apt73?
Apt73 is a ransomware group that maintains a leak site where it lists organizations it claims to have targeted. Such groups typically gain initial access through phishing, remote-access vulnerabilities, or compromised credentials, then move laterally before deploying encryption and exfiltrating data. Their public listings serve as a pressure tactic on victims. The appearance of iam.ma on the site constitutes the group’s claim; independent confirmation of the underlying events has not been reported.
iam.ma and its sector
Iam.ma is associated with Maroc Telecom, a major telecommunications provider operating in Morocco. Companies in this sector manage mobile and fixed-line services, customer billing systems, network infrastructure, and internal corporate records. A breach at such an organization can involve both customer account information and operational data that supports service delivery across the country.
What data was at risk
The only detail released is that internal files were allegedly exfiltrated. No inventory of specific file types, databases, or record counts has been published. Telecommunications providers routinely hold customer identifiers, service records, and network configuration data, yet it is not confirmed whether any of these categories were among the files removed in this case.
Why it matters
Even without a confirmed count of affected individuals, the exposure of internal files from a telecommunications operator can create downstream risks. Personal or account-related information, if present, could be used for targeted fraud or account takeover. For the organization, the incident adds operational and regulatory pressure while the scope of the data remains unclear.
What to do if you're exposed
Individuals concerned about possible exposure should monitor their financial and service accounts for unusual activity and change passwords on any iam.ma or Maroc Telecom-linked services. Enabling multi-factor authentication where available reduces the chance of unauthorized access. Readers can also run a free exposure scan of their email address against known breach data to check for appearances in previously published datasets.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
flazio.com Listed by apt73 Ransomware Groupsmarty.arpinet.am Listed by apt73 Ransomware Groupsella.eng.br Listed by apt73 Ransomware Groupires.ma Listed by apt73 Ransomware GroupLatest breaches
Read GalaxyWarden’s full analysis of the iam.ma Listed by apt73 Ransomware Group →
Publicly posted by apt73 — unverified claim, pending independent verification
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.