People search World Food Programme data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 World Food Programme-linked incident, with headline counts up to 600K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why World Food Programme breach history matters
World Food Programme operates in Nonprofit (International). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — Gaza self-registration app breach (~600k households; May 31)
Cataloged incident. The World Food Programme confirmed in early June 2026 that unauthorized actors accessed personal information submitted through its Palestine self-registration application (SRA), where individuals register for food and cash assistance after verification. Reporting in The New Humanitarian and DataBreaches.net cited roughly 600,000 Gaza households affected—described as potentially the largest-known breach of humanitarian beneficiary data—with exposed fields including names, ID numbers, mobile numbers, and location dat Exposed categories include Names, ID numbers, mobile numbers, and location data for Gaza assistance registrants. BreachHistory cites approximately 600K+ affected records in this row. See the world-food-programme-gaza-sra 2026 recor and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple World Food Programme catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the World Food Programme company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/world-food-programme · Latest: world-food-programme-gaza-sra2026.
Sources: BreachHistory catalog (1 row for World Food Programme), company and regulator disclosures cited in individual breach records.