Cyber & AI intelligence
Briefs indexed3764
Issues37
Published Mondays07:30 CT
█ Ransomware UNIVERSITY-OF-BRIT 2026-11-16

University of British Columbia: Shadowbyt3$ Ransomware Group Claims Breach

"The ransomware group Shadowbyt3$, which now calls itself "ShadowByt3$ 2.0", claimed on 16 November 2026 that it had breached the University of British Columbia (UBC) in Vancouver, Canada. The group says it will publish…"

The ransomware group Shadowbyt3$, which now calls itself "ShadowByt3$ 2.0", claimed on 16 November 2026 that it had breached the University of British Columbia (UBC) in Vancouver, Canada. The group says it will publish the stolen data unless the university contacts it to negotiate. The University of British Columbia has not confirmed the claim. No Canadian regulator or national CERT has published anything about it, and no established security outlet has reported it yet. Almost everything known so far comes from the attackers' own leak post, as summarised by the threat-tracking site QPulse. QPulse's alert lists the "geographic impact" as the United Kingdom, which is wrong: UBC is a Canadian institution. Treat this as an unverified extortion claim, not a confirmed breach.

What Happened

QPulse reports that Shadowbyt3$ posted UBC as a victim on 16 November, along with a contact email address for ransom talks and a threat to leak data if the university does not get in touch. QPulse rates the incident 85 out of 100 for severity. That rating is the site's own and is based on the attackers' claims.

The evidence the group has published points to a WordPress website, not to UBC's central systems. According to QPulse, the attackers released table structures and raw data samples from a WordPress database. They also named the site's theme (Airi) and plugins (Elementor, Contact Form 7, Kirki Toolkit and Mailchimp for WordPress). QPulse says the group also posted server command logs showing routine admin work on a Linux server, such as database management, file permission changes and maintenance.

It is still unclear which UBC website is involved, whether it is run centrally or by a single department, research group or outside contractor, and whether any file encryption took place. Nothing reported so far suggests ransomware was deployed. The claim reads more like data theft and extortion.

What Was Taken

Shadowbyt3$ has not said how much data it holds. The samples QPulse describes come from database tables with the prefix "ap_2_". In WordPress this usually means one site within a multi-site setup. They include:

On their own, these tables would be a limited exposure. The options table matters more than the rest, because WordPress sites often store API keys, SMTP credentials and third-party service tokens there.

QPulse also cites figures from the infostealer intelligence firm Hudson Rock: 486 UBC employees and 8,212 users with credentials stolen by infostealer malware, plus 333,452 passwords and 5,165 cookies in the related exposure data. These figures should not be read as data taken in this breach. Infostealer data is collected over time from infected personal and work devices across a whole organisation's domain. Neither QPulse nor Hudson Rock has shown that it is connected to the Shadowbyt3$ claim. It does show a large pool of stolen UBC logins already in criminal hands, and that is a real risk whether or not the claim holds up.

Why It Matters

Universities are under steady attack this term, and the attacks follow a familiar pattern: stolen data, threats to publish it, and slow or partial confirmation from the victim.

Many of these incidents began, or appear to have begun, with smaller and less central systems: a supplier's platform, a booking app, a login database. A departmental WordPress site fits that pattern. If the claim is real, the immediate danger is reused credentials and secrets taken from the site's configuration, which an attacker could use to get further into the university.

The Attack Technique

Shadowbyt3$ has not said how it got in, and UBC has not commented. Three routes are plausible, though none is confirmed:

  1. Vulnerable WordPress plugins or themes. Elementor, Contact Form 7, Kirki and similar plugins have all had serious flaws in the past. Unpatched sites built on several plugins are a common target.
  2. Logins stolen by infostealers. With Hudson Rock reporting nearly 8,700 UBC staff and user accounts in infostealer data, simply logging in with valid credentials is a realistic route. The server command logs the group published suggest it may have had shell or administrator access, not just a database copy.
  3. Social engineering. Computer Weekly reports that Jisc, which provides IT and network services to UK universities, is tracking a surge in ClickFix scams. These trick people into pasting and running commands on their own machines, which installs malware. Jisc says it has blocked between 300 and 37,000 phishing emails a week aimed at UK universities and colleges since the academic year began. Computer Weekly also cites Microsoft figures showing a more than twentyfold rise in ClickFix attacks between December 2025 and May 2026, with malware following 96% of the time. These campaigns are a common source of the infostealer infections described above.

What Organizations Should Do

  1. Rotate secrets stored in WordPress. Check the wp_options table (or prefixed versions) on every institutional WordPress site for API keys, SMTP passwords, Mailchimp tokens and similar secrets. Rotate any that could have been exposed, and reset WordPress salts and administrator passwords.
  2. Inventory and patch departmental websites. Universities often run hundreds of sites outside central IT. Find every WordPress install, remove plugins that are abandoned or unused, enforce automatic updates, and put sites with no clear owner behind a web application firewall or take them down.
  3. Act on infostealer data. Check your domains against infostealer intelligence feeds. Force password resets and revoke sessions for every account that turns up, because stolen cookies can get past MFA if sessions are not revoked.
  4. Require phishing-resistant MFA on administrator and remote access. Cover SSH, hosting control panels and CMS admin logins. The command logs Shadowbyt3$ published suggest server-level access, which a password alone should never grant.
  5. Train staff and students on ClickFix. Repeat Jisc's message: no genuine CAPTCHA or verification check will ever ask you to copy, paste and run a command. Where you can, block or alert on Run-dialog and PowerShell execution started from the browser.
  6. Prepare the people likely to be affected. The UK Information Commissioner's Office gave useful advice after a separate incident at ASOS. It told people who receive messages from apparent hackers not to click links in unexpected emails or texts, to change passwords only through the official site or app, and to watch their accounts for unusual activity. UBC staff, students and site users should follow the same advice and expect phishing that refers to this claim, whether or not a leak happens.

Sources: Shadowbyt3$ Ransomware Group Claims Breach of University of British... | ASOS statement ICO | NI schools: Parents warned to be on alert after data breach - BBC News | Nurseries among 320,000 school files leaked on dark web - BBC News | ClickFix scams pose growing risk to education sector, Jisc says Co... | University of Nottingham Breach Exposes 454,635 Student and Alumni... | Waseda data breach: 3,342 records and alumni service pause | Universidad Peruana Británico Employee Personal Data Exposed on Dar...