Zacharia Levi Ltd was listed on 21 June 2025 by the handala ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). handala listed 23 organizations that month and 174 in total.
- Listed 515 days ago.
- 507 organizations were listed by all groups in June 2025, see the month.
- 35 in Financial Services that month.
- 14 in IL that month.
Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.
Zacharia Levi Ltd
Threat Group Post & Evidence
- Listed by
- Handala 174 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Zacharia Levi Ltd Hacked Handala, hereby declare that we have successfully infiltrated the servers of the Zionist construction company Zacharia Levi Ltd During this operation: The entire database,including project information, contracts, customer records, and financial documents,has been extracted. Internal communications and private emails of senior executives are now in our possession. Technical blueprints and documents…
Kinds of data mentioned
-
Email and communications
“…financial documents,has been extracted. Internal communications and private emails of senior executives are now in our possession. Technical blueprints and documents…”
-
Customer or client data
“…operation: The entire database,including project information, contracts, customer records, and financial documents,has been extracted. Internal communications and private emails…”
-
Contracts and legal files
“…During this operation: The entire database,including project information, contracts, customer records, and financial documents,has been extracted. Internal communications and…”
-
Source code and designs
“…private emails of senior executives are now in our possession. Technical blueprints and documents…”
-
Databases and backups
“…construction company Zacharia Levi Ltd During this operation: The entire database,including project information, contracts, customer records, and financial documents,has been…”
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Zacharia Levi (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Zacharia Levi directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Zacharia Levi can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, email and communications.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: source code and designs, databases and backups.
Within 30 days
- Keep watching Zacharia Levi A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Zacharia Levi
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: email and communications, customer or client data.
Within 3 days
- Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
48/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Launch Attack Surface Recon →Run a free passive scan on your own domain to see what an attacker can see from the outside.