Ransomware Tracker by ExposureDrift
Dashboard / Victims / University of British Columbia

University of British Columbia was listed on 16 November 2026 by the ShadowByt3$ ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). ShadowByt3$ listed 5 organizations that month and 25 in total.

  • Listed 2 days ago.
  • 906 organizations were listed by all groups in November 2026, see the month.
  • 36 in Education that month.
  • 52 in CA that month.

Updated 2026-11-16 09:15 UTC. Data: public leak-site listings. How we work.

University of British Columbia corporate emblem
Listed by ShadowByt3$ Disclosed: 2026-11-16 08:35 UTC

University of British Columbia

ubc.ca Education CA

Threat Group Post & Evidence

Listed by
ShadowByt3$ 25 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.

We are ShadowByt3$ 2.0. We have hacked you. Contact us and negotiate or we will leak the following and our contact is below: contact: [email protected] - Administrator: The registered admin email belongs to [email protected]. 2. WordPress Database Infrastructure The file outlines the creation schema and raw data blocks for several standard database tables using the ap_2_ prefix: - ap_2_options: The largest chunk of the file, containing core site settings, active plugin configurations, serialized widget spaces, security notifications, and cron schedules. - ap_2_comments & ap_2_commentmeta: Stores reader comments. Currently contains only the default placeholder comment ("Hi, this is a comment...") from "A WordPress Commenter". - ap_2_links: Holds structural blogroll links. - Third-Party Plugin Tables: Structural blueprints for extended features, such as ap_2_ninja_table_items (for Ni…
Show the full post (2316 characters)

We are ShadowByt3$ 2.0. We have hacked you. Contact us and negotiate or we will leak the following and our contact is below: contact: [email protected] - Administrator: The registered admin email belongs to [email protected]. 2. WordPress Database Infrastructure The file outlines the creation schema and raw data blocks for several standard database tables using the ap_2_ prefix: - ap_2_options: The largest chunk of the file, containing core site settings, active plugin configurations, serialized widget spaces, security notifications, and cron schedules. - ap_2_comments & ap_2_commentmeta: Stores reader comments. Currently contains only the default placeholder comment ("Hi, this is a comment...") from "A WordPress Commenter". - ap_2_links: Holds structural blogroll links. - Third-Party Plugin Tables: Structural blueprints for extended features, such as ap_2_ninja_table_items (for Ninja Tables layout grids), ap_2_imagelinks, and ap_2_e_events. 3. Active Theme & Plugin Ecosystem The settings reveal the exact environment the site is utilizing: - Active Theme: It runs a theme called Airi (and references historical testing of Twenty Twenty and clf-basic). - Active Plugins: A serialized array lists core components active on the site, including Elementor (page builder), Contact Form 7, Kirki Toolkit, and Mailchimp for WordPress. - Site Feeds: It caches several localized technical news feeds, structural error logs, and recent WordPress core beta testing reports. 4. Technical Server Commands (File 2) The attached command log tracks an administrator manually managing the server environment on a Linux backend: - Database Management: Importing and exporting database backups (db_backup.sql, db_backup_newsite.sql). - File Permissions: Tweaking ownership rights across the backend directory structures (wp-admin, wp-content, wp-includes). - Server Maintenance: Upgrading the PHP version (switching to PHP 8.1), updating the WordPress CLI interface, clearing system caches, and deploying a local instance of phpMyAdmin to inspect the tables visually. - Migration Scripts: Executing broad global search-and-replace terminal operations to migrate site strings and absolute paths from an older testing subdomain (heiltsuknew.arts.ubc.ca) back to the main domain (heiltsuk.arts.ubc.ca).

Kinds of data mentioned

  • Email and communications

    “…below: contact: [email protected] - Administrator: The registered admin email belongs to [email protected]. 2. WordPress Database Infrastructure The file outlines the…”

  • Source code and designs

    “…Holds structural blogroll links. - Third-Party Plugin Tables: Structural blueprints for extended features, such as ap_2_ninja_table_items (for Ninja Tables layout grids), ap_2_imagelinks,…”

  • Databases and backups

    “…The registered admin email belongs to [email protected]. 2. WordPress Database Infrastructure The file outlines the creation schema and raw data blocks for several standard…”

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 University of British Columbia (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 University of British Columbia 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 University of British Columbia 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: email and communications.
  • 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: source code and designs, databases and backups.

Within 30 days

  • Keep watching University of British Columbia 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 University of British Columbia

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: email and communications.

Within 3 days

  • Rotate secrets and signing keys Assume secrets in repositories are exposed: rotate API keys, tokens and code-signing keys, and review build and release systems for unexpected changes. Why: The post names: source code and designs.
  • 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.
  • Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
  • Check regulatory and stakeholder notification duties Canada: PIPEDA requires reporting breaches that pose a real risk of significant harm, as soon as feasible. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Canada.

Within 30 days

  • Check shared suppliers and software List the suppliers and software you share with other Education organizations and ask them whether they were affected. Why: ShadowByt3$ listed 1 other Education 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

Resolved Domain ubc.ca
Industry Vertical Education
Country CA
Enrichment Status ENRICHED

Listing severity score (heuristic)

60/100 • ELEVATED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Higher education and research
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 18/25 pts
Larger claim: gigabytes, or business or financial records named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence

No scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.

Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Custom Mail Gateway (ca)
DNS Authority Authoritative DNS (ca)
Edge CDN / Shield None
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by ShadowByt3$

All →
Chevron Corporation
Energy & Utilities 2026-11-16 08:36 UTC
petstop
Retail & E-Commerce 2026-11-16 08:35 UTC
Gorcon Construction Inc
Manufacturing 2026-11-16 08:34 UTC
Glenmore Pharmacy & Medical Clinic
Healthcare 2026-11-16 08:33 UTC
HandyTrac Greystar AZ WARNING
Financial Services 2026-09-16 21:53 UTC
HandyTrac
Financial Services 2026-09-15 00:23 UTC