Skip to main content

Ransomware victim disclosure

All victims

Micropack

listed as micropack.com.ar · Claimed by Lockbit5 · listed 6 hours ago

Today
Age
since listed · data leaked

Status timeline

  1. ListedAug 3, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Country
Argentina
Listed on leak site
Aug 3, 2026

About the victim

AI dossier — public-source company profile

Micropack is a food and household goods distributor operating in Argentina, serving businesses and retail customers. The company operates from the domain micropack.com.ar.

Industry
Food & Household Goods Distribution

Attack summary

Severity: medium — Data has been published by the threat actor (disclosed status confirmed), but the leak post excerpt provides no specifics on data type, volume, or sensitivity. Distribution sector typically handles business records and customer data; without proof inventory details, severity cannot be escalated to 'high'.

LockBit5 claims to have compromised Micropack and published data. The specific attack vector (encryption, exfiltration, or both) and data categories are not detailed in the available post excerpt.

medium

What the group claims

Micropack is a well-known food and household goods distributor that has been serving businesses and...

Sources

Source

Indexed 6 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About lockbit5

Based on the provided data, LockBit5 appears to be a recently emerged ransomware operation first observed in December 2025, representing what may be a new iteration or rebrand within the LockBit ransomware ecosystem, with primary financial motivations evidenced by their targeting of high-value sectors. Given the LockBit naming convention and the timing of emergence, this group likely operates from Eastern Europe or Russia and may represent either a continuation of previous LockBit operations or a new affiliate group leveraging the established LockBit brand, though specific organizational details remain undocumented by major security agencies. While detailed attack methodologies have not been publicly documented by CISA, FBI, or major security researchers, the group's targeting pattern across 157 victims suggests a broad-spectrum approach focusing on technology, manufacturing, healthcare, and transportation sectors primarily in the United States, Brazil, Germany, Italy, and Mexico. Due to the group's recent emergence in December 2025, there are no publicly documented notable campaigns or major incidents reported by established threat intelligence sources, though the victim count indicates active operations. The group appears to be currently active based on the recent first observation date, though comprehensive analysis from major security agencies has not yet been published given the short timeframe since emergence. The group has been linked to 329 public disclosures across our corpus. First observed on a leak site on December 7, 2025; most recent post August 3, 2026. The operation is currently active.

Timeline of this disclosure

  • August 3, 2026micropack.com.ar listed by lockbit5on the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Manufacturing sector, which has 3,684 disclosures indexed across all operators we track. Geographically, micropack.com.ar is reported in Argentina, a country with 30 ransomware disclosures in our corpus.

If your organisation is affected

A listing by lockbit5 means micropack.com.ar appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Monitor for the data appearing on lockbit5's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.