lewa.com was listed on 03 October 2024 by the blackbasta ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). blackbasta listed 12 organizations that month and 523 in total.
- Listed 777 days ago.
- 543 organizations were listed by all groups in October 2024, see the month.
- 87 in Manufacturing that month.
- 2 in AT that month.
Updated 2026-11-19 06:25 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Black Basta 523 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.
For more than seven decades LEWA has set the technical standards as a manufacturer of pumps and systems for fluid metering. Our focus lies on metering and process pumps, metering systems and complete systems for process engineering processes. Pumps from LEWA are used today in a wide range of industries, from the very sensitive food industry to petrochemistry and refinery. We plan and produce efficient and individualized system solutions for nearly all metering requirements, conveyance, mixing, or odorizing tasks.SITE: www.lewa.com Address : LEWA Austria GmbH Diefenbachgasse 35/3/9 1150 ViennaTEL#: +43 1 8773 040-0ALL DATA SIZE: ≈400gb+ 1. Emplyees personal docs 2. Corporate data: Financial, Personal, HR, Acctg 3. Projects, DWG 4. Customer contracts, Confidential data 5. Engineering data, R&D(Fue) & etc…
Amounts as written
- 400gb
- 4. Customer
Kinds of data mentioned
-
Customer or client data
“…2. Corporate data: Financial, Personal, HR, Acctg 3. Projects, DWG 4. Customer contracts, Confidential data 5. Engineering data, R&D(Fue) & etc…”
-
Contracts and legal files
“…Corporate data: Financial, Personal, HR, Acctg 3. Projects, DWG 4. Customer contracts, Confidential data 5. Engineering data, R&D(Fue) & etc…”
Plain-English summary AI-written
The group says it holds more than 400 GB of data, including employees’ personal documents and corporate financial data.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
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 lewa.com (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 lewa.com 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 lewa.com 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.
Within 30 days
- Keep watching lewa.com 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 lewa.com
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: customer or client data.
Within 3 days
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 400gb, 4. Customer. Treat group figures as unverified.
- Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
- Check regulatory and stakeholder notification duties EU/EEA: GDPR Art. 33 and 34 require notifying the supervisory authority within 72 hours of becoming aware of a personal data breach, and affected people where risk is high. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Austria.
-
Check the ways blackbasta is reported to get in
Check these first; they are how the group is reported to work in general.
- Affiliates mainly use spearphishing; from February 2024 they also exploited ConnectWise CVE-2024-1709. (update of 8 Nov 2024)
- The November 2024 update adds a campaign of spam followed by calls and Microsoft Teams messages posing as IT support to get remote-access tools installed. (update of 8 Nov 2024)
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)
70/100 • ELEVATEDA 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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.