LAGUARDA Data Breach
Published: Nov 18, 2026 LockBit5
Threat Level
High
Confidence: High
Quick Summary
- Company
- LAGUARDA Data Breach
- Industry
- Retail
- Threat Actor
- LockBit5
- Date of Incident
- Nov 18, 2026
Executive Summary
LAGUARDA, a retail and e-commerce company based in Ecuador operating through laguarda[.]com.ec, has been claimed as a ransomware victim by the lockbit5 group on November 18, 2026. The company provides retail products and consumer goods through its online platform, serving the Ecuadorian market and a broader Latin American consumer base. SOCRadar’s CTI analysis identified the listing on the lockbit5 leak site, and the claim is further reinforced by a notable stealer-log exposure verdict, with SOCRadar’s stealer-log data returning 25 credential records tied to laguarda[.]com.ec. As a consumer-facing online retailer, LAGUARDA’s e-commerce platform and customer account data represent attractive targets for extortion-driven operations, consistent with the double-extortion model commonly applied to retail organizations. lockbit5 has claimed 39 victims in the past 60 days across Retail & E-Commerce, Healthcare, and Other sectors. Its geographic footprint includes the United States, Brazil, and Italy. LAGUARDA fits the group’s sector preference directly — retail and e-commerce organizations account for a meaningful portion of its victim roster. The listing of LAGUARDA adds Ecuador to the group’s known geographic range, extending its reach into the Latin American consumer market. This combination of sector alignment and geographic expansion makes the claim credible and of high severity for the victim organization.
Technical Analysis
SOCRadar’s stealer-log data returned 25 credential records tied to laguarda[.]com.ec, all linked to customer e-commerce accounts using consumer email providers. No corporate-domain employee credentials appeared in the queried dataset. The records run through November 2026, indicating active harvesting of credentials associated with the company’s customer base. The absence of employee credentials suggests customer account data — not direct employee access — may have been the primary exfiltration target, consistent with a double-extortion operation against a consumer-facing retailer. However, this result does not confirm that the organization is unaffected: the query covered only a sample of available data, and credentials may exist under alternate corporate domains, personal email aliases, or feeds outside the queried dataset. Credentials may also have been used and rotated before indexing, or may not yet have been indexed at all. The 25 customer-linked credential records current through November 2026, combined with the lockbit5 ransomware claim, make this a credible high-severity event for LAGUARDA. While the observed telemetry points to customer account exposure rather than confirmed corporate access, infostealer-harvested credentials could, in a broader scenario, be leveraged by initial access brokers or ransomware operators to validate access to corporate accounts, Microsoft 365, VPNs, or remote-access portals, potentially supporting ransomware deployment. This connection is presented as a possible attack path, not as confirmation of the method used in this incident. Retail-sector organizations should enforce MFA on customer accounts, audit privileged access management, and monitor underground channels for further credential listings. Continued dark web and stealer-log monitoring, proactive credential-hygiene checks, password rotation, and review of Microsoft 365, VPN, and remote-access activity are recommended defensive measures supported by the observed exposure.
Disclaimer
This report is intended for threat intelligence and security awareness purposes. SOCRadar does not host, redistribute or buy stolen data. All breach information reported here is collected from publicly accessible threat actor and ransomware portals. This content is intended to equip CTI teams with context around recent attacks. While we strive for accuracy, listings on ransomware leak and extortion sites cannot always be independently verified and may not reflect confirmed breaches. If you believe any data in this report is incorrect, please contact us.
Share