VX Case was listed on 29 March 2026 by the nova ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). nova listed 2 organizations that month and 177 in total.
- Listed 234 days ago.
- 839 organizations were listed by all groups in March 2026, see the month.
- 62 in Retail & E-Commerce that month.
- 14 in BR that month.
Updated 2026-11-19 05:47 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Nova 177 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.
vxcase.com.br is the website of a Brazilian e-commerce store that primarily sells accessories for cell phones and electronics, such as cases, screen protectors, and related products. The site is operated by a company called VX Case, which works in the smartphone and device accessories market - we got whatsapp pictures, customers informations and pictures, workers informations and more, only sansitive. corp you have 10 days to contact and get in touch to recover what you have lost and stop leak op.
Kinds of data mentioned
-
Customer or client data
“…the smartphone and device accessories market - we got whatsapp pictures, customers informations and pictures, workers informations and more, only sansitive. corp you have 10…”
Plain-English summary AI-written
The group says it obtained WhatsApp pictures, customer information and pictures, worker information, and other sensitive data from VX Case.
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 VX Case (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 VX Case 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 VX Case 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 VX Case 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 VX Case
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
- Check regulatory and stakeholder notification duties Brazil: LGPD requires notifying the ANPD and affected people of incidents that may cause relevant risk or harm. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Brazil.
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)
38/100 • LOWA 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.