People search CONASEMS data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 CONASEMS-linked incident, with headline counts up to 766K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why CONASEMS breach history matters
CONASEMS operates in Government / Healthcare (Brazil). Across indexed rows, recurring themes include unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — actor 888 leak claim; 766K users cited (unverified)
Unverified claim — treat actor counts cautiously. Unverified criminal-forum leak claim — observed July 14, 2026. Dark Web Informer reported actor alias 888 advertised a second alleged database dump from CONASEMS (Conselho Nacional de Secretarias Municipais de Saúde), Brazil's national council of municipal health secretariats, citing 766,000 unique users following an earlier November 2025 claim attributed to the same actor. Listed fields include CPF numbers, account passwords, contact data, and sensitive demographic categories. CONASEMS had not issued a matching pu Exposed categories include Actor-claimed 766,000 unique users with names, CPF national IDs, passwords, emails, phones, dates of birth, locations, sexual orientation, gender identity, disability status, and r. BreachHistory cites approximately 766K+ affected records in this row. See the conasems-forum888 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Unverified actor or scraping claims — appears across multiple CONASEMS catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the CONASEMS company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/conasems · Latest: conasems-forum8882026.
Sources: BreachHistory catalog (1 row for CONASEMS), company and regulator disclosures cited in individual breach records.