Data leak
⛓ Supply Chain
PageUp People HR SaaS Platform Breach — Australian HR Vendor Affecting 100+ Employers
Primary Source ↗Incident Details
In May 2018, PageUp People — a Melbourne-based HR and recruitment software company with clients across Australia, UK, US, Canada, and other countries — discovered unusual activity in its IT systems suggesting a malware-based compromise. PageUp disclosed the breach on 5 June 2018, prompting over 100 employer clients to suspend their use of PageUp and notify job applicants and employees. Major Australian employers affected included Telstra, Linfox, Reserve Bank of Australia, Aldi, Medibank, Target Australia, and the Australian government. UK clients included the BBC, Oxfam, and several UK government departments. The data potentially exposed included applicant details (names, addresses, dates of birth, email addresses, telephone numbers, employment history, academic qualifications), employee data, and reference information. PageUp stated that encrypted credit card data (not stored by PageUp), references, and documents were not compromised. PageUp notified the OAIC under Australia’s new mandatory Notifiable Data Breaches scheme (which had only come into effect in February 2018 — the PageUp breach was one of the first major cases under the new regime). The OAIC and UK ICO both investigated. The incident highlighted the risk of HR platform supply chains and the breadth of downstream impact when a single SaaS recruitment platform is compromised — affecting hundreds of thousands of job applicants across dozens of major organisations simultaneously.
Technical Details
- Initial Attack Vector
- Unknown attacker compromised PageUp People's cloud-based HR and recruitment platform; PageUp described it as unusual activity in its IT infrastructure suggesting a malware infection; the platform stored candidate and employee data for over 100 Australian and global employers
- Vendor / Product
- PageUp People HR recruitment SaaS platform
- Supply Chain Attack
- ✅ Confirmed third-party / vendor compromise
Timeline
- 2018-05-23 Breach occurred
- 2018-06-05 Publicly disclosed
- 2018-06-05 Customers notified