HomeNewsBreachesAbout
Account
fedex-salesforce-2025

Fedex (Partial) Breach

Oct 10, 2025

166,293,145 rows

Added on Oct 3, 2025

Search the Leak

Email
Phone Number

What happened in the Fedex (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
  • Job title / department - β›” Empty
  • Gender - β›” Empty
  • Date of birth / age - β›” Empty
  • Nationality / country of residence - βœ… Present

πŸͺͺ Identification Data

  • Internal Salesforce record IDs - βœ… Present
  • Customer / account IDs - βœ… Present
  • Employee or user IDs - βœ… Present
  • Tracking and case numbers - βœ… Present
  • Passport or government ID - β›” Empty

πŸ“§ Contact Information

  • Email addresses - βœ… Present (multiple customer and staff addresses)
  • Phone numbers - βœ… Present (work phone and system contact fields)
  • Street address - βœ… Present (company and customer addresses)
  • City, state, postal code, country - βœ… Present
  • Fax, alternate, and mobile numbers - β›” Mostly empty

🏒 Company / Business Information

  • Company names - βœ… Present
  • Business role or contact type (e.g., shipper, case owner) - βœ… Present
  • Department or division - β›” Empty in most records

πŸ’¬ Chat & Interaction Data

  • Live chat transcript text - βœ… Present (short real-time conversation logs)
  • Chat timestamps and duration - βœ… Present
  • Browser, device, and IP address info - βœ… Present
  • Location derived from IP - βœ… Present
  • Visitor network name - βœ… Present
  • Referrer URL and browser language - βœ… Present
  • Chat agent and customer identifiers - βœ… Present

πŸ“¨ Customer Support Case Data

  • Case number and ID - βœ… Present
  • Case subject and description - βœ… Present (included full email thread text)
  • Customer and company contact info - βœ… Present
  • Case category, language, and region - βœ… Present
  • Account number and tracking number fields - β›” Empty
  • Proof of delivery / survey flags - β›” Empty
  • Case status and timestamps - βœ… Present
  • Internal queue and SLA data - βœ… Present

πŸ’³ Account & Communication Preferences

  • Opt-in / opt-out flags (email, SMS, phone) - βœ… Present
  • HasOptedOutOfEmail - βœ… Present (false)
  • DoNotCall settings - βœ… Present
  • Preferred communication method - βœ… Present
  • Other consent or survey flags - β›” Mostly empty

βš™οΈ System Metadata

  • Record creation and modification timestamps - βœ… Present
  • Creator and owner IDs - βœ… Present
  • SystemModstamp and internal tracking fields - βœ… Present
  • User account details (system usernames, company affiliations) - βœ… Present
  • Login or activity timestamps - βœ… Present for chat and case logs
  • Password or authentication data - β›” Empty

πŸ”— Cross-System and Integration Data

  • Connected system IDs (LiveChat, Case, Account, Contact links) - βœ… Present
  • Email domain and tracking relationships - βœ… Present
  • External system references - βœ… Present (e.g., β€œApplied_eCAR”)
  • Federation or partner identifiers - β›” Empty

βš–οΈ Privacy & Legal Fields

  • Data rights or opt-out flags - βœ… Present
  • Confidentiality disclaimers in email text - βœ… Present (inside case description)
  • Legal/notice text from customer email - βœ… Present
  • Government ID or sensitive personal docs - β›” Empty

For media inquiries, contact us at contact@databreach.com