← Back to blog Cybersecurity

Hackers stole 133 million dollars from a French bank through its service provider: how to check vendor access at your Mexico operation today

3 min read

On November 7, BleepingComputer reported that attackers stole about 100 million euros, roughly 133 million dollars, from a French bank. They did not break down the front door. They walked in through a service provider that already had access.

If you run a plant, warehouse or office in Mexico from Houston, Madrid or Toronto, this should sound familiar. Your local site probably has an accounting firm, an integrator, a CCTV contractor and a payroll platform plugged into its network. Often nobody at headquarters has the full list.

133M USD stolen from a French bank, about 100 million euros
1 provider was the way in, according to the reports

What happened and why it matters for a Mexico site

Mexican outlet Excélsior covered it on November 4, and the technical details are still coming out. The path is clear, though: the attacker did not look for the hardest lock. They looked for someone with a key.

In our experience, foreign operations in Mexico get the firewall right (the device that filters traffic in and out of the network) and lose track of who has a login inside. That is the gap.

Your local vendor chain holds more keys than you think

Inventory first You cannot close a door you do not know exists. Make the list before changing anything.

Picture a typical plant in Querétaro. The local accounting firm (the despacho contable) logs into the accounting system over remote desktop. The CCTV contractor watches the cameras from a phone app. Payroll uploads files with a shared account. And the integrator who installed the switches left their user in place “just in case”.

Nobody did anything wrong. But each one is a key, and headquarters rarely knows how many there are.

My Press put it well this week (in Spanish): with nearshoring, cyber risk also comes in through suppliers. Once your Mexico site connects to the corporate network, your smallest local vendor becomes part of your supply chain risk.

We saw the same pattern with the stolen ConnectWise credential that opened the Microsoft 365 tenants of many clients at once. This time the target was a bank. The shape is identical.

Checklist: how to review vendor access today

Two terms first. MFA is the second factor: on top of the password, a code or an approval on a phone. A VLAN is a separate network that lives inside the same switches.

What to checkWhat good looks like
Access inventoryA list of every vendor, which system they touch and who owns the relationship
Named accounts with MFAOne user per person, with a real name, and a second factor
Expiring accessOpened for the job and closed automatically when it ends
VLAN segmentationThe camera contractor reaches the recorder, not the ERP
LogsA record of who logged in, when and what they did
Contract clausesIncident notice, handover of credentials and data deletion on exit

Segment the network so no vendor sees everything

Everyone in their own lane Cameras, guests, office and production on separate networks, with clear rules between them.

If the CCTV contractor logs in, they should only reach the recorder. If someone steals their password, the damage stays there and does not jump to payroll or to your corporate VPN.

We walk through it in how to separate guests, CCTV and IoT with VLANs. The same logic applies to vendors.

Assume breach

Backups out of reach A copy no vendor can delete is what gets your Mexico site running again.

In an interview with Diario Judío México, the CISO of monday.com described the Israeli doctrine of assume breach: work as if the attacker is already inside. We think it is the right mindset for a Mexico site run from abroad.

In practice: review logs every month, not only when something breaks. Keep backups that no vendor can delete. And know who answers the phone at 2 a.m. local time.

We are a vendor too

Access in writing Which accounts we use, what for and how we hand them back: it is all in the plan.

It would be odd to ask this of you and not do it ourselves. At ProcessBi we document every access we use, with named accounts and MFA, and hand it over whenever you ask. It is written into our IT support plans, with an SLA and reports in English for headquarters.

We also review your other local vendors: who gets in, through where and with which permissions. No finger-pointing. Just a list that adds up.

Reviewing vendor agreements with a local partner
An up-to-date vendor list beats yet another firewall Foto: Pexels

What about your Mexico operation?

Try this: can you say right now, without looking, how many vendors have a login on your Mexico network? If the answer takes a while, that is where we start.

Book your free vendor access review — we reply the same business day.

Your path

Running IT in Mexico from abroad

71 of 89
  1. Zyxel/D-Link switches ✓ Read You are here 3 min
  2. Patch today ✓ Read You are here 3 min
  3. Vendor access ✓ Read You are here 3 min
  4. 23H2 Enterprise ends ✓ Read You are here 3 min
  5. November patches ✓ Read You are here 3 min
  6. Bank fraud ✓ Read You are here 3 min
  7. M365 outage plan ✓ Read You are here 3 min
  8. Field services →
Next Windows 11 23H2 Enterprise and Education lose support on November 10, 2026: what to do today with the PCs of your Mexico operation