# Upbound Group Data Theft Enables $13M in Fraudulent Acima Lease-to-Own Fraud (Q2 2026)

> Threat actors obtained unauthorized access to non-sensitive customer information and documents belonging to Upbound Group (parent of Acima Leasing, Rent-A-Center, Brigit, and Upbound Mexico) and weaponized the stolen data to fraudulently establish Acima lease-to-own agreements, causing approximately $13 million in fraudulent contract losses during Q2 2026. No ransomware or extortion group has claimed responsibility, and Upbound disclosed the incident in a July 21, 2026 SEC Form 8-K.

- **Published:** 2026-07-22T00:00:00Z
- **Last reviewed:** 2026-07-22T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-1634
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-upbound-acima-data-theft-lease-fraud-tl-2026-1634.webp?v=fe396fff (Threadlinqs threat intel: Upbound Group Acima Data Theft: Detection & IOCs (TL-2026-1634) — Medium severity, 18 IOCs, 9 detection rules.)
- **ID:** TL-2026-1634
- **Severity:** MEDIUM
- **Category:** DATA_BREACH
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 18

## Description

Upbound Group, Inc. (formerly Rent-A-Center, parent of Acima Leasing, Rent-A-Center, Brigit, and Upbound Mexico) disclosed in a Form 8-K filed with the SEC on July 21, 2026 that it identified unauthorized access to non-sensitive customer information and supporting documents. The company has not disclosed the initial access vector, any exploited vulnerability, or malware used; no CVE has been assigned and no ransomware or extortion group has taken credit, distinguishing this from typical ransomware-driven breach disclosures.

Rather than encrypting systems or threatening to leak data for extortion, the threat actors monetized the stolen information directly: they used the compromised customer identity and document data to fraudulently apply for and establish lease-to-own agreements through Acima's consumer financing platform. Acima's lease-to-own model allows customers to obtain merchandise from participating third-party retailers while Acima pays the retailer upfront and collects lease payments from the customer over time. By impersonating real customers using the stolen personal data (a pattern consistent with identity-theft-enabled application fraud / 'Frankenstein fraud' techniques used across consumer lending), the fraudsters caused Acima to pay retailers for merchandise that was then obtained by the fraud ring, with no corresponding lease payments ever made.

This resulted in approximately $13 million in elevated fraudulent contract losses within the Acima segment during Q2 2026 (April-June 2026), which Upbound quantified and disclosed to investors. Upon identifying the data compromise, Upbound states it began implementing mitigation and remediation measures, including enhanced authentication controls, additional fraud-detection and monitoring capabilities, and other security enhancements, developed in coordination with external cybersecurity experts. The company also notified federal law enforcement of the incident. Upbound's investigation remains ongoing, and the company has stated it will make further legal or regulatory notifications as appropriate based on investigation findings. Upbound assessed the incident as not material to its investment decisions/financial condition for SEC reporting purposes beyond the disclosed fraud-loss figure.

Upbound's board formed a dedicated Cybersecurity, Technology and Innovation Committee on December 4, 2024 to oversee cybersecurity, technology, and innovation risk at the board level — governance context that predates this incident and that the company's post-incident enhanced-authentication and fraud-monitoring remediation now feeds into.

No technical indicators of compromise (IPs, domains, hashes, malware families, or C2 infrastructure) have been publicly disclosed, and no CVE is associated with this incident — this is a data-theft-enabled financial fraud campaign rather than a disclosed technical exploit chain. The fraud mechanism itself follows a well-documented pattern in consumer-lending/BNPL and rent-to-own fraud: stolen or synthesized identity data and supporting documents (pay stubs, ID images, proof-of-address) are used to pass identity-verification checks, an account or application is established or taken over under a real or blended identity, merchandise is financed and shipped/collected, and the fraud actor defaults on all payments, leaving the lender (Acima) to absorb the retailer payout as a loss.

## MITRE ATT&CK

- T1589 Gather Victim Identity Information
- T1591 Gather Victim Org Information
- T1586 Compromise Accounts
- T1585 Establish Accounts
- T1078 Valid Accounts
- T1684.001 Impersonation
- T1213 Data from Information Repositories
- T1005 Data from Local System
- T1567 Exfiltration Over Web Service
- T1657 Financial Theft
- T1565 Data Manipulation

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Bulk Customer Identity Repository Access — Service Account Anomaly** (`TL-2026-1634-SPL-001`)

Detects a service or read-only account performing a bulk/scripted pull against a customer-identity or document repository (CRM, document store, lease-origination backend) outside normal single-record lookup patterns — the reconnaissance/staging precursor to identity-theft-enabled application fraud like the Upbound/Acima incident.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1213, T1005
- **Data sources:** acima:document_repository application logs, CustomAppLogs_CL (Sentinel custom log table)
- **Severity:** high
- **Confidence:** high

### Splunk SPL

```spl
index=app_crm sourcetype="acima:document_repository" (action="bulk_query" OR action="bulk_export" OR query_record_count>50)
| eval hour=strftime(_time,"%H")
| where account_type="service" OR account_type="readonly"
| stats count as bulk_events, sum(query_record_count) as total_records_pulled, values(src_ip) as src_ips, dc(document_id) as distinct_documents by user, account_type
| where bulk_events>=1 AND total_records_pulled>50
| table user, account_type, bulk_events, total_records_pulled, distinct_documents, src_ips
| sort -total_records_pulled
```

### Microsoft KQL

