
Stellantis (Partial) Breach
Oct 10, 2025
9,429,250 rows
Added on Oct 3, 2025
What happened in the Stellantis (Partial) Breach?
DataBreach.com Team Β· October 2nd 2025, 8:00 pm EDT
The incident is one of several breaches affecting Salesforce in 2025. A group calling itself "Scattered LAPSUS$ Hunters" released a limited sample of the stolen database on October 3, 2025. The records have since been indexed and anonymized in our search engine.
According to the attackers, the full dataset is scheduled for release on October 10, 2025.
Data found in hackersβ sample -
π§ Personal Information
- Full name - β Present
- First and last names (separate fields) - β Present
- Title / salutation - β Present
- Gender - β Present
- Date of birth - β Present
- Language - β Present
- Nationality - β Empty
π§ Contact Information
- Email address - β Present
- Phone number - β Present
- Mobile number - β Empty
- Home phone - β Present
- Contact preference flags (email, phone, SMS, mail) - β Present
- Alternate or secondary emails - β Empty
π Address / Location Data
- Street address - β Present
- City - β Present
- State / province - β Present
- Postal code - β Present
- Country - β Present
- Latitude / longitude - β Present (on FCA contact)
π’ Account / Company Information
- Company name - β Present
- Account ID and record ID - β Present
- Record type - β Present
- Dealer / business type - β Present
- Customer market - β Present (βUSAβ)
- Dealer code or company code - β Present
- Region or business unit - β Present
- Parent dealer or preferred dealer - β Empty
π Vehicle Ownership & Interest
- Owns new vehicles - β Present
- Owns pre-owned vehicles - β Present
- Number of cars owned - β Present
- Community or club membership flags - β Present
- Vehicle interest fields (sports / preferences) - β Empty
π¬ Marketing & Communication
- Direct-marketing permission - β Present
- Newsletter subscription - β Present
- Privacy hold / contact privacy - β Present
- Soft-spam flag - β Present
- Preferred language - β Present
- Lead source - β Present (βMODISβ)
- Legal resolution or disclaimer fields - β Empty
π Data Quality & Profiling
- Data quality score - β Present
- Data quality description - β Present
- Basic validation check - β Present
- Internal domain detection flag - β Present
- Email correctness flag - β Present
βοΈ System Metadata
- Record creation date - β Present
- Record modification date - β Present
- SystemModstamp - β Present
- Created by / modified by user IDs - β Present
- Owner ID - β Present
- Photo URL - β Present
- Deleted / priority flags - β Present
- Legacy creation / migration / batch IDs - β Present (FCA records)
π Cross-System & IDs
- Internal Salesforce record IDs - β Present
- Legacy customer source ID - β Present
- Legacy batch ID - β Present
- External IDs (social, Jigsaw, etc.) - β Empty
Recent News











Ho-ly G*t: TeamPCP Claims Theft of Thousands of GitHub Internal Repositories
a month ago

17M Nissan cars impacted by large ransomware attack
3 months ago

Iranian hackers just used Strykerβs own security tools to delete itself
4 months ago

Massive Odido cyberattack leaks customer IBANs and government IDs
4 months ago

Figure breach proves blockchain cannot save us from human error
4 months ago

Substack notifies users of data breach affecting nearly 700,000 accounts
5 months ago

UPenn claims "Under 10" victims in 1.2M breach involving donors like Trump and Musk
5 months ago

How 0apt is Using Random Noise to Fake a Ransomware Empire
5 months ago

Hackers Are Now Using Global-e Data to Target Ledger Owners at Their Home Addresses
6 months ago

Meta Denies Instagram Breach After Password Reset Panic
6 months ago

Why the 2.3 Million Wired Record Breach Is a Nightmare for CondΓ© Nast
6 months ago