← Breach analysis by the Dual Vulnerabilities framework

Acer Philippines employee data leak (Ph1ns, 2024)

2024 · Philippines · C - Manufacturing · Data theft via third-party vendor

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via third-party vendor

Dual vulnerability type

Strategy to Execution

Evidence coverage: 2/6 stages, weight 11/60

Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Strategic expectation at the victim: Acer Philippines remained accountable for its own employees' personal data and publicly pledged the most rigorous data protection for information entrusted to its care, with the National Privacy Commission and the Cybercrime Investigation and Coordinating Center the competent authorities it notified. (2) In practice, that data sat with an unnamed external vendor running the company's employee attendance system; the vendor's database was breached, the full employee dataset - including usernames, passwords, roles, birthdates and mobile numbers - was published on a hacking forum on 12 March 2024 by 'ph1ns' under #OpEDSA, and neither the vendor nor Acer had detected the compromise: it surfaced through the attacker's own post and an e-mail tip to the monitoring group Deep Web Konek. The entry vector into the vendor environment was never disclosed and is not load-bearing. (3) The expectation that was not acted on originated doctrinally - a public protection commitment plus controller accountability for outsourced employee data - and the chain broke in execution: safeguards and assurance over the vendor-run attendance system were not realized in operational reality, so the dataset could be stolen and published unnoticed. No source shows leadership deferring, under-resourcing or accepting the assurance gap, so the break is execution rather than leadership. The classification rests on the pre-breach condition at the entry stage (clearest evidence); the detection-stage gap (nothing detected the intrusion before the leak) is recorded as a separate, inference-based gap pointing to Expertise to Execution and cannot win the tie-break. Response and disclosure were prompt - same-day acknowledgement and regulator notification - and show no gap. (4) RM13 (Strategy to Execution lens): Acer's trust in the attendance vendor was not matched by supplier-security requirements, due diligence or monitoring that translated into controlled third-party operation - the vendor's database was breached while holding Acer's employee records, and the victim learned of it only from a public leak (causal role: Enabling). RM34 (Strategy to Execution lens): the monitoring and detection requirements that should have covered the outsourced dataset holding the victim's HR data were not implemented or operated as intended, so the intrusion stayed invisible until the data was published (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Row's Victim/receiver_name field is 'Acer Philippines;Not available' (two receiver entries, the second unresolved); the Acer Philippines entry was classified. The third-party vendor holding the attendance data was never publicly named, so the vendor-side control failure could not be examined directly; the victim-side reading rests on Acer's own statements and reporting. Attacker claims (pure data theft, no extortion, data wiped on the breached servers) are unverified attacker statements reported by BleepingComputer. The EuRepoC start_date 01.01.2024 looks like a generic placeholder; the incident surfaced on 12 March 2024, which is consistent with Year 2024. BleepingComputer lists earlier Acer group incidents (REvil ransomware 2021, India after-sales breach 2021, server breach 2023), but none involves a comparable vendor-managed personal-data path, so RM21 was not coded. Unattended run: no action requiring user consent was needed or taken.