Egypt ransomware and cyber extortion policy

A Disputed Telecom Egypt Ransomware Claim Shows Egypt's Rules Punish Attackers but Leave Breach Disclosure Untested

Egypt's 2018 cybercrime law and new data-protection rules pair heavy attacker penalties with an untested disclosure duty, as an unconfirmed N0n claim shows.

Egypt's Ransomware Rules by the Numbers People of Internet Research · Egypt 72 hrs Breach notice deadline Controllers must notify the data c… EGP 5M Max fine, state systems Article 20 tier where data is dest… 180 days Mandatory log retention Service providers must retain logs… peopleofinternet.com
Egypt's Ransomware Rules by the Number… People of Internet Research · Egypt 72 hrs Breach notice deadline EGP 5M Max fine, state systems 180 days Mandatory log retention peopleofinternet.com

Key Takeaways

On 18 October 2026, the ransomware group N0n was reported to have listed Telecom Egypt on its extortion site, according to the threat-intelligence aggregator DeXpose. Neither the company nor Egyptian authorities has confirmed it. The trackers also list a run of 2026 claims against Egyptian entities, including the Egyptian Airports Company and Petroshahd, the Egypt branch of ENAP Sipetrol. This article treats all of these as unverified claims.

What we can and cannot say

The evidence is thin. The DeXpose page gives the date and names Telecom Egypt in its header fields. But the leak-site text it reproduces describes a different victim: a "computer training academy" in Egypt, with course materials and student account folders. The page does not explain the mismatch, and I found no statement from Telecom Egypt. SOCRadar's tracker entry returned an access error when I tried to open it, so I could not check what it says.

That gap matters for policy. Extortion sites are marketing venues for criminals. A listing can be inflated, mislabelled or recycled, and a regime that reacts to listings rather than confirmed intrusions will punish the wrong people. It also means the public cannot tell whether an incident happened unless the victim says so. That is the problem breach-disclosure rules exist to solve.

The strongest case for tougher rules

The case for aggressive state action is serious. Ransomware against a national telecom operator or an airports company can degrade services millions of people rely on. Victims have every incentive to stay silent, pay quietly and hope the leak never surfaces. Regulators argue that without mandatory reporting and heavy penalties, nobody can see the scale of the problem, and attackers face no deterrent.

Egypt's Law No. 175 of 2018 on Information Technology Crimes takes that logic seriously on the attacker side. In the English translation, Article 14 sets one to two years' imprisonment and fines of EGP 50,000 to 200,000 for unlawful access, with the higher tier when data is destroyed, altered, copied or republished. Article 17 covers destroying or deleting data, with at least two years and EGP 100,000 to 500,000. Article 20 covers systems managed by or on behalf of the State or a public legal entity, with fines of EGP 1 million to 5 million where data is destroyed, altered, duplicated or republished. Article 21 aggravates penalties for disrupting a state-operated network. Article 3 extends the law to non-Egyptians acting abroad when, among other conditions, the victim is Egyptian or an organised group operates in Egypt.

Where the framework is thin

The attacker-side provisions are strong, but the provisions I reviewed do not address ransom payment, and Law 175 does not contain a breach-notification duty. Article 2 requires service providers to retain logs for 180 days and to "secure the data and information to ensure its confidentiality, prevent unauthorized access, and protect against damage." It also requires them, on national security agencies' request, to provide technical capabilities to those agencies. That is a duty to defend and a duty to assist the state. It is not a duty to tell the public or a data regulator that a breach has happened.

That job falls to the Personal Data Protection Law, No. 151 of 2020. Its executive regulations were issued as Ministerial Decision No. 816 of 2025 on 1 November 2025, according to CMS. CMS says controllers and processors must notify the Personal Data Protection Centre within 72 hours of becoming aware of a breach, and affected individuals within three days of that notification, or sooner where national security is involved. CMS also says the regulations were not made public until 25 December 2025 and that a one-year compliance period began on issuance. It reports enforcement as expected from 1 November 2026, with "some uncertainty" about that date.

The timing is awkward. If CMS's date is right, the Telecom Egypt claim, dated 18 October, landed just before the notification regime was due to bite. Whether that regime applies to the operator, and whether any notification was filed, is not publicly known. I could not reach official Egyptian ministry or regulator pages to check.

A proportionate path

The pro-innovation answer is not to add penalties. Egypt already has them, and criminals operating from leak sites abroad are not deterred by a fine they will never pay. Three changes would do more good.

First, make disclosure the centre of the framework. A 72-hour regulator notice is a reasonable, GDPR-style standard, but it only works if regulators publish aggregate incident statistics and confirm or deny significant public claims. Silence lets rumour fill the gap. Second, keep disclosure separate from the security apparatus. A duty to report to a data regulator should not be routed through national security agencies as the default channel, because victims who fear that route will report less. Third, shift the emphasis to prevention. The EFF's AI cybersecurity framework is written about AI developers, not telecoms. But its core argument transfers: existing practices such as network isolation, least-privilege access, logging and monitoring, and incident-response procedures would prevent many incidents, and legislation can require them with liability for failures.

A fourth question is open: whether paying ransoms should be restricted. Egypt has not answered it in the text I reviewed, and the evidence on bans is contested. A sensible first step is mandatory reporting of any payment to the regulator, which gives officials data without criminalising victims.

What to watch

Three facts will show whether the framework works. First, whether Telecom Egypt, the airports company or Petroshahd confirm or deny the claims. Second, whether the Personal Data Protection Centre publishes breach statistics once enforcement starts. Third, whether any prosecution under Law 175 reaches an extortion actor rather than a domestic defendant. Until then, Egypt has strong penalties on paper and little public evidence about how it handles real incidents.

Sources & Citations

  1. Law No. 175 of 2018 on IT Crimes (English translation)
  2. CMS: Egypt PDPL executive regulations
  3. DeXpose: N0n listing of Telecom Egypt
  4. EFF: AI Cybersecurity Policy Framework