All Breaches
September 25, 2016 Unverified Telecommunications

Libero Alleged Data Exposure

The 2016 Libero data breach occurred in September 2016 when the MongoDB production user database (lebero-poinx21.pxusers) of Libero (Italiaonline, libero.it), one of Italy's premier web portals and email services, was compromised and leaked online.

699.8 Thousand
Email Identifiers
6
Data Types
High
Exposure Scope
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

6
  • Email addresses
  • Passwords
  • Names
  • Usernames
  • Genders
  • Physical addresses

About This Record

What information was affected in the Libero incident?

The leaked JSON database export (libero.it-lebero-poinx21.pxusers-plaintext-md5-2016.json) comprises approximately 700,000 user profiles, compromising:

  • Identity & Demographics: Full user names (firstname), account usernames, and genders (sex).
  • Authentication Credentials: Passwords stored completely in plaintext (clearPassword) alongside MD5 cryptographic hashes.
  • Contact & Geographic Coordinates: Email addresses (email), street addresses (address), cities, provinces/districts, and postal codes (zipcode).

How many accounts were affected?

Strict RFC canonical email validation verified 699,756 unique valid email addresses across the database.

Technical analysis and security risks

The storage of user credentials in plaintext format represents a critical security failure, allowing direct unauthorized inbox takeovers without requiring cryptographic cracking. Exposure of Italian portal credentials poses severe risks of credential stuffing and identity fraud.

Recommended actions for affected individuals

Users who held accounts on Libero or associated portals should:

  • Immediately reset passwords across any online services where the same password was reused.
  • Enable two-factor authentication (2FA) across email and primary accounts.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information