LowBreach / campaignMonitoring

aoqin leaks ransomware group claims attack on Petroshahd (Enap Sipetrol Egypt)

RansomLook says aoqin leaks listed Petroshahd (Enap Sipetrol Egypt) on its leak site; unconfirmed, so watch for official statements.

Published
Exploitation
No evidence in the sources; the only item is a leak-site listing claim, not confirmed by the victim

What happened

According to the ransomware tracker RansomLook, the aoqin leaks ransomware group claimed Petroshahd (Enap Sipetrol International - Egypt Branch) on its leak site. The listing was recorded on 2026-11-10 RansomLook. RansomLook reports the group’s listing; a listing is a claim by the group, not proof of an intrusion.

What is not confirmed:

  • The victim has not confirmed the claim. No source provided here carries a statement from Petroshahd or Enap Sipetrol.
  • No independent outlet verifies it. The only sources are a claim tracker and its headline.
  • The sources do not say what data was taken, how much, or whether any systems were encrypted.
  • The entry point, the date of any intrusion and the group’s demands are not confirmed.
  • The page we retrieved from RansomLook was its general front page and did not show the details of this listing.

Am I affected?

Nothing in the sources identifies who, beyond the named organisation, could be affected. If you work for or do business with Petroshahd or Enap Sipetrol’s Egypt branch, you may want to ask your contact whether the company has issued guidance. Whether any customer, partner or employee data is involved is not confirmed. For everyone else, there is nothing to act on from these sources.

What to do now

  1. Treat the listing as an unverified claim until Petroshahd or Enap Sipetrol confirms or denies it.
  2. If you are a direct contact of the company, check for an official notice through your normal business channel rather than through the leak site.
  3. Be cautious with unexpected emails or calls that mention this claim, and verify them through a known contact before responding.
  4. Check back for updates; this advisory will be revised if a source with more detail appears.

Sources