Food Bank of Central Louisiana was listed on 04 November 2026 by the Dark Project ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Dark Project listed 7 organizations that month and 43 in total.
- Listed 15 days ago.
- 971 organizations were listed by all groups in November 2026, see the month.
- 14 in Agriculture and Food Production that month.
- 427 in US that month.
Updated 2026-11-19 05:30 UTC. Data: public leak-site listings. How we work.
Food Bank of Central Louisiana
Threat Group Post & Evidence
- Listed by
- Dark Project 43 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.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
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.
About Food Bank of Central Louisiana\ The Food Bank of Central Louisiana is a nonprofit organization dedicated to alleviating hunger in Central Louisiana through collaboration and food distribution programs. They provide assistance to over 42,500 households annually, offering resources such as SNAP applications and mobile pantry services. Their initiatives include programs aimed at strengthening children and nourishing seniors, addressing the specific needs of vulnerable populations. The organization encourages community involvement through donations and volunteer opportunities to support their mission. The Central Louisiana Food Bank was the victim of a cyberattack, resulting in the theft of more than 130 GB of confidential data. The stolen data includes documents such as banking and financial information, personal data of employees and clients, databases, and other important company in…
Show the full post (910 characters)
About Food Bank of Central Louisiana\ The Food Bank of Central Louisiana is a nonprofit organization dedicated to alleviating hunger in Central Louisiana through collaboration and food distribution programs. They provide assistance to over 42,500 households annually, offering resources such as SNAP applications and mobile pantry services. Their initiatives include programs aimed at strengthening children and nourishing seniors, addressing the specific needs of vulnerable populations. The organization encourages community involvement through donations and volunteer opportunities to support their mission. The Central Louisiana Food Bank was the victim of a cyberattack, resulting in the theft of more than 130 GB of confidential data. The stolen data includes documents such as banking and financial information, personal data of employees and clients, databases, and other important company information.
Amounts as written
- 130 GB
Kinds of data mentioned
-
Customer or client data
“…such as banking and financial information, personal data of employees and clients, databases, and other important company information.”
-
Employee and HR records
“…documents such as banking and financial information, personal data of employees and clients, databases, and other important company information.”
-
Databases and backups
“…banking and financial information, personal data of employees and clients, databases, and other important company information.”
Plain-English summary AI-written
The group says the Food Bank of Central Louisiana was targeted in a cyberattack that resulted in theft.
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 Food Bank of Central Louisiana (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 Food Bank of Central Louisiana 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 Food Bank of Central Louisiana 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.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, employee and hr records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
Within 30 days
- Keep watching Food Bank of Central Louisiana 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 Food Bank of Central Louisiana
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: customer or client data.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- 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: 130 GB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Agriculture and Food Production organizations and ask them whether they were affected. Why: Dark Project listed 1 other Agriculture and Food Production organization(s) in the last 90 days.
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
Listing severity score (heuristic)
48/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.