What happened in two weeks
Between November 4 and 13, 2026, four Brazilian public bodies and state-owned companies confirmed security incidents. We read the coverage on November 16 and separated what each organization stated from what is still unknown.
- National Treasury, November 4. Unauthorized access to the e-Serviços portal, exposing about 30,000 registrations (name, CPF tax ID and e-mail), and to an internal query database holding about 4,000 Pix keys of people who receive federal payments. The Treasury said there was no financial impact, that its core systems were preserved, and that it notified the data protection authority (ANPD) and the government's incident response center (CTIR Gov).
- Caixa Vida e Previdência, November 6. Caixa Seguridade told the market on November 12 that the attack copied registration data of its 7.6 million active customers and of former customers: CPF, address, phone, e-mail and date of birth. According to the statement, there is no sign that financial or authentication data was compromised. The company notified the ANPD and the data subjects on November 11.
- Santos Port Authority. An attack was recorded in the first week of the month. On November 13 its online systems were still unstable and service ran through alternative channels. The authority said port operations continued normally.
- Minas Gerais Court of Justice, November 13. The court (TJMG) identified the incident on Friday and confirmed on Saturday the 14th that files had been disclosed. It did not say which files or how many people. According to the court, its judicial and administrative systems were not compromised. At-risk accounts had their passwords reset, and the ANPD and the police were notified.
None of the four said how the intruder got in.
Pix also failed in the period. On the evening of November 6, Downdetector reached 11,090 reports at 7:11 p.m., from customers of Banco do Brasil, Nubank, Itaú, Santander, Bradesco, Caixa and others. The Central Bank confirmed a partial failure, said it was resolved and gave no cause. None of the sources we read links that failure to the attacks.
The month before was already heavy
October was nicknamed "Black October" on social media. The label comes from no official alert, but the cases behind it are real, and four of them hit people who ship SaaS:
- LiteLLM. On October 21, version 1.107.0 of the PyPI package and its Docker images shipped with credential-stealing code. It stayed up for about two hours.
- Railway. The hosting platform reported possible unauthorized access to customers' environment variables and advised rotating the credentials stored there.
- Zeabur. The platform confirmed that data from 321,810 accounts and more than 3.2 million environment variable records was read on October 14 and 15, and announced it will shut down by December 31.
- Next.js. On October 14 a fix shipped for a critical remote code execution flaw in image optimization with SVG files (CVE-2026-96889, score 9.5), resolved in versions 16.4.1 and 15.5.28. Seven more fixes followed on November 3, in versions 16.4.5 and 15.5.29. We moved our own site to 16.4.5 the day we wrote this.
In the same month Brazil had 32 companies listed as ransomware victims, the fourth highest count in the world and the fifth monthly rise in a row (23 in June, 26 in July, 27 in August, 31 in September). The figures are from Ransomware.live, with Cohesity data, and count only companies that appeared on a leak site. A company that paid quietly is not in them.
What this changes for a SaaS
The two Brazilian leaks share a profile: registration data left, passwords and balances did not. It sounds like the mild case, and for your product it is the one that creates the most work in the following weeks.
Someone holding the name, CPF, e-mail, phone and date of birth of 7.6 million people can write an invoice or password reset message that gets every detail of the victim right. Some of those people are customers of your SaaS and use the same e-mail to log in. The attack that reaches you after a leak like this goes through your login form and your password recovery screen.
Railway and Zeabur show the other side. Your Stripe key, database password and e-mail provider token live in environment variables on someone else's platform. If the platform is read, the intruder needs no flaw in your code.
Five things to check this week
- Can your domain be spoofed? Without DMARC at reject, anyone can send e-mail to your customers with your sender address. Our SPF, DKIM and DMARC checker answers in a minute.
- Does password recovery ask for more than registration data? If a CPF and a date of birth are enough to change an account's password or e-mail, these two leaks opened that door. The flow must depend on something only the account owner has, such as access to the mailbox or a second factor.
- Does login have attempt limits, and a second factor for admins? An admin panel with no second factor is the shortest path once a reused password leaks.
- Can you rotate every secret within an hour? List the keys held in environment variables, who owns each one and how it is rotated. Teams on Railway or Zeabur had to do this with no warning.
- Are your dependencies pinned? The poisoned LiteLLM version was up for two hours. A project that installs the latest version on every build got it. A project with a lockfile and pinned versions did not.
If the incident is yours
Brazil's LGPD requires notifying the ANPD and the data subjects when an incident may cause relevant risk or harm, and the ANPD regulation sets the deadline at 3 business days from the moment you learn of it. For small processing agents, a category many startups fall into, ANPD Resolution 2/2022 doubles that period. What delays that notice most is being unable to answer the basics: which data left, from how many people, and by which path. The four organizations above still had no public answer for "by which path".
A manual penetration test answers that question before the incident, in the flows where a mistake costs most: login, password recovery, permissions and per-customer data. Our pentest Sprint costs R$9,500, with 25 hours of manual testing and a scope closed in writing.
Sources
- Diário de Pernambuco, Subsidiária da Caixa sofre ataque hacker e 7,6 milhões de clientes têm dados vazados, 2026-11-12
- Economic News Brasil, Ataque hacker ao Tesouro Nacional expõe 4 mil chaves Pix a golpes, 2026-11-13
- Fast Company Brasil, Brasil registra sequência de ataques hackers com vazamento de dados pessoais, 2026-11-13
- TI Inside, Brasil é o 4º país com mais ataques de ransomware no mundo, 2026-11-09
- Forças Terrestres, 'Black October': falhas críticas e vazamentos mobilizam empresas e autoridades de cibersegurança, 2026-10-22
- O Tempo, TJMG sofre ataque cibernético e confirma vazamento de arquivos, 2026-11-16
- NC News, Pix fora do ar em vários bancos, 2026-11-07
- Next.js, security advisories on GitHub
- ANPD, Resolução CD/ANPD nº 2/2022
