23 Philippine Institutions Named in Leak Claims: Why the Risks Extend Beyond the Headlines
One week. Twenty-three institutions. Millions of records claimed. And a country trying to work out which of those claims are real.
Between November 5 and 7, a monitoring group called Deep Web Konek documented underground postings naming 23 Philippine institutions, including national government agencies, law enforcement bodies, a military branch, universities, and private companies. The postings claimed to contain millions of personal, corporate, and administrative records, alongside reports of a website defacement.
Then the official responses began, and the picture became more nuanced. Some of what was claimed is being investigated, some has been acknowledged, and some may turn out to be recycled. For any organization that holds personal data, the useful question is not "who is right?" but "what would we do if our name were on that list next week?"
What Was Claimed, and by Whom
The report documents what threat actors allegedly posted, rather than findings independently established by investigators. It attributes the leaks to several underground groups and lists claimed volumes: about 19.2 million records from the Department of Labor and Employment, up to 19 million resident profiles tied to a local government database, and thousands of files from agencies including the Office of the Vice President and the Coast Guard. Separately, the same monitoring group claimed about 10 million individual taxpayer records and 500,000 corporate records from the Bureau of Internal Revenue (BIR).
The data types named in the report range from government IDs and taxpayer and corporate registration details to employee and payroll records, student files, and operational logs. On the education side, it cites claimed student records ranging from about 11,000 at one university to more than 117,000 at another.
Treat every one of these figures as a claim. The Philstar article itself says the affected entities are still verifying the extent of the breach, and it does not independently confirm which 23 institutions were hit or how the data was obtained. Neither the monitoring report nor the coverage of it explains the technique used against any single organization. A claimed record count is a statement about what someone says they hold, not a measurement of what was lost.
What Has Been Confirmed So Far
On November 10, the National Privacy Commission (NPC) said it had received personal data breach notifications from 10 government agencies: the BIR, the Securities and Exchange Commission (SEC), the Department of Information and Communications Technology (DICT), the Presidential Commission on Good Government, the Department of Labor and Employment, PAGCOR, the Department of Justice, the Philippine Coast Guard, the Department of Trade and Industry, and the Philippine Institute of Volcanology and Seismology.
Notice what the NPC did not say. It did not disclose how many people may be affected, what types of information were involved, when the incidents happened, or whether they are connected. A notification indicates that an organization has reported a personal data breach to the NPC. However, it does not automatically establish that the specific leak claims circulating online are accurate, or confirm the scale of the exposure.
Notably, the DICT, which plays a central role in the country's cybersecurity efforts, is among the agencies that submitted notifications. It is a reminder that even institutions responsible for strengthening national cybersecurity face their own security challenges.
The Cybercrime Investigation and Coordinating Center (CICC) added more color. Its executive director, Renato Paraiso, said hackers have claimed breaches of around 20 agencies, that some data appears to have been stolen, and that the vulnerabilities in the BIR and SEC were not only contained but remediated. He also said investigators are checking whether some of the posted datasets are old data being recycled to look like new hacks, and that the real identities of the groups involved have not yet been determined.
The agencies themselves have been careful. The BIR's November 10 advisory said initial findings indicate that no taxpayer information was modified or lost and that no filing and payment records were compromised, but that certain taxpayer profile information may have been exposed. A forensic investigation with the CICC and the DICT's national CERT is ongoing, and the BIR has not confirmed the 10 million figure circulating online. The SEC said it learned of the reports on November 6, launched an investigation, tightened security, and increased monitoring, and had not confirmed a breach in the early reporting. Expect the picture to keep shifting as investigations conclude.
Why Unverified Claims Still Matter
How should a business leader read a story like this? Four questions help. Who is making the claim, and what is their incentive? Is there proof, such as samples that investigators can check? Is the data new, or recycled from an earlier incident? And what does the affected organization say once it has looked? Right now, most of the 23 entries are still at the first question.
It is tempting to wait for certainty. That is a mistake, for two reasons.
First, even recycled data is useful to a scammer. The NPC warned the public about phishing, fraudulent messages, identity theft, and other social engineering scams tied to the reported breaches, and advised avoiding suspicious links and attachments and not sharing personal information with unverified parties. A tax-themed phishing message containing real names and taxpayer information can appear convincing whether the underlying data is two weeks or two years old. A leak does not need to be new to be dangerous. It only needs to be believable.
Second, the legal expectations do not wait for forensics. The NPC reminded agencies that filing a notification does not remove their responsibility to contain incidents, reduce harm, and prevent recurrence, and that under Section 21 of the Data Privacy Act they remain accountable for data held by outside contractors. Its spokesperson, Jose Belarmino II, called for "concrete and effective measures," not only compliance with notification rules. That standard applies to private organizations that hold personal data as well, which makes this week's headlines relevant well beyond government.
This Did Not Start Last Week
The government had already signaled concern. On September 8, the DICT and the CICC placed national agencies, government-owned corporations, local governments, and critical information infrastructure operators on heightened cyber vigilance, after reports involving the Department of Migrant Workers, the Department of Labor and Employment, and the Philippine Ports Authority. Within 24 hours, each covered organization had to give its head a one-page readiness assessment.
The priorities in that advisory read like a checklist for any organization: fix critical vulnerabilities, enforce multi-factor authentication on critical and privileged accounts, remove unnecessary internet exposure, strengthen security monitoring, confirm that backups can be restored, review third-party access, and test incident-response procedures. The agencies were careful to say the exercise must produce "protective action, not merely another compliance report." One caution: some claims from that earlier period, such as a hacktivist group's assertion of month-long access to a government directory, were still unconfirmed when the advisory was reported.
Taken together, the September advisory and November's leak claims point to recurring security concerns: exposed systems, excessive access privileges, and third-party connections that may introduce additional vulnerabilities.
What Every Organization Should Do Now
You do not need to be named in a leak claim to recognize the security risks it exposes. These steps apply whether your organization is a ministry, a school, or a logistics company.
Maintain an Inventory of Personal Data. Many organizations can describe their main databases. Fewer can list the exports, backups, and contractor-held copies that sit beside them.
Audit Third-Party Access. The DICT advisory specifically calls out third-party access. List every vendor, contractor, and integration with a connection to your systems, and remove what is no longer needed.
Enforce MFA on Privileged Accounts. Enforce multi-factor authentication on administrative and privileged accounts first, since those are the ones that turn a small foothold into a large loss.
Reduce Unnecessary Internet Exposure. Remove interfaces and services that do not need to be public. If it is exposed by habit, close it.
Establish an Incident Notification Process. Know who decides whether an incident meets the notification threshold under the Data Privacy Act, and who talks to the NPC, your customers, and your staff. Draft that process before the day you need it.
Monitor for Leaked Organizational Data. Monitor for your organization's domains, staff emails, and branded phishing pages appearing in new leaks or scams, so that you learn about it before your customers do.
Prepare Employees and Customers for Phishing. If your organization appears in any claim, expect a wave of convincing phishing. Tell customers how you will, and will not, contact them.
Check Whether You Are Reachable Before Someone Else Does
Most of these steps rely on an accurate picture of what is exposed. That picture is hard to get from the inside, because the answer includes systems added years ago, test environments left running, and connections opened for a vendor's convenience.
Secuna Pentest helps organizations identify and validate security weaknesses across web applications, APIs, networks, cloud infrastructure, and mobile applications through manual, scoped penetration testing. This supports the DICT's priorities of reducing unnecessary internet exposure and reviewing third-party access.
As a DICT-recognized VAPT provider under the D-TAP program, Secuna helps organizations gain a clearer understanding of their security posture and identify weaknesses that could expose their systems to potential attacks.
Penetration testing does not replace incident response, patching, or strong access controls, and it does not guarantee that every exposed asset is found. It can assess authorized, in-scope systems that connect to third parties, but it does not automatically audit every vendor's security. It also cannot tell you whether a specific leak claim is true. What it can do is help an organization see where an attacker could realistically get in, so that the next headline is about someone else.
Claims of a breach are not proof of one, but the response should not wait for proof. Organizations that navigate this period effectively will be those that already understand what data they hold, who can access it, and how they will respond when a security incident occurs.
To learn more about how Secuna can help strengthen your organization's security posture, reach out to our team at sales@secuna.io or explore our services at secuna.io.
Sources: Massive Cyber Attacks Hit 23 Government, Private Sites, The Philippine Star · Alleged Hacks Hit at Most 20 Government Agencies: CICC, The Philippine Star · NPC Confirms Data Breach Reports From 10 Gov't Agencies, Newsbytes.ph · Philippine Tax Agency Faces 10 Million-Record Leak Claim: What We Know, eSecurityPlanet · SEC, BIR Probe Alleged Leaks of Corporate, Taxpayer Data, Context.ph · BIR Says Taxpayer Profile Data May Have Been Exposed, Philstar Tech · DICT, CICC Order 24-Hour Cyber Checks After Attacks on Gov't Websites, Newsbytes.ph · Massive Cyber Attacks Hit 23 Government, Private Sites, OneNews.ph