Buró Laboral México breach exposes records tied to about 560 companies: what to do if your Mexico operation or its candidates are in it
On November 13, 2026, El Economista reported a breach at Buró Laboral México, a local employment-history platform, with records tied to about 560 companies.
If your local HR team or recruiting agency used it, the data of your Mexico staff and candidates may be out there. Your headquarters may not even know the platform exists. That is the first thing worth fixing.
What employee and candidate data is usually exposed
Employment-history platforms in Mexico store what HR collects at hiring: full name, CURP (the national population ID), RFC (the tax ID), phone, email, address and job history.
The exact scope of this breach is not public yet. But with a CURP and an RFC, a fraudster can already do a lot.
| Data | How a fraudster uses it | What to do |
|---|---|---|
| CURP and RFC | Open accounts or apply for credit in someone else’s name | Tell staff to watch their credit report |
| Email and phone | Phishing and calls that sound legitimate | Distrust messages that know too much |
| Job history | Pose as HR or a former manager | Verify through another channel |
Why impersonation is a bigger worry now
One day earlier, Expansión reported that Mexico’s new Digital Economy Law opens an impersonation and data-theft challenge for smaller companies. More digital payments and paperwork mean more places where stolen data is useful.
In our experience, the hit rarely comes on breach day. It comes weeks later: an email “from HR” asking to update a payroll bank account, or a call to accounting from someone who already knows everyone’s RFC. More on that in our Digital Economy Law IT checklist.
What Mexican privacy law expects from your local entity
The LFPDPPP is Mexico’s private-sector data protection law. If you know GDPR, the logic will feel familiar: whoever collects the data is responsible for it, even when a vendor stores it.
In short, your Mexico entity needs:
- A privacy notice (aviso de privacidad) that lists who receives staff and candidate data.
- Administrative, technical and physical safeguards.
- To inform affected people without delay when a breach significantly affects them.
- Contracts that bind each vendor to protect the data and report incidents.
How to tell your Mexico staff without causing panic
A short, clear message in Spanish beats a long global memo. Say what happened, what you know and what you do not know yet.
Give three easy rules: HR never asks for passwords over WhatsApp, payroll account changes are never done by email alone, and anything odd goes to a named person. If you kept candidate data, candidates deserve the notice too.
HR checklist for this week
- List every external platform that receives staff data: payroll, job boards, background checks, insurers, e-signature.
- Check who has a login in each one. Remove people who left; here is how to cut access when an admin or vendor leaves.
- Turn on 2FA (a phone code on top of the password) everywhere, starting with payroll and the HR mailbox.
- Review vendor contracts for data clauses and incident notice. See how to check vendor access.
- Delete what you no longer use: old CVs, spreadsheets full of CURPs, forgotten shared folders.
What about your Mexico operation?
If nobody at headquarters can name the vendors that hold your Mexico staff data, that is your starting point.
At ProcessBi the support plan includes a vendor access audit, email and Microsoft 365 protected with 2FA, and an incident response plan in English and Spanish, invoiced in MXN or USD.
Book your free assessment — we reply the same business day.
Your path
Running IT in Mexico from abroad
77 of 89- M365 outage plan ✓ Read You are here 3 min
- Firewall and MSP ✓ Read You are here 3 min
- HR data breach ✓ Read You are here 3 min
- IDE extensions ✓ Read You are here 3 min
- Network changes ✓ Read You are here 3 min
- WhatsApp with AI ✓ Read You are here 3 min
- AI phone agents ✓ Read You are here 3 min
- Field services →