```kql
let LookbackWindow = 24h;
let BulkThreshold = 50;
CustomAppLogs_CL
| where TimeGenerated > ago(LookbackWindow)
| where AppName_s in ("acima-crm", "acima-document-repo")
| where Action_s in ("bulk_query", "bulk_export") or RecordCount_d > BulkThreshold
| where AccountType_s in ("service", "readonly")
| summarize BulkEvents=count(), TotalRecordsPulled=sum(RecordCount_d), DistinctDocuments=dcount(DocumentId_s), SourceIps=make_set(SrcIp_s) by UserPrincipalName_s, AccountType_s
| where TotalRecordsPulled > BulkThreshold
| project UserPrincipalName_s, AccountType_s, BulkEvents, TotalRecordsPulled, DistinctDocuments, SourceIps
| sort by TotalRecordsPulled desc
```

### Sigma

```yaml
title: Bulk Customer Identity Repository Access by Service Account
id: 7a1e2c10-4f3b-4a1a-9c1a-tl20261634sig01
status: experimental
description: Detects a service/read-only account performing bulk or scripted reads against a customer-identity or document repository, consistent with pre-fraud data staging seen in the Upbound/Acima incident.
references:
    - https://www.bleepingcomputer.com/news/security/upbound-says-hack-caused-13-million-in-fraudulent-acima-leases/
author: Threadlinqs Team
date: 2026-07-22
tags:
    - attack.collection
    - attack.t1213
    - attack.t1005
    - attack.reconnaissance
    - attack.t1589
logsource:
    category: application
    product: web
detection:
    selection_action:
        Action:
            - 'bulk_query'
            - 'bulk_export'
    selection_account:
        AccountType:
            - 'service'
            - 'readonly'
    selection_volume:
        RecordCount|gt: 50
    condition: (selection_action or selection_volume) and selection_account
falsepositives:
    - Scheduled legitimate ETL/reporting jobs against the same repository
    - Authorized data migration or backup activity
level: medium
```

**Known false positives:**

- Scheduled ETL/reporting jobs against the repository using a legitimate service account
- Authorized bulk data migration or backup export

**Tuning notes:** Baseline normal bulk-export volume per service account over 30 days and set BulkThreshold above p99 of legitimate ETL jobs; exclude known backup/migration account IDs via an allowlist lookup.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- Reconnaissance-to-Application Pipeline — Identity Lookup Preceding Application Submission (locked: unlock with TL Creds)
- Repeated Document Template/Image Hash Reuse Across Distinct Applicant Identities (locked: unlock with TL Creds)
- Retailer Payout Disbursed With No Subsequent Customer Payment Activity (locked: unlock with TL Creds)
- Scripted Bulk Export Process Pattern Against Internal Record System (locked: unlock with TL Creds)
- Impersonated-Identity Valid Account Usage Across Unrelated Application Sessions (locked: unlock with TL Creds)
- Aggregate Financial Theft Loss Spike — Fraudulent Contract Loss Rate Anomaly (locked: unlock with TL Creds)
- High-Velocity Fraudulent Lease/Loan Application Submission Burst (locked: unlock with TL Creds)
- Immediate Payment Default Following Lease Origination — Financial Theft Pattern (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Upbound says hack caused $13 million in fraudulent Acima leases](https://www.bleepingcomputer.com/news/security/upbound-says-hack-caused-13-million-in-fraudulent-acima-leases/)
- [Upbound Group, Inc. Form 8-K (July 21, 2026)](https://www.sec.gov/Archives/edgar/data/0000933036/000119312526310605/upbd-20260721.htm)
- [Upbound Group, Inc. Form 8-K Exhibit 99.1](https://www.sec.gov/Archives/edgar/data/0000933036/000162828026028583/ex-991upboundgroupincrep.htm)
- [Upbound posts 2025 growth, issues 2026 outlook (8-K filing coverage)](https://www.stocktitan.net/sec-filings/UPBD/8-k-upbound-group-inc-reports-material-event-4b813ac45438.html)
- [Upbound Group Inc. filed SEC Form 8-K: Results of Operations and Financial Condition, Regulation FD Disclosure](https://quantisnow.com/insight/upbound-group-inc-filed-sec-form-8k-results-of-operations-and-financial-condition-regulation-5745390)
- [UPBOUND GROUP, INC. SEC 10-K Report (board Cybersecurity, Technology and Innovation Committee disclosure)](https://www.tradingview.com/news/tradingview:b6c76932e28bb:0-upbound-group-inc-sec-10-k-report/)
- [SEC Filing | Upbound Group, Inc. - Investor Relations (governance/cybersecurity oversight disclosure)](https://investor.upbound.com/node/19876/html)
- [Financial Theft, Technique T1657 - Enterprise | MITRE ATT&CK](https://attack.mitre.org/techniques/T1657/)
- [Gather Victim Identity Information, Technique T1589 - Enterprise | MITRE ATT&CK](https://attack.mitre.org/techniques/T1589/)
- [Impersonation, Technique T1656 - Enterprise | MITRE ATT&CK](https://attack.mitre.org/techniques/T1656/)
- [Valid Accounts, Technique T1078 - Enterprise | MITRE ATT&CK](https://attack.mitre.org/techniques/T1078/)
- [Data Manipulation, Technique T1565 - Enterprise | MITRE ATT&CK](https://attack.mitre.org/techniques/T1565/)
- [What Is Synthetic Identity Fraud & Theft? - Proofpoint](https://www.proofpoint.com/us/threat-reference/synthetic-identity-fraud)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-1634
