Ransomware Tracker by ExposureDrift
Dashboard / Victims / City of Fort St. John (city.cityfsj.local)

City of Fort St. John (city.cityfsj.local) was listed on 27 March 2025 by the incransom ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). incransom listed 30 organizations that month and 1044 in total.

  • Listed 602 days ago.
  • 751 organizations were listed by all groups in March 2025, see the month.
  • 58 in Government & Defense that month.
  • 36 in CA that month.

Updated 2026-11-19 06:13 UTC. Data: public leak-site listings. How we work.

City of Fort St. John (city.cityfsj.local) corporate emblem
Listed by incransom Disclosed: 2025-03-27 12:56 UTC

City of Fort St. John (city.cityfsj.local)

fortstjohn.ca Government & Defense CA

Threat Group Post & Evidence

Listed by
INC Ransom 1,044 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.

With a population of 21,000 and growing with the city itself, Fort St. John is the largest city in Northeastern BC. Fort St. John is not only the largest city in the Northeast Region of BC; it is also the largest city in British Columbia situated along the world-famous Alaska Highway. If you are driving the highway, we invite you to stop in and explore all that Fort St. John has to offer. You wont be disappointed! Fort St. John is The Energetic City for good reason. The title reflects not only our large resource base of oil, natural gas, forestry and agriculture, but also the vitality of our residents who are, on average, 9 years younger than the average population in the rest of the province. Modern-day pioneers continue to bring a fresh spirit of exploration, innovation and connection to community within our city

Plain-English summary AI-written

The group says the text does not identify any data it holds.

Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.

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 City of Fort St. John (city.cityfsj.local) (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 City of Fort St. John (city.cityfsj.local) 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 City of Fort St. John (city.cityfsj.local) 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.

Within 30 days

  • Keep watching City of Fort St. John (city.cityfsj.local) 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 City of Fort St. John (city.cityfsj.local)

Within 3 days

  • Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
  • Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
  • 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 Government & Defense organizations and ask them whether they were affected. Why: incransom listed 6 other Government & Defense 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 fortstjohn.ca
Industry Vertical Government & Defense
Country CA
Enrichment Status ENRICHED

Listing severity score (heuristic)

81/100 • CRITICAL

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 30/30 pts
Government, public safety and defense
2. Group tier 25/25 pts
Tier 1: among the groups with the most listings in our data
3. Data Volume & PII Scope 10/25 pts
Baseline: no size or sensitive data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
73/100 • CRITICAL
Last Audited: 2026-11-14 17:57 UTC Passive Recon
Total Network Assets 8
5 hosts • 3 unique IPs
0 cloud-hosted • 4 SaaS
Subdomain Assets 5
Critical Panels 1 (VPN/Admin/SSO)
Non-Prod / UAT 0 Staging/Dev
SaaS Ecosystem 4 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A+ (SPF/DMARC)
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 Mimecast Secure Gateway
DNS Authority Amazon Route 53
Edge CDN / Shield AWS CloudFront / Edge
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by incransom

All →
CHAMBOURCY
Agriculture and Food Production 2026-11-19 17:35 UTC
Pulsar
Technology 2026-11-19 01:56 UTC
CENTERED CO., LTD.
Technology 2026-11-19 01:56 UTC
Chin Fong Machine Industrial
Manufacturing 2026-11-17 00:14 UTC
pilotcat.com
Technology 2026-11-16 22:40 UTC
BHIC Bofors Asia
Government & Defense 2026-11-16 14:02 UTC