CannabisForum

cannabis.com

233,999
Exposed Records
Feb 2014
Breach Date
12 years ago
Unknown
Password Risk
Retail industry
Retail
Industry
Added to XposedOrNot on November 8, 2023 · #611 of 776 breaches by records exposed

About This Breach

The Ontario Cannabis Store (OCS) Data Breach, which occurred in 2014, resulted in a significant theft and leak of sensitive business data. The breach exposed information such as individual cannabis retailers’ sales figures, inventory levels, license numbers, and quantities of cannabis sold during December 2021 and January 2022.

Data Exposed

Usernames
Email addresses
Passwords
Historical passwords
Instant messenger identities
IP addresses
Geographic locations
Dates of birth

Frequently Asked Questions

When did the CannabisForum data breach happen?

CannabisForum was breached in Feb 2014. The breach was added to the XposedOrNot index on November 8, 2023.

How many records were exposed in the CannabisForum breach?

233,999 records were exposed, making it the #611 largest of the 776 breaches in our index.

What data was exposed in the CannabisForum breach?

The exposed data includes: Usernames, Email addresses, Passwords, Historical passwords, Instant messenger identities, IP addresses, Geographic locations, Dates of birth.

What should I do if I was affected by the CannabisForum breach?

Change your password on the affected service (and anywhere you reused it), turn on two-factor authentication, and set up free breach alerts on XposedOrNot so you know the moment your email appears in a new breach.

What Should You Do?

Urgent

Change Your Passwords

Update your password immediately, using 12+ characters with numbers and symbols.

High Priority

Enable Two-Factor Authentication

Add 2FA on all supported accounts using an authenticator app like Google Authenticator or Authy.

Recommended

Review Device Security

Update your devices and browsers, and check for unauthorized logins.

Recommended

Monitor Your Accounts

Set up login alerts and review account activity regularly for suspicious access.

Best Practice

Use a Password Manager

Never reuse passwords: use a password manager to generate unique ones for each account.