Ransomware Tracker by ExposureDrift
Dashboard / Victims / hacla.org

hacla.org was listed on 31 December 2022 by the lockbit3 ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). lockbit3 listed 56 organizations that month and 2015 in total.

  • Listed 1419 days ago.
  • 489 organizations were listed by all groups in December 2022, see the month.
  • 24 in Government & Defense that month.
  • 2 other listings for the same organization.

Updated 2026-11-19 07:07 UTC. Data: public leak-site listings. How we work.

hacla.org corporate emblem
Listed by lockbit3 Disclosed: 2022-12-31 18:30 UTC

hacla.org

hacla.org Government & Defense

Named in 3 separate listings

Other listings name this organization: a different group, or the same group months apart. Each is a claim the group published, not a confirmed breach. The same group listing it again within a few months is not counted: that is the same listing sent twice or moved from countdown to published.

This listing: lockbit3, 31 Dec 2022 cactus, 31 Oct 2024 dispossessor, 19 Apr 2024

Threat Group Post & Evidence

Listed by
LockBit 3.0 (Black) 2,015 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

More than 15TB of files : The Housing Authority of the City of Los Angeles is a state-chartered public agency. Established in 1938, HACLA provides the largest stock of affordable housing in the city Los Angeles, California and is one of the nation's...

Amounts as written

  • 15TB

Plain-English summary AI-written

The group says it has more than 15TB of files associated with the Housing Authority of the City of Los Angeles.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with hacla.org (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask hacla.org directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what hacla.org can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.

Within 30 days

  • Keep watching hacla.org A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are hacla.org

Within 3 days

  • Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
  • Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 15TB. Treat group figures as unverified.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 2 critical panel(s) reachable from the internet.
  • Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain hacla.org
Industry Vertical Government & Defense
Country Not stated
Enrichment Status ENRICHED

Listing severity score (heuristic)

100/100 • CRITICAL

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 30/30 pts
Government, public safety and defense
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 25/25 pts
Largest claim: a terabyte or more, or regulated data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
87/100 • CRITICAL
Last Audited: 2026-11-14 18:36 UTC Passive Recon
Total Network Assets 9
5 hosts • 4 unique IPs
0 cloud-hosted • 2 SaaS
Subdomain Assets 5
Critical Panels 2 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 2 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Microsoft 365 / Exchange Online
DNS Authority Authoritative DNS (com)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by lockbit3

All →
new blog domain lockbit 5.0
Other 2025-12-05 11:08 UTC
hennessyfunds.com
Financial Services 2025-05-09 11:00 UTC
ehlers-inc.com
Technology 2025-05-06 17:44 UTC
kll-law.com
Legal Services 2025-05-01 23:45 UTC
arc-com.com
Technology 2025-05-01 23:44 UTC
pdcm.com
Financial Services 2025-05-01 23:43 UTC

Other listings for this name

3 listings
lockbit3 Viewing Now
2022-12-31 18:30 UTC Severity: 100/100
cactus CRITICAL
2024-10-31 11:15 UTC Open listing →
2024-04-19 10:49 UTC Open listing →