Events Secure.com at Black Hat USA 2026

EXTRA! Thief Empties 27 Migrant Worker Databases in 24 Minutes, Then Leaves the Door Open

Hackers copied 68.8 GiB of Philippine migrant worker database backups in under 24 minutes. See what was taken, the IOCs, and how to defend it.

Philippine Migrant Worker Data Breach Was Caught by the Attacker’s Own Logs

Somebody walked out of a Philippine government agency with 27 database backups tied to overseas workers, and nobody noticed for weeks. The only reason we know? The thief left their own logs sitting on an open web server.

What Happened?

On 6 September 2026, an unknown operator copied 68.8 GiB of SQL Server backups to a rented server in Singapore in 23 minutes and 46 seconds. The filenames match systems of the former Philippine Overseas Employment Administration, now part of the Department of Migrant Workers (DMW), covering case management, contracts, accreditation, and cashier records.

What Was Inside the Open Directory?

A threat intelligence crawler found the server’s open directory a day later, according to recent reports. Inside sat:

  • The rclone transfer log recording the theft
  • A PowerShell stager that rebuilds its payload in memory
  • A rebranded GodPotato privilege escalation tool
  • A full Impacket kit for working Windows networks
Breach Timeline · Philippines

27 databases out the door in under 24 minutes.

The theft finished in the early hours of 6 September 2026. Nobody outside the operator knew for weeks, until their own open directory gave the game away.

68.8 GiB
Backups copied
27
SQL Server backups
23m 46s
Transfer time
  1. 6 SEP · 01:26
    Transfer completesBackups tied by filename to POEA and OFW systems land on a Singapore staging server.
  2. 6 SEP · 21:38
    Payloads pulled backAgency linked hosts fetch the stager and a rebranded GodPotato build over a 76 minute window.
  3. 7 SEP
    Open directory spottedA crawler indexes the unprotected folder, logs and tools included.
  4. 28 OCT
    Findings publishedResearchers go public after notifying national CERT and the migrant workers department.
  5. 29 OCT
    Privacy regulator steps inThe National Privacy Commission opens a probe under the Data Privacy Act of 2012.

Where the data went after the staging server is still unknown.

The Plot Thickens

About 20 hours after the theft, two hosts carrying the agency’s own dmw.gov.ph certificate reached back to that server and pulled down the payloads. That hints the operator still had a foothold inside.

What We Still Don’t Know

How they first got in is unknown. Researchers found no initial access method, no command-and-control channel, and no proof the payloads ran. They never opened the backups either, so the link to the agency rests on filenames.

Attack Chain · What The Logs Show

Public tools, renamed and reused.

Nothing here was a zero day. The operator stitched together free, well known tooling and leaned on one Windows privilege that service accounts hold by default.

01
Initial access
Not established. Victim hosts exposed SMB, WinRM and RDP to the internet.
UNKNOWN
02
Stager
PowerShell script rebuilds a payload from base64 chunks in memory.
portalload.ps1
03
Privilege escalation
Rebranded GodPotato abuses SeImpersonate to reach SYSTEM.
Wrqsnx.dll
04
Collection
27 SQL Server backups staged; Impacket on hand for Windows networks.
/tmp/imp
05
Exfiltration
rclone copies 68.8 GiB to a Singapore VPS. Final destination unknown.
rclone.log
Defender takeaway

Strip SeImpersonate from accounts that do not need it, pull SMB and WinRM off the internet, and alert on large outbound backup transfers. Each one breaks a link above.

What’s the Impact?

Overseas Filipino workers are a huge, mobile population, and records like these likely hold identity, contract, and payment details. That’s raw material for identity theft, recruitment scams, and loan fraud. It’s also a detailed map of a diaspora, which interests spy agencies as much as criminals.

Who Did It?

Nobody’s saying. Some Chinese language strings turned up, but they came from a third-party library, so researchers declined to attribute the attack. The data hasn’t surfaced for sale yet.

How Have Authorities Responded?

Researchers alerted the national CERT and the DMW before publishing on 28 October, and the National Privacy Commission opened a probe under the Data Privacy Act of 2012 the next day, as Dark Reading also reported.

How to Avoid This

  • Pull SMB (445), WinRM (5985, 47001), and RDP (3389) off the internet. All four were exposed on agency-linked hosts.
  • Strip SeImpersonate from service accounts that don’t need it. GodPotato abuses that one privilege to reach SYSTEM.
  • Encrypt database backups and keep them off production servers.
  • Alert on large outbound transfers and on tools like rclone running where they shouldn’t.
  • Scan your own attack surface on a schedule, the way an attacker would.
Attack Surface · Agency Linked Hosts

Four doors that should not face the internet.

Researchers found these services answering on hosts tied to the migrant worker portal. Any one of them hands an attacker a place to start.

445
SMB
File sharing and a classic route for lateral movement
5985
WinRM
Remote command execution over HTTP
47001
WinRM
Second WinRM listener left reachable
3389
RDP
Self signed portal cert, open to brute force

Put admin protocols behind a VPN or jump host, then scan your own ranges the way an attacker would.

Your Backups Are a Target. Treat Them Like One.

This attacker used free, public tools and still walked off with 27 databases. The gap was routine hygiene nobody had time to chase.

Secure.com puts governed AI Teammates on that grunt work while your team stays in charge:

  • Cloud Teammate flags exposed admin ports like SMB and WinRM and opens the fix with full context.
  • Red Teammate tests whether a low-privilege foothold can climb to SYSTEM, then hands defenders the path to close.
  • SOC Teammate watches for odd bulk transfers and escalates to a human under approval rules you set.
  • GRC Teammate maps every fix to evidence, so the audit trail is ready when regulators ask.
  • Every action runs inside scoped permissions and approval gates. Attack. Harden. Prove. Repeat.

The Bottom Line

A careless operator exposed this theft, not a detection tool. Most victims won’t get that lucky. If your exposed ports, risky privileges, and backup transfers aren’t on someone’s watch list today, they’re already on an attacker’s.

FAQs

What happened in the Philippine migrant worker data breach?
On 6 September 2026, an unknown operator copied 27 SQL Server backups (68.8 GiB) linked by filename to the Department of Migrant Workers to a server in Singapore in under 24 minutes.
What data was stolen in the DMW breach?
The backups match former POEA systems for case management, contracts, accreditation, and cashier records. They likely hold identity, contract, and payment details of overseas Filipino workers, though researchers did not open the files.
How was the breach discovered?
A threat intelligence crawler found the attacker’s unprotected open directory on 7 September 2026. It held the rclone transfer log, a PowerShell stager, a rebranded GodPotato build, and an Impacket kit.
Who is behind the attack?
Nobody has been named. Researchers found some Chinese-language strings, but they came from a third-party library, so they declined to attribute the attack.
Is the government investigating?
Yes. The National Privacy Commission opened a probe under the Data Privacy Act of 2012 on 29 October 2026, a day after researchers published their findings.
How can organizations prevent a similar attack?
Take SMB, WinRM, and RDP off the internet, remove SeImpersonate from service accounts that don’t need it, encrypt backups, and alert on large outbound transfers and unexpected rclone use.