El-Mohandes
bd_2ad197cb83b2ec2f · schema v1 · pii pii-v1
Full breach record for El-Mohandes →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group ALPHV / BlackCat on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
El Mohandes was established in 1998, in Janaklis, El-Behira Governorate, which is about 80 km away from Alexandria Port. The company has a total surface area of 80,000 Sqm and more than 1000 employees and workers serving in various functions and departments. We are proud to be offering a wide scope of products and unique services to a large number of clients. This enabled El Mohandes to contribute to the growth and development of several industries in Egypt. We provide a large variety of distinctive products and services, such as filling (bulk, IBC, drums, cans), mixing, and blending. We also provide technical support and some services especially tailored to several industries. Our success story, providing outstanding professional services and products, is based on the hard work and dedication of our excellent management team, highly qualified and trained workers and employees in all fields, and a strong marketing network. We are also firmly committed to the highest standards of safety and security in our working environment. All these factors enabled us to serve the needs of thousands of customers in Egypt, the Middle East, and Africa. However, the key to our success remains the desire of our customers to purchase our products to obtain the highest levels of quality at unbeatable prices.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 5, 2023
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
alphv
According to ransomware.live, The operators of the ALPHV/BlackCat ransomware began their activity in December 2021, making posts on Dark Web forums to promote their affiliate program, offering other actors the opportunity to engage in a 'new type of ransomware family' developed from scratch using the Rust programming language. Some clear evidence indicates that the actors behind this new ransomware are not new to cybercrime, and there were links to other affiliate programs such as DarkSide, BlackMatter, and REvil. (After several attacks against large companies, these groups faced pressure and arrests, necessitating the termination of their operations). As a security measure, the operators of ALPHV implemented the requirement for the execution of the ransomware payload by providing an 'access token,' which is supplied by the owners of the Ransomware-as-a-Service to the affiliate. This token is added to the victim's ransom note so that they can contact the threat actor responsible for encrypting the data. ALPHV affiliates employ double and triple extortion techniques, meaning the publication of the company's name on leak sites, threats of data leakage, and lastly, threats of DDoS attacks against the organization. Source: https://github.com/crocodyli/ThreatActors-TTPs