People search Bilt Rewards data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Bilt Rewards-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why Bilt Rewards breach history matters
Bilt Rewards operates in Fintech (United States). Across indexed rows, recurring themes include ransomware and extortion, credential theft and social engineering, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2024 — customer notices after Evolve Bank & Trust LockBit ransomware / partner breach
Cataloged incident. Evolve Bank & Trust, Bilt’s banking partner for the Bilt Mastercard program, disclosed a major cybersecurity incident tied to LockBit ransomware activity with unauthorized access beginning February 9, 2024, discovery in late May 2024, and containment May 31, 2024 per Evolve’s public incident summary and mainstream security press. Evolve stated affected data could include names, Social Security numbers, account and payment-card numbers, DOB, contact information, government IDs, and ACH transaction metadata for milli Exposed categories include Types described in Evolve notifications—financial and identity fields for partner-bank customer datasets; Bilt users potentially overlapping that population. No attested victim count is published for this row yet. See the bilt-evolve-partner2024 and canonical BreachHistory entry.
2022 — email-to-profile API disclosed names, buildings, unit numbers (press)
Cataloged incident. In June 2022, TechCrunch reported that Bilt Rewards’ web API could return a user’s full name, apartment building name, and apartment number when supplied with only an email address, without login—framed as a serious privacy and potential stalking/abuse vector. Bilt was quoted stating the data returned was already available through public records in normal cases and that the company addressed the issue; journalists and privacy advocates emphasized risks where address linkage is non-obvious from public sources alone. Exposed categories include Name, residential building, and unit number tied to email per reporting—scope of exploitable addresses not standardized in public sources. No attested victim count is published for this row yet. See the bilt2022 and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Bilt Rewards catalog entries; prioritize controls that address this class of failure.
- Credential theft and social engineering — appears across multiple Bilt Rewards catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Bilt Rewards 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 Bilt Rewards company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/bilt · Latest: bilt-evolve-partner2024.
Sources: BreachHistory catalog (2 rows for Bilt Rewards), company and regulator disclosures cited in individual breach records.