Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Lexipol Public Safety Platform Breach Exposes 672K User Credentials

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
HIGH
🏢
Affected
4 sector(s)
✅
Actions
5 recommended
📰
Source
haveibeenpwned.com

Lexipol Public Safety Platform Breach Exposes 672K User Credentials

What Happened

In February 2025, Lexipol’s public‑safety policy‑management system was breached by a self‑identified “Puppygirl Hacker Polycule”. Attackers accessed and later published 672,546 user records that contained email addresses, full names, phone numbers, system‑generated usernames and password hashes stored as MD5 or SHA‑256.

Why It Matters for Compliance & Audit Readiness

  • Demonstrates the need for continuous credential‑management controls (strong hashing, mandatory password rotation, MFA) that can be evidenced during audits.
  • Highlights the importance of real‑time monitoring for unauthorized data exfiltration and rapid incident‑response documentation.
  • Reinforces the requirement to keep vendor risk assessments current, capturing data‑handling practices and remediation timelines.

Who Is Affected

  • Public‑safety agencies and law‑enforcement departments that use Lexipol’s SaaS platform.
  • Municipal and state governments that rely on Lexipol for policy management.
  • Any third‑party contractors or partners with shared Lexipol accounts.

Recommended Actions

  • Verify whether any of your organization’s Lexipol accounts appear in the exposed set; request a list from Lexipol if needed.
  • Review and strengthen password‑storage practices (e.g., migrate from MD5/SHA‑256 to bcrypt or Argon2) and enforce a forced password reset for all users.
  • Ensure logging and alerting for anomalous access to Lexipol APIs are enabled and retained per audit policies.
  • Update your vendor risk register with breach details and adjust control‑assurance testing accordingly.
  • Request Lexipol’s incident‑response report and any remediation steps they have taken.

Technical Notes

  • Attack vector: Likely credential harvesting via compromised admin accounts or API endpoints; exact method not disclosed.
  • CVE(s): None reported.
  • Data types exposed: Email addresses, full names, phone numbers, usernames, password hashes (MD5, SHA‑256).

Source: https://haveibeenpwned.com/api/v3/breach/Lexipol

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/Lexipol ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

Point-in-time vendor reviews miss incidents like this.

Verisq AI Trust Operations replaces the annual questionnaire with continuous third-party monitoring — so vendor exposure becomes audit evidence, not a once-a-year guess.

See how Verisq AI Trust Operations works →