Skip to content
Lacambra Web Portal Services
← 2026, week by week
Privacy · Week 44, 26 October to 1 November 2026

DMW-linked backups: 68.8 GiB copied in under 24 minutes

An operator's own logs show 27 backups named for the overseas-employment systems copied in under 24 minutes. Why the backup is the copy to guard.

Two plain grey archive boxes side by side on a concrete floor, one sealed with oxblood tape, the other open and empty with its lid leaning against it.

On 28 October the threat-intelligence firm Hunt.io published something attackers rarely leave behind: their own logs. An operator had worked from a server in Singapore with its folder open to anyone, and the transfer log inside it records 27 SQL Server backups, 68.8 GiB in all, copied on 6 September in 23 minutes and 46 seconds. The file names match systems of the Philippine Overseas Employment Administration, whose work is now the Department of Migrant Workers'. The next day the National Privacy Commission said it was investigating and coordinating with the DMW.

Much is still unknown, and Hunt.io says so. It did not open the backups, so what is in them is not established. It could not see how the operator got in, or where the copy went. The systems those names describe serve overseas Filipino workers, 2.16 million of them in 2023 by the Philippine Statistics Authority's estimate, though nobody has said how many records the backups hold. What the logs do settle is the order of events: the backups were copied about twenty hours before the first payload was fetched from the folder, so whatever access took the data was already enough. And the operation came to light because the folder was public, Hunt.io notes, not because anyone had detected the theft. On 10 November the NPC named ten agencies that had filed breach notifications, without saying the list was complete; the DMW was not among them.

Why the backup is the copy that matters

A live system makes an attacker work. Its records sit behind screens, searches and permissions, and taking them a page at a time is slow and leaves a trail. A full backup is the opposite: the whole database, every table and every record in it, in one file designed to be moved. That is what makes backups the prize, and how 68.8 GiB could be copied in less time than a lunch break.

It is also the copy fewest people watch. A scheduled job makes it every night, it lands on a file share or a second server, and nobody thinks about it again until a restore is needed. The question an office rarely asks is who, and what, can read that file.

What it means for the systems I build

Most of the systems I build hold personal data about people who never chose the system: staff in a travel approval chain, members in a portal, parents paying tuition by card. All of them are backed up, and moving one makes more copies still. A migration makes an export from the old system, a staging database and a copy to rehearse on, and each one is a complete set of the data. Each needs the same care as the live system, and a date by which it is deleted. It is the same accounting that a migration report should give for the records themselves.

There is a second point in what the NPC said on 10 November. An agency stays accountable for personal data even when a contractor handles it, under Section 21 of the Data Privacy Act of 2012, and the same section binds every organisation that controls personal data, not only agencies. It requires contractual or other reasonable means to give the data a comparable level of protection in the contractor's hands. That is why a data processing agreement is in place before I touch personal data, and why the data stays in the client's own accounts rather than mine.

Five checks for your own backups

  • Find every backup: the nightly ones, the export someone made before an upgrade, the copy a supplier took for testing. A file nobody knows about cannot be protected.
  • Encrypt them, and keep the key somewhere other than beside the backup.
  • Store them where the accounts that run your servers and services cannot read them. A backup the web server can open is one break-in away from leaving.
  • Watch for large transfers out. A copy that size takes long enough to notice, if something is watching.
  • Put backups in your Data Privacy Act inventory and your breach plan. If one leaves, it is a breach of everything in it, and the NPC's breach rules, Circular 16-03, apply.

If the backups are the part of an old system nobody owns any more, that is usually a sign the system itself needs moving, which is the work behind Move it. The fit check is the place to start.

Sources

  1. Hunt.io, 68 GB Stolen From a Philippine Government Agency's Overseas-Employment Databases, Exposed by the Operator's Own Open Directory, 28 October 2026
  2. Newsbytes.PH, NPC probes alleged theft of 68GB of DMW-linked database backups, 29 October 2026
  3. Newsbytes.PH, NPC confirms data breach reports from 10 gov't agencies, 10 November 2026
  4. Lawphil, Republic Act No. 10173

Enrique Lacambra III builds internal business systems from Cainta, Rizal.

Email me← All writing

Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.