Badge
11,371 badges added since 01 January 2025
โ† Back to Shoppers Drug Mart company page

Shoppers Drug Mart Breach Incident Score: Analysis & Impact (NO-SHOPRELOB1773534483)

The Rankiteo video explains how the company Shoppers Drug Mart has been impacted by a Breach on the date March 13, 2026.

newsone

Incident Summary

Rankiteo Incident Impact
-122
Company Score Before Incident
794 / 1000
Company Score After Incident
672 / 1000
Company Link
Incident ID
NO-SHOPRELOB1773534483
Type of Cyber Incident
Breach
Primary Vector
NA
Data Exposed
Over 1.8 billion records allegedly exposed
First Detected by Rankiteo
March 13, 2026
Last Updated Score
March 14, 2026

If the player does not load, you can open the video directly.

newsone

Key Highlights From This Incident Analysis

  • Timeline of Shoppers Drug Mart's Breach and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteoโ€™s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Shoppers Drug Mart Rankiteo cyber scoring and cyber rating.
  • Rankiteoโ€™s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
newsone

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Shoppers Drug Mart breach identified under incident ID NO-SHOPRELOB1773534483.

The analysis begins with a detailed overview of Shoppers Drug Mart's information like the linkedin page: https://www.linkedin.com/company/shoppers-drug-mart, the number of followers: 211309, the industry type: Retail and the number of employees: 31984 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 794 and after the incident was 672 with a difference of -122 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Shoppers Drug Mart and their customers.

On 12 March 2024, Loblaw Companies Limited disclosed Data Breach issues under the banner "Alleged Massive Data Breach at Loblaw".

A threat actor operating under the handle 'igotafeeling' on the DarkWeb Informer forum has claimed to have breached Loblaw, Canadaโ€™s largest food and pharmacy retailer.

The disruption is felt across the environment, affecting Salesforce, Shoppers Drug Mart systems and GitLab projects, and exposing Over 1.8 billion records allegedly exposed, with nearly 1.8 billion (alleged) records at risk.

In response, and stakeholders are being briefed through Press release downplaying the breach and denying financial data compromise.

The case underscores how Unverified (allegations under scrutiny), with advisories going out to stakeholders covering Loblaw customers with PC Optimum accounts, Shoppers Drug Mart loyalty cards, or prescription histories advised to monitor for potential fraud.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating salesforce, Shoppers Drug Mart systems, Oracle identity systems affected and Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating oracle identity records (MFA device details and credentials) compromised. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with moderate to high confidence (80%), supported by evidence indicating shoppers Drug Mart records include passwords and tokens and OS Credential Dumping (T1003) with moderate to high confidence (70%), supported by evidence indicating oracle identity records (MFA device details and credentials) compromised. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating 1.8 billion records allegedly exposed, including customer, pharmacy, and payment data and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating 75.1M Salesforce records, 673 marketing/email tables compromised. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating threat actor claims possession of 1.8B records; data sold on dark web alleged and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating threat actor posted on DarkWeb Informer forum; invited media to verify data. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (30%), supported by evidence indicating no evidence of ransomware or encryption, but extortion demand made and Data Manipulation: Stored Data Manipulation (T1565.001) with lower confidence (40%), supported by evidence indicating threat actor may manipulate data to pressure Loblaw into response. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating use of compromised Oracle identity records (MFA/credentials) to evade detection and Hide Artifacts: Hidden Files and Directories (T1564.001) with moderate confidence (50%), supported by evidence indicating source code (3,014 GitLab projects) accessed; may hide malicious code. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.